How to integrate Render MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Render logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Render to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Render agent that can deploy latest code to staging service, restart production web service now, get current status of all services through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Render account through Composio's Render MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Render with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Render
  • Configure an AI agent that can use Render as a tool
  • Run a live chat session where you can ask the agent to perform Render operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

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 Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Render account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Render functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Render
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["render"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Render
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Render tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Render
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

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

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Render
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["render"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Render tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Render through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Render MCP Agent with another framework

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 Agent SDK?

Yes, you can. Claude Agent SDK 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.