How to integrate Swaggerhub MCP with LlamaIndex

This guide walks you through connecting Swaggerhub to LlamaIndex 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 your orders api through natural language commands. This guide will help you understand how to give your LlamaIndex 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.

Swaggerhub logoSwaggerhub
Api Key

Swaggerhub is a collaborative API design and documentation platform built on OpenAPI. It accelerates API delivery, quality, and teamwork with powerful standards and workflow tools.

49 Tools

Introduction

This guide walks you through connecting Swaggerhub to LlamaIndex 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 your orders api through natural language commands.

This guide will help you understand how to give your LlamaIndex 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.

Also integrate Swaggerhub with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Swaggerhub
  • Connect LlamaIndex to the Swaggerhub MCP server
  • Build a Swaggerhub-powered agent using LlamaIndex
  • Interact with Swaggerhub through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Swaggerhub account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Swaggerhub

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Swaggerhub access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called swaggerhub_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["swaggerhub"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Swaggerhub actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, swaggerhub)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Swaggerhub tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Swaggerhub
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Swaggerhub tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Swaggerhub
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Swaggerhub, then start asking questions.

Complete Code

Here's the complete code to get you started with Swaggerhub and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["swaggerhub"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Swaggerhub actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Swaggerhub to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Swaggerhub tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Add Access Control for Teams

Tool to assign access control roles to teams on a SwaggerHub resource.

Add Access Control for Users

Tool to assign access control roles to users on a SwaggerHub resource.

Delete Table of Contents Entry

Tool to delete a table of contents entry from SwaggerHub portal.

Get Access Control Users

Tool to retrieve the list of users assigned access control on a SwaggerHub resource.

Get API Default Version

Tool to get the default version identifier of a SwaggerHub API.

Get API Versions

Tool to retrieve a list of API versions for a specific API in SwaggerHub.

Get Consumer Products

Tool to get a list of products that are visible to the consumer in a SwaggerHub portal.

Get API Definition

Tool to get the OpenAPI definition of a specified API version from SwaggerHub.

Get Domain Default Version

Tool to retrieve the default version identifier of a SwaggerHub domain.

Get domain definition

Tool to retrieve the OpenAPI definition of a specified domain version from SwaggerHub.

Get Domain JSON Definition

Tool to retrieve the OpenAPI definition for a specified domain version in JSON format.

Get Domain Lifecycle Settings

Tool to get the published status for a specific domain and version in SwaggerHub.

Get Domain Private Settings

Tool to retrieve the visibility (public or private) of a domain version in SwaggerHub.

Get Domain Versions

Tool to get a list of domain versions from SwaggerHub.

Get Domain YAML Definition

Tool to retrieve the OpenAPI definition for a specified domain version in YAML format from SwaggerHub.

Get JSON API Definition

Tool to download OpenAPI definition as a JSON file from SwaggerHub Portal API.

Get JSON Definition

Tool to get the OpenAPI definition for a specified API version in JSON format.

Get lifecycle settings

Tool to get the published status for the specified API and version.

Get Organization Members

Tool to retrieve a list of organization members and their roles from SwaggerHub.

Get User Organizations

Tool to get organizations for a user.

Get Organization Projects V2

Tool to get all projects of an organization in SwaggerHub.

Get Owner APIs

Tool to get a list of APIs for a specified owner in SwaggerHub.

Get owner domains

Tool to retrieve domains owned by a specific SwaggerHub user or organization.

Get Portal

Tool to retrieve information about a portal.

Get Portal Access Requests

Tool to retrieve access requests for a portal in SwaggerHub.

Get Portal Attachment

Tool to get informational attachment metadata from SwaggerHub Portal.

Get Portal Product

Tool to retrieve detailed information about a specific product resource.

Get Portal Products

Tool to get products for a specific portal that match your criteria.

Get Portals

Tool to search for available portals.

Get Portal Templates

Tool to get templates for a specific portal that match your criteria.

Get API Version Private Settings

Tool to get the visibility (public or private) of an API version.

List Resource Types and Roles

Tool to list available resource types and assignable roles for each in a SwaggerHub organization.

Get Templates

Tool to retrieve a list of templates for an owner in SwaggerHub.

Get User Roles

Tool to retrieve all roles assigned to a user across organization resources in SwaggerHub.

Get YAML API Definition

Tool to download OpenAPI definition as a YAML file from SwaggerHub Portal API.

Get YAML Definition

Tool to get the OpenAPI definition in YAML format for the specified API version from SwaggerHub.

List Attachments

Tool to retrieve all attachments for a portal or product.

Remove Access Control for Teams

Tool to remove access control for teams from a SwaggerHub resource.

Remove Access Control For Users

Tool to remove access control for users from a SwaggerHub organizational resource.

Remove Organization Members

Tool to remove members from a SwaggerHub organization.

Search APIs

Tool to search SwaggerHub APIs.

Search APIs and Domains

Tool to search SwaggerHub APIs, domains, and templates.

Search Domains

Tool to search SwaggerHub domains.

Search Published Portal

Tool to search published portal content.

Update Access Control for Teams

Tool to update access control roles for teams on a SwaggerHub resource.

Update Access Control for Users

Tool to update access control roles for users on a SwaggerHub resource.

Update Access Control for Teams

Tool to update access control for teams on a SwaggerHub resource.

Update Access Control Users

Tool to update access control roles for users on a SwaggerHub resource.

Update Portal

Tool to update specific portal information in SwaggerHub.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Swaggerhub.It takes 30 seconds.

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

Start building