How to integrate Swaggerhub MCP with Mastra AI

Framework Integration Gradient
Swaggerhub Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Swaggerhub to Mastra AI using the Composio tool router. By the end, you'll have a working Swaggerhub agent that can list all apis i have access to, create a new api named petstore, update the description for my orders api through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Swaggerhub account through Composio's Swaggerhub 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 Swaggerhub tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Swaggerhub 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 Swaggerhub 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 Swaggerhub MCP server, and what's possible with it?

The Swaggerhub MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Swaggerhub account. It provides structured and secure access so your agent can perform Swaggerhub operations on your behalf.

Supported Tools & Triggers

Tools
Add Access Control for TeamsTool to assign access control roles to teams on a SwaggerHub resource.
Add Access Control for UsersTool to assign access control roles to users on a SwaggerHub resource.
Delete Table of Contents EntryTool to delete a table of contents entry from SwaggerHub portal.
Get Access Control UsersTool to retrieve the list of users assigned access control on a SwaggerHub resource.
Get API Default VersionTool to get the default version identifier of a SwaggerHub API.
Get API VersionsTool to retrieve a list of API versions for a specific API in SwaggerHub.
Get Consumer ProductsTool to get a list of products that are visible to the consumer in a SwaggerHub portal.
Get API DefinitionTool to get the OpenAPI definition of a specified API version from SwaggerHub.
Get Domain Default VersionTool to retrieve the default version identifier of a SwaggerHub domain.
Get domain definitionTool to retrieve the OpenAPI definition of a specified domain version from SwaggerHub.
Get Domain JSON DefinitionTool to retrieve the OpenAPI definition for a specified domain version in JSON format.
Get Domain Lifecycle SettingsTool to get the published status for a specific domain and version in SwaggerHub.
Get Domain Private SettingsTool to retrieve the visibility (public or private) of a domain version in SwaggerHub.
Get Domain VersionsTool to get a list of domain versions from SwaggerHub.
Get Domain YAML DefinitionTool to retrieve the OpenAPI definition for a specified domain version in YAML format from SwaggerHub.
Get JSON API DefinitionTool to download OpenAPI definition as a JSON file from SwaggerHub Portal API.
Get JSON DefinitionTool to get the OpenAPI definition for a specified API version in JSON format.
Get lifecycle settingsTool to get the published status for the specified API and version.
Get Organization MembersTool to retrieve a list of organization members and their roles from SwaggerHub.
Get User OrganizationsTool to get organizations for a user.
Get Organization Projects V2Tool to get all projects of an organization in SwaggerHub.
Get Owner APIsTool to get a list of APIs for a specified owner in SwaggerHub.
Get owner domainsTool to retrieve domains owned by a specific SwaggerHub user or organization.
Get PortalTool to retrieve information about a portal.
Get Portal Access RequestsTool to retrieve access requests for a portal in SwaggerHub.
Get Portal AttachmentTool to get informational attachment metadata from SwaggerHub Portal.
Get Portal ProductTool to retrieve detailed information about a specific product resource.
Get Portal ProductsTool to get products for a specific portal that match your criteria.
Get PortalsTool to search for available portals.
Get Portal TemplatesTool to get templates for a specific portal that match your criteria.
Get API Version Private SettingsTool to get the visibility (public or private) of an API version.
List Resource Types and RolesTool to list available resource types and assignable roles for each in a SwaggerHub organization.
Get TemplatesTool to retrieve a list of templates for an owner in SwaggerHub.
Get User RolesTool to retrieve all roles assigned to a user across organization resources in SwaggerHub.
Get YAML API DefinitionTool to download OpenAPI definition as a YAML file from SwaggerHub Portal API.
Get YAML DefinitionTool to get the OpenAPI definition in YAML format for the specified API version from SwaggerHub.
List AttachmentsTool to retrieve all attachments for a portal or product.
Remove Access Control for TeamsTool to remove access control for teams from a SwaggerHub resource.
Remove Access Control For UsersTool to remove access control for users from a SwaggerHub organizational resource.
Remove Organization MembersTool to remove members from a SwaggerHub organization.
Search APIsTool to search SwaggerHub APIs.
Search APIs and DomainsTool to search SwaggerHub APIs, domains, and templates.
Search DomainsTool to search SwaggerHub domains.
Search Published PortalTool to search published portal content.
Update Access Control for TeamsTool to update access control roles for teams on a SwaggerHub resource.
Update Access Control for UsersTool to update access control roles for users on a SwaggerHub resource.
Update Access Control for TeamsTool to update access control for teams on a SwaggerHub resource.
Update Access Control UsersTool to update access control roles for users on a SwaggerHub resource.
Update PortalTool to update specific portal information in SwaggerHub.

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 Swaggerhub 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 Swaggerhub

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

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

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

FAQ

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

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

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

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