How to integrate Render MCP with Mastra AI

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

30 min · no commitment · see it on your stack

Render logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Render to Mastra AI 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 Mastra AI 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:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Render tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Render tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Render agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Render through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_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
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Render

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["render"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Render MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "render" for Render access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Render toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "render-mastra-agent",
    instructions: "You are an AI agent with Render tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

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

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;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        render: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Render toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["render"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      render: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "render-mastra-agent",
    instructions: "You are an AI agent with Render tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { render: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Render through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

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

LangChain logo

LangChain

Use Render MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Render MCP with Vercel AI SDK

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 Mastra AI?

Yes, you can. Mastra AI 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↗