# How to integrate Swaggerhub MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Swaggerhub MCP with Vercel AI SDK v6", "toolkit": "Swaggerhub", "toolkit_slug": "swaggerhub", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/swaggerhub/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/swaggerhub/framework/ai-sdk.md", "updated_at": "2026-03-29T06:52:20.058Z" } ``` ## Introduction This guide walks you through connecting Swaggerhub to Vercel AI SDK v6 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 Vercel AI SDK 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 - [OpenAI Agents SDK](https://composio.dev/toolkits/swaggerhub/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/swaggerhub/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/swaggerhub/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/swaggerhub/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/swaggerhub/framework/codex) - [OpenClaw](https://composio.dev/toolkits/swaggerhub/framework/openclaw) - [Hermes](https://composio.dev/toolkits/swaggerhub/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/swaggerhub/framework/cli) - [Google ADK](https://composio.dev/toolkits/swaggerhub/framework/google-adk) - [LangChain](https://composio.dev/toolkits/swaggerhub/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/swaggerhub/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/swaggerhub/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/swaggerhub/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Swaggerhub integration - Using Composio's Tool Router to dynamically load and access Swaggerhub tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## 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 | Tool slug | Name | Description | |---|---|---| | `SWAGGERHUB_ADD_ACCESS_CONTROL_FOR_TEAMS` | Add Access Control for Teams | Tool to assign access control roles to teams on a SwaggerHub resource. Use when you need to grant team permissions (OWNER, DESIGNER, CONSUMER) for APIs, domains, projects, or portal products. | | `SWAGGERHUB_ADD_ACCESS_CONTROL_FOR_USERS` | Add Access Control for Users | Tool to assign access control roles to users on a SwaggerHub resource. Use when you need to grant user permissions (owner, designer, consumer) for APIs, domains, projects, organizations, teams, or portal products. | | `SWAGGERHUB_DELETE_TABLE_OF_CONTENTS_ENTRY` | Delete Table of Contents Entry | Tool to delete a table of contents entry from SwaggerHub portal. Use when you need to remove a table of contents entry by its ID. Optionally supports recursive deletion of nested entries. | | `SWAGGERHUB_GET_ACCESS_CONTROL_USERS` | Get Access Control Users | Tool to retrieve the list of users assigned access control on a SwaggerHub resource. Use when you need to check who has access to an API, domain, project, organization, team, or portal product. | | `SWAGGERHUB_GET_API_DEFAULT_VERSION` | Get API Default Version | Tool to get the default version identifier of a SwaggerHub API. Use when you need to know which version is marked as default for an API. This returns only the version identifier; to get the full API definition, use the version with GET /apis/{owner}/{api}/{version}. | | `SWAGGERHUB_GET_API_VERSIONS` | Get API Versions | Tool to retrieve a list of API versions for a specific API in SwaggerHub. Use when you need to get all versions of an API owned by an organization or user. Returns 404 if the specified API is not found or if the authenticated user does not have access to a private API. | | `SWAGGERHUB_GET_CONSUMER_PRODUCTS` | Get Consumer Products | Tool to get a list of products that are visible to the consumer in a SwaggerHub portal. Use when you need to retrieve products from a portal, including both accessible and inaccessible products. This endpoint does not require authentication. | | `SWAGGERHUB_GET_API_DEFINITION` | Get API Definition | Tool to get the OpenAPI definition of a specified API version from SwaggerHub. Use when you need to retrieve the complete API specification including endpoints, schemas, and documentation for a specific API version. | | `SWAGGERHUB_GET_DOMAIN_DEFAULT_VERSION` | Get Domain Default Version | Tool to retrieve the default version identifier of a SwaggerHub domain. Use when you need to know which version is set as default for a domain before fetching its definition. | | `SWAGGERHUB_GET_DOMAIN_DEFINITION` | Get domain definition | Tool to retrieve the OpenAPI definition of a specified domain version from SwaggerHub. Use when you need to access reusable domain components, schemas, or parameters. | | `SWAGGERHUB_GET_DOMAIN_JSON_DEFINITION` | Get Domain JSON Definition | Tool to retrieve the OpenAPI definition for a specified domain version in JSON format. Use when you need to access the domain definition document from SwaggerHub. | | `SWAGGERHUB_GET_DOMAIN_LIFECYCLE_SETTINGS` | Get Domain Lifecycle Settings | Tool to get the published status for a specific domain and version in SwaggerHub. Use when you need to check if a domain version is published or unpublished. | | `SWAGGERHUB_GET_DOMAIN_PRIVATE_SETTINGS` | Get Domain Private Settings | Tool to retrieve the visibility (public or private) of a domain version in SwaggerHub. Use when you need to check whether a specific domain version is accessible publicly or restricted to private access. | | `SWAGGERHUB_GET_DOMAIN_VERSIONS` | Get Domain Versions | Tool to get a list of domain versions from SwaggerHub. Use when you need to retrieve all versions of a domain definition and see which APIs reference it. The domain must exist and be accessible with the provided authentication. Returns domain information in APIs.json format including referencing APIs. | | `SWAGGERHUB_GET_DOMAIN_YAML_DEFINITION` | Get Domain YAML Definition | Tool to retrieve the OpenAPI definition for a specified domain version in YAML format from SwaggerHub. Use when you need to fetch domain schemas or API specifications in YAML format. | | `SWAGGERHUB_GET_JSON_API_DEFINITION` | Get JSON API Definition | Tool to download OpenAPI definition as a JSON file from SwaggerHub Portal API. Use when you need to retrieve the API specification in JSON format. | | `SWAGGERHUB_GET_JSON_DEFINITION` | Get JSON Definition | Tool to get the OpenAPI definition for a specified API version in JSON format. Use when you need to retrieve the complete API specification from SwaggerHub. Returns the OpenAPI/Swagger definition which includes paths, operations, schemas, and other API metadata. | | `SWAGGERHUB_GET_LIFECYCLE_SETTINGS` | Get lifecycle settings | Tool to get the published status for the specified API and version. Use when you need to check if an API version is published or unpublished. | | `SWAGGERHUB_GET_ORGANIZATION_MEMBERS` | Get Organization Members | Tool to retrieve a list of organization members and their roles from SwaggerHub. Use when you need to view member details including email addresses, roles, and last activity. The authenticating user must be the organization owner. | | `SWAGGERHUB_GET_USER_ORGANIZATIONS` | Get User Organizations | Tool to get organizations for a user. Use when you need to retrieve all organizations that the authenticating user is a member of. Results can be filtered by name using the q parameter, sorted by name or email, and paginated using page and pageSize parameters. | | `SWAGGERHUB_GET_ORGANIZATION_PROJECTS_V2` | Get Organization Projects V2 | Tool to get all projects of an organization in SwaggerHub. Use when you need to retrieve projects belonging to a specific organization. Projects organize APIs and domains into logical groups. Returns 403 if projects are not available in the organization's plan, or 404 if the organization is not found. | | `SWAGGERHUB_GET_OWNER_APIS` | Get Owner APIs | Tool to get a list of APIs for a specified owner in SwaggerHub. Use when you need to retrieve all APIs belonging to a specific user or organization. Results are returned in APIs.json format and can be paginated and sorted by various criteria. | | `SWAGGERHUB_GET_OWNER_DOMAINS` | Get owner domains | Tool to retrieve domains owned by a specific SwaggerHub user or organization. Use when you need to list all domains associated with an owner. | | `SWAGGERHUB_GET_PORTAL` | Get Portal | Tool to retrieve information about a portal. Use when you need to fetch details about a specific SwaggerHub portal by its UUID or subdomain. | | `SWAGGERHUB_GET_PORTAL_ACCESS_REQUESTS` | Get Portal Access Requests | Tool to retrieve access requests for a portal in SwaggerHub. Use when you need to list all users who have requested access to a portal's products, with optional filtering by status or search query. Returns paginated results with details about each request including user information, product, status, and timestamps. | | `SWAGGERHUB_GET_PORTAL_ATTACHMENT` | Get Portal Attachment | Tool to get informational attachment metadata from SwaggerHub Portal. Use when you need to retrieve details about a specific attachment by its UUID. This endpoint supports both authenticated and unauthenticated access for branding attachments or public product attachments. | | `SWAGGERHUB_GET_PORTAL_PRODUCT` | Get Portal Product | Tool to retrieve detailed information about a specific product resource. Use when you need to fetch complete details about a product using its UUID or portal-subdomain:product-slug identifier. | | `SWAGGERHUB_GET_PORTAL_PRODUCTS` | Get Portal Products | Tool to get products for a specific portal that match your criteria. Use when you need to retrieve a list of products from a portal, with optional filtering by name or slug and pagination support. | | `SWAGGERHUB_GET_PORTALS` | Get Portals | Tool to search for available portals. Returns portals where you have a designer role, either at the product level or organization level. | | `SWAGGERHUB_GET_PORTAL_TEMPLATES` | Get Portal Templates | Tool to get templates for a specific portal that match your criteria. Use when you need to list or search for templates within a portal by name or other filters. Supports pagination for large result sets. | | `SWAGGERHUB_GET_API_VERSION_PRIVATE_SETTINGS` | Get API Version Private Settings | Tool to get the visibility (public or private) of an API version. Use when you need to check whether a specific API version is publicly accessible or private. | | `SWAGGERHUB_LIST_RESOURCE_TYPES_AND_ROLES` | List Resource Types and Roles | Tool to list available resource types and assignable roles for each in a SwaggerHub organization. Use when you need to understand what roles can be assigned to different resource types like APIs, domains, projects, teams, and organizations. | | `SWAGGERHUB_GET_TEMPLATES` | Get Templates | Tool to retrieve a list of templates for an owner in SwaggerHub. Use when you need to get available templates for creating new API definitions or domain models. | | `SWAGGERHUB_GET_USER_ROLES` | Get User Roles | Tool to retrieve all roles assigned to a user across organization resources in SwaggerHub. Use when you need to check what permissions a user has across APIs, teams, domains, and other resources in an organization. | | `SWAGGERHUB_GET_YAML_API_DEFINITION` | Get YAML API Definition | Tool to download OpenAPI definition as a YAML file from SwaggerHub Portal API. Use when you need to retrieve the API specification in YAML format. | | `SWAGGERHUB_GET_YAML_DEFINITION` | Get YAML Definition | Tool to get the OpenAPI definition in YAML format for the specified API version from SwaggerHub. Use when you need to retrieve the API specification as YAML text for parsing, storage, or processing. | | `SWAGGERHUB_LIST_ATTACHMENTS` | List Attachments | Tool to retrieve all attachments for a portal or product. Use when you need to list attachments associated with either a specific portal or product. Provide either productId or portalId, not both. | | `SWAGGERHUB_REMOVE_ACCESS_CONTROL_FOR_TEAMS` | Remove Access Control for Teams | Tool to remove access control for teams from a SwaggerHub resource. Use when you need to revoke team permissions from an API, domain, project, or portal product. | | `SWAGGERHUB_REMOVE_ACCESS_CONTROL_FOR_USERS` | Remove Access Control For Users | Tool to remove access control for users from a SwaggerHub organizational resource. Use when you need to revoke user access to APIs, domains, projects, organizations, teams, or portal products. | | `SWAGGERHUB_REMOVE_ORGANIZATION_MEMBERS` | Remove Organization Members | Tool to remove members from a SwaggerHub organization. Use when you need to revoke membership for one or more users by their email addresses. | | `SWAGGERHUB_SEARCH_APIS` | Search APIs | Tool to search SwaggerHub APIs. Use when you need to find API definitions in SwaggerHub by name, owner, or other criteria. This is a convenience alias for GET /specs?specType=API. | | `SWAGGERHUB_SEARCH_APIS_AND_DOMAINS` | Search APIs and Domains | Tool to search SwaggerHub APIs, domains, and templates. Use when you need to retrieve a list of currently defined APIs, domains, and/or templates in APIs.json format. Supports filtering by spec type, visibility, state, owner, and free text search with pagination and sorting. | | `SWAGGERHUB_SEARCH_DOMAINS` | Search Domains | Tool to search SwaggerHub domains. Use when you need to find domain definitions in SwaggerHub by name, owner, or other criteria. This is a convenience alias for GET /specs?specType=DOMAIN. | | `SWAGGERHUB_SEARCH_PUBLISHED_PORTAL` | Search Published Portal | Tool to search published portal content. Use when you need to search for APIs, operations, schemas, or documents within a specific SwaggerHub portal. This endpoint does not require authentication for public content, but authentication provides access to private products within the API key's access boundary. | | `SWAGGERHUB_UPDATE_ACCESS_CONTROL_FOR_TEAMS` | Update Access Control for Teams | Tool to update access control roles for teams on a SwaggerHub resource. Use when you need to assign or change team permissions (designer or consumer) for APIs, domains, projects, or portal products. | | `SWAGGERHUB_UPDATE_ACCESS_CONTROL_FOR_USERS` | Update Access Control for Users | Tool to update access control roles for users on a SwaggerHub resource. Use when you need to assign or change user permissions (owner, designer, consumer) for APIs, domains, projects, organizations, teams, or portal products. | | `SWAGGERHUB_UPDATE_ACCESS_CONTROL_FOR_TEAMS` | Update Access Control for Teams | Tool to update access control for teams on a SwaggerHub resource. Use when you need to grant or modify team permissions for an API, domain, project, or portal product. | | `SWAGGERHUB_UPDATE_ACCESS_CONTROL_USERS` | Update Access Control Users | Tool to update access control roles for users on a SwaggerHub resource. Use when you need to change user permissions (CONSUMER, DESIGNER, or OWNER) for APIs, domains, projects, organizations, teams, or portal products. | | `SWAGGERHUB_UPDATE_PORTAL` | Update Portal | Tool to update specific portal information in SwaggerHub. Use when you need to modify portal settings such as name, branding, subdomain, or other configuration options. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Swaggerhub MCP server is an implementation of the Model Context Protocol that connects your AI agent to Swaggerhub. It provides structured and secure access so your agent can perform Swaggerhub operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Swaggerhub tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Swaggerhub-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["swaggerhub"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Swaggerhub tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to swaggerhub, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Swaggerhub tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript 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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n๐Ÿ‘‹ Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["swaggerhub"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to swaggerhub, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n๐Ÿ‘‹ Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Swaggerhub agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Swaggerhub MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/swaggerhub/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/swaggerhub/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/swaggerhub/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/swaggerhub/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/swaggerhub/framework/codex) - [OpenClaw](https://composio.dev/toolkits/swaggerhub/framework/openclaw) - [Hermes](https://composio.dev/toolkits/swaggerhub/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/swaggerhub/framework/cli) - [Google ADK](https://composio.dev/toolkits/swaggerhub/framework/google-adk) - [LangChain](https://composio.dev/toolkits/swaggerhub/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/swaggerhub/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/swaggerhub/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/swaggerhub/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### 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 Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)