How to integrate Render MCP with Claude Code

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Render logo
Claude Code logo
divider

Introduction

Manage your Render directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Render with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Render to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

Supported Tools & Triggers

Tools
Add Header RuleTool to add a custom HTTP header rule to a Render service.
Add or Update Secret FileTool to add or update a secret file for a Render service.
Add Resources to EnvironmentTool to add resources to a Render environment.
Add RouteTool to add redirect or rewrite rules to a Render service.
Create Custom DomainTool to add a custom domain to a Render service.
Create Environment GroupTool to create a new environment group.
Create EnvironmentTool to create a new environment within a Render project.
Create Postgres InstanceTool to create a new Postgres instance on Render.
Create Registry CredentialTool to create a registry credential.
Delete Environment Group VariableTool to remove an environment variable from an environment group.
Delete Environment Group Secret FileTool to remove a secret file from an environment group.
Delete EnvironmentTool to delete a specified environment.
Delete Key ValueTool to delete a Key Value instance.
Delete Owner Log StreamTool to delete a log stream for an owner.
Delete Owner Metrics StreamTool to delete a metrics stream for a workspace.
Delete Registry CredentialTool to delete a registry credential.
Delete Secret FileTool to delete a secret file from a Render service.
Delete ServiceTool to delete a service.
Disconnect BlueprintTool to disconnect a blueprint from your Render account.
Get Active ConnectionsTool to get active connection count metrics for Render resources.
Get Bandwidth SourcesTool to get bandwidth usage breakdown by traffic source.
Get CPU UsageTool to retrieve CPU usage metrics for Render resources.
Get CPU LimitTool to retrieve CPU limit metrics for Render resources.
Get Disk CapacityTool to get disk capacity metrics for Render resources.
Get Disk UsageTool to retrieve disk usage metrics for Render resources.
Get Instance CountTool to get instance count metrics for Render resources.
Get Memory UsageTool to get memory usage metrics for one or more resources.
Get Memory LimitTool to get memory limit metrics for Render resources over a specified time range.
Get Memory TargetTool to get memory target metrics for Render resources.
Get UserTool to get the authenticated user.
Link Service to Environment GroupTool to link a service to an environment group.
List Application Filter ValuesTool to list queryable instance values for application metrics.
List BlueprintsTool to list all blueprints.
List DeploysTool to list recent deploys for a Render service with pagination and filtering.
List DisksTool to list all disks.
List Environment GroupsTool to list environment groups.
List EnvironmentsTool to list environments for a project.
List Environment Variables for ServiceTool to list all environment variables configured directly on a Render service (with pagination).
List InstancesTool to list instances of a service.
List Key Value InstancesTool to list all Key Value instances.
List LogsTool to list logs for a specific workspace and resource.
List Log Label ValuesTool to list log label values for a workspace.
List Maintenance RunsTool to list maintenance runs.
List Notification OverridesTool to list notification overrides for services.
List Workspace MembersTool to list workspace members.
List OwnersTool to list owners (users and teams).
List Postgres InstancesTool to list Postgres instances.
List Postgres ExportsTool to list all exports for a Postgres instance.
List PostgreSQL UsersTool to list PostgreSQL user credentials for a Render PostgreSQL database instance.
List ProjectsList Projects
List Registry CredentialsTool to list registry credentials.
List Resource Log StreamsTool to list resource log stream overrides.
List RoutesTool to list redirect/rewrite rules for a service.
List Secret FilesTool to list secret files for a Render service.
List ServicesTool to list all services.
List Task RunsTool to list task runs.
List TasksTool to list tasks.
List WebhooksTool to list all webhooks.
List WorkflowsTool to list workflows.
List Workflow VersionsTool to list workflow versions.
Restart ServiceTool to restart a service.
Resume ServiceTool to resume a suspended service.
Retrieve Custom DomainTool to retrieve a specific custom domain for a service.
Retrieve deployRetrieve deploy
Retrieve Environment GroupTool to retrieve a specific environment group by ID.
Retrieve Environment VariableTool to retrieve a specific environment variable from a Render environment group.
Retrieve Environment Group Secret FileTool to retrieve secret file from an environment group.
Retrieve Environment VariableTool to retrieve a specific environment variable from a Render service.
Retrieve OwnerTool to retrieve a specific owner (workspace) by ID.
Retrieve Owner Notification SettingsTool to retrieve notification settings for a specific owner (workspace).
Retrieve Postgres InstanceTool to retrieve a specific Postgres instance.
Retrieve ProjectTool to retrieve a specific project by ID.
Retrieve Registry CredentialTool to retrieve a registry credential by ID.
Retrieve Secret FileTool to retrieve a secret file from a Render service.
Retrieve ServiceTool to retrieve a specific service by ID.
Stream Task Runs EventsTool to stream real-time task run events via Server-Sent Events (SSE).
Subscribe to LogsTool to subscribe to real-time logs via WebSocket connection.
Suspend ServiceTool to suspend a service.
Trigger DeployTool to trigger a new deploy for a specified service.
Update Environment GroupTool to update an environment group's name.
Update Environment Group VariableTool to add or update an environment variable in an environment group.
Update Environment Group Secret FileTool to add or update a secret file in an environment group.
Update Environment VariableTool to add or update an environment variable for a Render service.
Update Environment Variables for ServiceTool to update environment variables for a Render service.
Update Header RulesTool to replace all header rules for a Render service.
Update Owner Log StreamTool to update log stream configuration for an owner.
Update Owner Notification SettingsTool to update notification settings for a specific owner (workspace).
Update Postgres InstanceTool to update a Postgres instance configuration.
Update ProjectTool to update a project's name.
Update Registry CredentialTool to update a registry credential.
Update Resource Log StreamTool to update log stream override for a resource.
Update RoutesTool to update redirect/rewrite rules for a service.
Update Secret Files for ServiceTool to update secret files for a Render service.
Update ServiceTool to update a service configuration.
Verify Custom DomainTool to verify DNS configuration for a custom domain.

What is the Render MCP server, and what's possible with it?

The Render MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Render account. It provides structured and secure access to your cloud infrastructure, so your agent can perform actions like deploying applications, managing services, monitoring site health, restarting instances, and scaling resources on your behalf.

  • Automated application deployment: Instantly deploy new web apps or services without manual steps, letting your agent handle setup and rollouts.
  • Service monitoring and status checks: Ask your agent to check the health and uptime of your apps or services, so you’re always up to speed on what’s running smoothly—and what’s not.
  • Instance management and restarts: Enable your agent to restart, stop, or scale up/down your running services to quickly respond to changes or issues.
  • Resource scaling and configuration: Let your agent adjust resource allocations, increasing or decreasing capacity based on current needs or traffic spikes.
  • Error diagnostics and log retrieval: Have your agent fetch logs or error reports to help troubleshoot issues before they become major problems.

Connecting Render via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Render) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Render account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["render"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http render-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Render. This URL will be used to connect Claude Code to Render.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Render
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Render MCP to Claude Code

bash
claude mcp add --transport http render-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (render-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Render MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your render-composio entry in the list
  • This confirms that Claude Code can now access Render tools

If everything is wired up, you should see your render-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Render

The first time you try to use Render tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Render
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Render authorization flow
  • Return to the terminal and start using Render through Claude Code

Once authenticated, you can ask Claude Code to perform Render operations in natural language. For example:

  • "Deploy latest code to staging service"
  • "Restart production web service now"
  • "Get current status of all services"

Complete Code

Here's the complete code to get you started with Render and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["render"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http render-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Render with Claude Code using Composio's MCP server. Now you can interact with Render directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Render operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Render operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Render MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Render MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Render MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Render MCP with Claude Agent SDK

Claude Cowork logo

Claude Cowork

Use Render MCP with Claude Cowork

Codex logo

Codex

Use Render MCP with Codex

Cursor logo

Cursor

Use Render MCP with Cursor

OpenClaw logo

OpenClaw

Use Render MCP with OpenClaw

Hermes logo

Hermes

Use Render MCP with Hermes

CLI logo

CLI

Use Render MCP with CLI

Google ADK logo

Google ADK

Use Render MCP with Google ADK

LangChain logo

LangChain

Use Render MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Render MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Render MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Render MCP with LlamaIndex

CrewAI logo

CrewAI

Use Render MCP with CrewAI

OpenCode logo

OpenCode

Use Render MCP with OpenCode

VS Code logo

VS Code

Use Render MCP with VS Code

FAQ

What are the differences in Tool Router MCP and Render MCP?

With a standalone Render MCP server, the agents and LLMs can only access a fixed set of Render tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Render and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Render tools.

Can I manage the permissions and scopes for Render while using Tool Router?

Yes, absolutely. You can configure which Render scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Render data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗