MCP server
by amrsa1
Integrate Swagger/OpenAPI with your REST API to explore endpoints, fetch docs, and execute authenticated requests easily
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.
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.
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.
MIT
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Swagger/OpenAPI for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Swagger/OpenAPI has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Swagger/OpenAPI is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Swagger/OpenAPI against two servers with overlapping tools; this profile had the clearer scope statement.
Swagger/OpenAPI reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Strong directory entry: Swagger/OpenAPI surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Swagger/OpenAPI has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired Swagger/OpenAPI into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend Swagger/OpenAPI for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Useful MCP listing: Swagger/OpenAPI is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 64
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.
Create an MCP configuration file in your IDE's configuration directory:
~/.vscode/mcp.json or .vscode/mcp.json (in your project)~/.cursor/mcp.json or .cursor/mcp.json (in your project)~/.windsurf/mcp.json or .windsurf/mcp.json (in your project)mcp.json (in your project root) or .mcp/config.json"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"
}
}
"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"
}
}
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 authenticationAPI_PASSWORD - Password for basic authenticationThe server intelligently handles authentication:
fetch_swagger_infoFetches and parses Swagger/OpenAPI documentation from a given URL to discover available API endpoints.
list_endpointsLists all available API endpoints after fetching Swagger documentation, showing methods, paths, and summaries.
get_endpoint_detailsGets detailed information about a specific API endpoint including parameters, request/response schemas, and examples.
execute_api_requestExecutes an API request to a specific endpoint with authentication, parameters, headers, and body handling.
validate_api_responseValidates an API response against the schema definitions from Swagger documentation to ensure compliance.
Once configured, you can use the MCP server in your AI-powered editor to:
The server automatically detects configuration files from:
.vscode/mcp.json).cursor/mcp.json).windsurf/mcp.json)mcp.json).mcp/config.json)# 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
MIT License - see LICENSE file for details.
Contributions are welcome! Please feel free to submit a Pull Request.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.