Swagger/OpenAPI MCP Server

Explore and interact with Swagger/OpenAPI specifications, allowing for browsing endpoints and retrieving details on API operations.

A Model Context Protocol (MCP) server that allows LLMs to explore and interact with Swagger/OpenAPI specifications. This server provides tools and resources for loading API specifications, browsing endpoints, and getting detailed information about API operations.
- Clone or create the project directory
- Install dependencies:

Load an OpenAPI/Swagger specification into the server.

- apiId(string): Unique identifier for this API
- source(string): URL or file path to the OpenAPI/Swagger specification

{ "name": "load_api", "arguments": { "apiId": "petstore", "source": "https://petstore.swagger.io/v2/swagger.json" } }

Get detailed information about a specific API endpoint.

- apiId(string): ID of the loaded API
- method(string): HTTP method (GET, POST, etc.)
- path(string): API endpoint path
- natural(boolean, optional): If true, returns a human-readable summary

{ "name": "get_endpoint_details", "arguments": { "apiId": "petstore", "method": "GET", "path": "/pet/{petId}", "natural": true } }

List all currently loaded API specifications.

Search for endpoints matching a specific pattern.

- apiId(string): ID of the loaded API
- pattern(string): Search pattern for endpoint paths or descriptions

{ "name": "search_endpoints", "arguments": { "apiId": "petstore", "pattern": "pet" } }

Get overview information about a loaded API specification.

Get a list of all available endpoints for an API.

swagger://{apiId}/endpoint/{method}/{path}

Get detailed information about a specific endpoint.

To use this server with Claude Desktop, add the following to yourclaude_desktop_config.json:

{ "mcpServers": { "swagger-explorer": { "command": "node", "args": ["/path/to/your/swagger-mcp-server/build/index.js"] } } }

Replace/path/to/your/swagger-mcp-serverwith the actual path to your project directory.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

A TypeScript MCP server to access Apifox API data via Stdio.

Provides API documentation from Apifox projects as a data source for AI programming tools that support MCP.

A tool to retrieve API interface information from YApi, with authentication configurable via environment variables.

Clix MCP Server for assisting Clix SDK/API integrations with semantic search across Clix docs and SDK source (iOS, Android, Flutter, React Native).

Check software end-of-life (EOL) dates and support status using the endoflife.date API to provide accurate lifecycle and security information.

Fetches API information from Feishu OpenAPI for seamless integration and management within an IDE.

Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding

Provides educational content, model information, and read-only API interactions for Lerian developers.