How to integrate Swaggerhub MCP with LlamaIndex

GET STARTED FOR FREE
Framework Integration Gradient
Swaggerhub Logo
LlamaIndex Logo
divider

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 my 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.

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.

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

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

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

  • composio-llamaindex: Composio's LlamaIndex integration
  • llama-index: Core LlamaIndex framework
  • llama-index-llms-openai: OpenAI LLM integration
  • llama-index-tools-mcp: MCP client for LlamaIndex
  • python-dotenv: Environment variable management

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

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

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

Key imports:

  • asyncio: For async/await support
  • Composio: Main client for Composio services
  • LlamaIndexProvider: Adapts Composio tools for LlamaIndex
  • ReActAgent: LlamaIndex's reasoning and action agent
  • BasicMCPClient: Connects to MCP endpoints
  • McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set in the environment")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment")

What's happening:

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

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["swaggerhub"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Swaggerhub actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Swaggerhub actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

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.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

  • We're creating a direct terminal interface to chat with your Swaggerhub database
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

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

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 asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["swaggerhub"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Swaggerhub actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Swaggerhub actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

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.

How to build Swaggerhub MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Swaggerhub MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Swaggerhub MCP with Claude Agent SDK

Google ADK

Google ADK

Use Swaggerhub MCP with Google ADK

LangChain

LangChain

Use Swaggerhub MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Swaggerhub MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Swaggerhub MCP with Mastra AI

CrewAI

CrewAI

Use Swaggerhub MCP with CrewAI

Claude Code

Claude Code

Use Swaggerhub MCP with Claude Code

Codex

Codex

Use Swaggerhub MCP with Codex

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 LlamaIndex?

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.

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.

Book a call↗Get started for free