Render.com MCP Extension for Gemini CLI

This Gemini CLI extension integrates with Render.com's Model Context Protocol (MCP) server, providing tools to manage and interact with Render.com services directly from the Gemini CLI.

Features

This extension connects to Render.com's remote MCP server, which provides tools for:

• Managing Render.com services
• Deploying applications
• Monitoring service health
• Managing environment variables
• And more Render.com operations

Prerequisites

• Gemini CLI installed
• Node.js (v18 or later)
• A Render.com API key

Setup

1. Get your Render.com API key from https://dashboard.render.com/

   • Go to Account Settings → API Keys
   • Create a new API key

2. Create a .env file in the extension directory:

   cp .env.example .env

   Then edit .env and add your API key:

   RENDER_API_KEY=your_render_api_key_here
   

   Note: The .env file is gitignored and will not be committed to version control.

3. Install the extension:

   gemini extensions install /path/to/render-com-mcp

4. Enable the extension:

   gemini extensions enable render-com-mcp

Usage

Once installed and enabled, you can use Render.com tools directly in your Gemini CLI conversations:

gemini chat

Then in the chat:

• "List my Render services"
• "Deploy my latest changes to production"
• "Check the status of my web service"
• "Update environment variables for my service"

Configuration

The extension consists of:

• gemini-extension.json - Extension configuration
• start-server.js - Wrapper script that loads .env and starts the MCP connection
• .env - Your Render.com API key (create from .env.example)

The extension automatically loads your API key from the .env file in the extension directory.

Troubleshooting

Authentication errors

Make sure your .env file exists and contains a valid RENDER_API_KEY:

cat .env  # Unix/Mac/Linux
type .env  # Windows

The file should contain:

RENDER_API_KEY=your_actual_api_key_here

Extension not starting

1. Verify Node.js is installed: node --version
2. Check that the .env file is in the extension directory
3. Verify the API key in .env is correct

Connection issues

Verify you have internet access and can reach https://mcp.render.com/mcp

License

Apache-2.0