Swagger/OpenAPI

Swagger/OpenAPI

amrsa1

Loads OpenAPI/Swagger documentation from any URL and lets you test API endpoints directly through the MCP interface. Supports multiple authentication methods and automatically detects IDE configurations.

Integrates with REST APIs through OpenAPI specifications to fetch documentation, explore endpoints, execute authenticated requests, and validate responses with support for multiple authentication methods.

71,972 views4Local (stdio)

What it does

  • Fetch OpenAPI/Swagger documentation from URLs
  • Test API endpoints with authentication
  • Explore API schemas and data structures
  • Execute authenticated HTTP requests
  • Validate API responses against schemas
  • Auto-discover documentation URLs

Best for

API developers testing endpoints during developmentQA engineers validating API behaviorIntegration developers exploring third-party APIsBackend developers documenting API interactions
Multi-IDE auto-discovery supportMultiple auth methods (API key, basic, bearer)Zero setup with npx

About Swagger/OpenAPI

Swagger/OpenAPI is a community-built MCP server published by amrsa1 that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate Swagger/OpenAPI with your REST API to explore endpoints, fetch docs, and execute authenticated requests easily It is categorized under developer tools.

How to install

You can install Swagger/OpenAPI in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

Swagger/OpenAPI is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

Swagger MCP Server

A Model Context Protocol (MCP) server that provides tools for exploring and testing APIs through Swagger/OpenAPI documentation. This server automatically detects configuration files from multiple IDEs and provides comprehensive API interaction capabilities.

Features

  • 🔍 Fetch and parse Swagger/OpenAPI documentation from any URL
  • 🧪 Test API endpoints directly through the MCP interface
  • 📊 Explore API schemas and understand data structures
  • 🔧 Multi-IDE support - automatically detects config from VS Code, Cursor, Windsurf, and more
  • 🌐 Flexible authentication - supports API keys, basic auth, and bearer tokens
  • Auto-discovery - can find documentation URLs automatically

Configuration

IDE Setup

Create an MCP configuration file in your IDE's configuration directory:

  • VS Code: ~/.vscode/mcp.json or .vscode/mcp.json (in your project)
  • Cursor: ~/.cursor/mcp.json or .cursor/mcp.json (in your project)
  • Windsurf: ~/.windsurf/mcp.json or .windsurf/mcp.json (in your project)
  • Any IDE: mcp.json (in your project root) or .mcp/config.json

Authentication Options

Option 1: Using API Key

"swagger-mcp": {
  "command": "npx",
  "args": [
    "-y",
    "swagger-mcp@latest"
  ],
  "env": {
    "API_BASE_URL": "https://api.example.com",
    "API_DOCS_URL": "https://api.example.com/swagger.json",
    "API_KEY": "your-api-key-here"
  }
}

Option 2: Using Username and Password

"swagger-mcp": {
  "command": "npx",
  "args": [
    "-y", 
    "swagger-mcp@latest"
  ],
  "env": {
    "API_BASE_URL": "https://api.example.com",
    "API_DOCS_URL": "https://api.example.com/swagger.json",
    "API_USERNAME": "your-username",
    "API_PASSWORD": "your-password"
  }
}

Configuration Options

  • API_BASE_URL - Base URL for your API (e.g., https://api.example.com) [Required]
  • API_DOCS_URL - Direct URL to Swagger/OpenAPI JSON/YAML (optional, will be auto-discovered)
  • API_KEY - API key for authentication (used as Bearer token)
  • API_USERNAME - Username for basic authentication
  • API_PASSWORD - Password for basic authentication

Authentication Flow

The server intelligently handles authentication:

  1. For API requests: Uses API_KEY as Bearer token, falls back to Basic auth
  2. For authentication endpoints: Auto-injects username/password credentials
  3. Token management: Automatically stores and reuses tokens from login responses
  4. Auto-refresh: Attempts to refresh tokens on 401 Unauthorized responses

Available Tools

fetch_swagger_info

Fetches and parses Swagger/OpenAPI documentation from a given URL to discover available API endpoints.

list_endpoints

Lists all available API endpoints after fetching Swagger documentation, showing methods, paths, and summaries.

get_endpoint_details

Gets detailed information about a specific API endpoint including parameters, request/response schemas, and examples.

execute_api_request

Executes an API request to a specific endpoint with authentication, parameters, headers, and body handling.

validate_api_response

Validates an API response against the schema definitions from Swagger documentation to ensure compliance.

Usage Examples

Once configured, you can use the MCP server in your AI-powered editor to:

  • Explore APIs: "Show me the available endpoints in this API"
  • Test endpoints: "Test the POST /users endpoint with this data"
  • Understand schemas: "Explain the User model structure"
  • Debug API calls: "Help me troubleshoot this API request"
  • Validate responses: "Check if this response matches the API schema"

Supported IDEs

The server automatically detects configuration files from:

  • VS Code (.vscode/mcp.json)
  • Cursor (.cursor/mcp.json)
  • Windsurf (.windsurf/mcp.json)
  • Root directory (mcp.json)
  • Alternative location (.mcp/config.json)

Development

# Clone the repository
git clone https://github.com/amrsa1/SwaggerMCP.git
cd SwaggerMCP

# Install dependencies
npm install

# Run in development mode
npm run dev

# Build for production
npm run build

License

MIT License - see LICENSE file for details.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Alternatives

Related Skills

Browse all skills
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
ai-sdk

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

6
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

4
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

3
ydc-ai-sdk-integration

Integrate Vercel AI SDK applications with You.com tools (web search, AI agent, content extraction). Use when developer mentions AI SDK, Vercel AI SDK, generateText, streamText, or You.com integration with AI SDK.

2