How to integrate Agenty MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Agenty Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Agenty to Mastra AI using the Composio tool router. By the end, you'll have a working Agenty agent that can clone my top-performing agent for news sites, list all my running web scraping agents, create a new agent to monitor product prices, delete an outdated agent by its id through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Agenty account through Composio's Agenty MCP server.

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

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 Agenty tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Agenty 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 Agenty 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 Agenty MCP server, and what's possible with it?

The Agenty MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Agenty account. It provides structured and secure access to your web scraping agents and automation tools, so your agent can perform actions like creating, managing, cloning, and monitoring scraping agents, as well as handling API keys and templates—all on your behalf.

  • Agent creation and configuration: Instantly create new scraping or automation agents, set up their configurations, and optionally auto-start them—all without manual coding.
  • Clone and update agents: Duplicate existing agents to streamline workflows or update agent settings to refine your data extraction processes.
  • Fetch and manage agents: List all active agents in your account, retrieve details for any agent, and organize your entire automation fleet from a single place.
  • Template selection and management: Browse public agent templates or sample agents, making it easy to kickstart new projects or standardize scraping tasks.
  • API key management: Create, download, or delete API keys for secure programmatic access and efficient credential management, keeping your automation environment safe and organized.

Supported Tools & Triggers

Tools
Clone Agent by IDTool to clone an existing agent by its id.
Create AgentTool to create a new agent.
Get Agent TemplatesTool to fetch all public agent templates and sample agents.
Delete Agent by IDTool to delete a single agent by its id.
Fetch all agentsTool to fetch all active agents under an account.
Get Agent by IDTool to fetch details of a specific agent by its id.
Update Agent by IDTool to update an agent's configuration and settings by agent id.
Create API KeyTool to create a new api key.
Delete API key by IDTool to delete an api key by its key id.
Download API keysTool to download all api keys under an account in csv format.
Get all API keysTool to retrieve all api keys under an account.
Get API key by IDTool to get an api key by key id.
Reset API key by IDTool to reset an api key by key id.
Update API key by IDTool to update an api key by its id.
Change API key status by IDTool to enable or disable an api key by its id.
Get all connectionsTool to get all connections.
Create API KeyTool to create a new api key.
Get dashboard reports and usageTool to fetch account reports like pages used by agent, date, and product.
Get agent input by IDTool to get agent input by agent id.
Update Input by Agent IDTool to update agent input by agent id.
Download jobsTool to download all jobs in csv format.
Download job file by IDTool to download output files by job id.
Download Job Result by IDTool to download the agent output result by job id.
Fetch all jobsTool to fetch all jobs under an account.
Get Job by IDTool to fetch details of a specific job by its id.
Get Job Logs by IDTool to fetch logs for a given job by its id.
List job files by IDTool to list output files by job id.
Start Agent JobTool to start a new agent job.
Stop Job by IDTool to stop a running job by job id.
Clear List RowsTool to clear all rows in a list by its id.
Create ListTool to create a new list.
Delete List by IDTool to delete a specific list by its id.
Download listsTool to download all lists in csv format.
Get all listsTool to retrieve all lists under an account.
Fetch List Rows by IDTool to fetch all rows in a specified list.
Update List by IDTool to update a list's name or description by list id.
Upload CSV file to ListTool to upload a csv file to a list.
Add Agents to ProjectTool to add agent(s) to a project.
Create ProjectTool to create a new project.
Get all projectsTool to retrieve all projects under an account.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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 Agenty 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 Agenty

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

  const composioMCPUrl = session.mcp.url;
  console.log("Agenty MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "agenty" for Agenty 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 Agenty toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "agenty-mastra-agent",
    instructions: "You are an AI agent with Agenty 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: {
        agenty: 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 Agenty 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 Agenty 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: ["agenty"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "agenty-mastra-agent",
    instructions: "You are an AI agent with Agenty 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: { agenty: 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 Agenty 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 Agenty MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Agenty MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Agenty MCP with Claude Agent SDK

Google ADK

Google ADK

Use Agenty MCP with Google ADK

LangChain

LangChain

Use Agenty MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Agenty MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Agenty MCP with LlamaIndex

CrewAI

CrewAI

Use Agenty MCP with CrewAI

FAQ

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

With a standalone Agenty MCP server, the agents and LLMs can only access a fixed set of Agenty tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Agenty 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 Agenty tools.

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

Yes, absolutely. You can configure which Agenty 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 Agenty 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.

Book a call↗Get started for free