How to integrate Render MCP with LangChain

This guide walks you through connecting Render to LangChain 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 LangChain 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.

Get started for freeGet a demo
Render logoRender
Api Key

Render is a unified cloud platform for building and running apps and websites. It simplifies deployment, scaling, and management across your projects.

95 Tools

Introduction

This guide walks you through connecting Render to LangChain 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 LangChain 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

ChatGPTOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Render project to Composio
  • Create a Tool Router MCP session for Render
  • Initialize an MCP client and retrieve Render tools
  • Build a LangChain agent that can interact with Render
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

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

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Render functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Render tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['render']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Render tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Render tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "render-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Render MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Render tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Render related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['render']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "render-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Render related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

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

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Render action and event your agent gets out of the box.

Add Header Rule

Tool to add a custom HTTP header rule to a Render service.

Add or Update Secret File

Tool to add or update a secret file for a Render service.

Add Resources to Environment

Tool to add resources to a Render environment.

Add Route

Tool to add redirect or rewrite rules to a Render service.

Create Custom Domain

Tool to add a custom domain to a Render service.

Create Environment Group

Tool to create a new environment group.

Create Environment

Tool to create a new environment within a Render project.

Create Postgres Instance

Tool to create a new Postgres instance on Render.

Create Registry Credential

Tool to create a registry credential.

Delete Environment Group Variable

Tool to remove an environment variable from an environment group.

Delete Environment Group Secret File

Tool to remove a secret file from an environment group.

Delete Environment

Tool to delete a specified environment.

Delete Key Value

Tool to delete a Key Value instance.

Delete Owner Log Stream

Tool to delete a log stream for an owner.

Delete Owner Metrics Stream

Tool to delete a metrics stream for a workspace.

Delete Registry Credential

Tool to delete a registry credential.

Delete Secret File

Tool to delete a secret file from a Render service.

Delete Service

Tool to delete a service.

Disconnect Blueprint

Tool to disconnect a blueprint from your Render account.

Get Active Connections

Tool to get active connection count metrics for Render resources.

Get Bandwidth Sources

Tool to get bandwidth usage breakdown by traffic source.

Get CPU Usage

Tool to retrieve CPU usage metrics for Render resources.

Get CPU Limit

Tool to retrieve CPU limit metrics for Render resources.

Get Disk Capacity

Tool to get disk capacity metrics for Render resources.

Get Disk Usage

Tool to retrieve disk usage metrics for Render resources.

Get Instance Count

Tool to get instance count metrics for Render resources.

Get Memory Usage

Tool to get memory usage metrics for one or more resources.

Get Memory Limit

Tool to get memory limit metrics for Render resources over a specified time range.

Get Memory Target

Tool to get memory target metrics for Render resources.

Get User

Tool to get the authenticated user.

Link Service to Environment Group

Tool to link a service to an environment group.

List Application Filter Values

Tool to list queryable instance values for application metrics.

List Blueprints

Tool to list all blueprints.

List Deploys

Tool to list recent deploys for a Render service with pagination and filtering.

List Disks

Tool to list all disks.

List Environment Groups

Tool to list environment groups.

List Environments

Tool to list environments for a project.

List Environment Variables for Service

Tool to list all environment variables configured directly on a Render service (with pagination).

List Instances

Tool to list instances of a service.

List Key Value Instances

Tool to list all Key Value instances.

List Logs

Tool to list logs for a specific workspace and resource.

List Log Label Values

Tool to list log label values for a workspace.

List Maintenance Runs

Tool to list maintenance runs.

List Notification Overrides

Tool to list notification overrides for services.

List Workspace Members

Tool to list workspace members.

List Owners

Tool to list owners (users and teams).

List Postgres Instances

Tool to list Postgres instances.

List Postgres Exports

Tool to list all exports for a Postgres instance.

List PostgreSQL Users

Tool to list PostgreSQL user credentials for a Render PostgreSQL database instance.

List Projects

List Projects

List Registry Credentials

Tool to list registry credentials.

List Resource Log Streams

Tool to list resource log stream overrides.

List Routes

Tool to list redirect/rewrite rules for a service.

List Secret Files

Tool to list secret files for a Render service.

List Services

Tool to list all services.

List Task Runs

Tool to list task runs.

List Tasks

Tool to list tasks.

List Webhooks

Tool to list all webhooks.

List Workflows

Tool to list workflows.

List Workflow Versions

Tool to list workflow versions.

Restart Service

Tool to restart a service.

Resume Service

Tool to resume a suspended service.

Retrieve Custom Domain

Tool to retrieve a specific custom domain for a service.

Retrieve deploy

Retrieve deploy

Retrieve Environment Group

Tool to retrieve a specific environment group by ID.

Retrieve Environment Variable

Tool to retrieve a specific environment variable from a Render environment group.

Retrieve Environment Group Secret File

Tool to retrieve secret file from an environment group.

Retrieve Environment Variable

Tool to retrieve a specific environment variable from a Render service.

Retrieve Owner

Tool to retrieve a specific owner (workspace) by ID.

Retrieve Owner Notification Settings

Tool to retrieve notification settings for a specific owner (workspace).

Retrieve Postgres Instance

Tool to retrieve a specific Postgres instance.

Retrieve Project

Tool to retrieve a specific project by ID.

Retrieve Registry Credential

Tool to retrieve a registry credential by ID.

Retrieve Secret File

Tool to retrieve a secret file from a Render service.

Retrieve Service

Tool to retrieve a specific service by ID.

Stream Task Runs Events

Tool to stream real-time task run events via Server-Sent Events (SSE).

Subscribe to Logs

Tool to subscribe to real-time logs via WebSocket connection.

Suspend Service

Tool to suspend a service.

Trigger Deploy

Tool to trigger a new deploy for a specified service.

Update Environment Group

Tool to update an environment group's name.

Update Environment Group Variable

Tool to add or update an environment variable in an environment group.

Update Environment Group Secret File

Tool to add or update a secret file in an environment group.

Update Environment Variable

Tool to add or update an environment variable for a Render service.

Update Environment Variables for Service

Tool to update environment variables for a Render service.

Update Header Rules

Tool to replace all header rules for a Render service.

Update Owner Log Stream

Tool to update log stream configuration for an owner.

Update Owner Notification Settings

Tool to update notification settings for a specific owner (workspace).

Update Postgres Instance

Tool to update a Postgres instance configuration.

Update Project

Tool to update a project's name.

Update Registry Credential

Tool to update a registry credential.

Update Resource Log Stream

Tool to update log stream override for a resource.

Update Routes

Tool to update redirect/rewrite rules for a service.

Update Secret Files for Service

Tool to update secret files for a Render service.

Update Service

Tool to update a service configuration.

Verify Custom Domain

Tool to verify DNS configuration for a custom domain.

FRAMEWORKS

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 Code logo

Claude Code

Use Render MCP with Claude Code

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

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

Frequently asked questions

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.

Yes, you can. LangChain 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.

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.

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.

Start with Render.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Render tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies