Swagger MCP Server

mcp server which will dynamically define tools based on swagger

Local serverstdioGo

What is the Swagger MCP server?

Swagger MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. mcp server which will dynamically define tools based on swagger.

What you get

Supported spec formats: - Swagger 2.0 (swagger: "2.0") — path/query/header parameters and in: body request bodies - OpenAPI 3.0 (openapi: "3.0.x") — path/query/header parameters and requestBody with inline or $ref schemas

swagger-mcp is a tool that reads a Swagger 2.0 or OpenAPI 3.0 specification and dynamically generates MCP tools at runtime — one tool per API endpoint. These tools can be used by any MCP client for LLM-driven API interaction.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need one environment variable: XQUIK_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

To use swagger-mcp, ensure you have the following dependencies: 1. LLM Model API Key / Local LLM: Requires access to OpenAI, Claude, or Ollama models. 2. Any MCP Client: (Used mark3labs - mcphost)

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by danishjsheikh; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the swagger mcp server does with a few real requests.

How to install the Swagger MCP server

With bearer auth and path filtering:
```json
{
    "mcpServers": {
        "swagger_loader": {
            "command": "swagger-mcp",
            "args": [
                "--specUrl=https://api.example.com/openapi.json",
                "--security=bearer",
                "--bearerAuth=your-token-here",
                "--includeMethods=GET,POST"
            ]
        }
    }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

To use swagger-mcp, ensure you have the following dependencies: 1. LLM Model API Key / Local LLM: Requires access to OpenAI, Claude, or Ollama models. 2. Any MCP Client: (Used mark3labs - mcphost)

VariableDescriptionRequired
XQUIK_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

Swagger 2.0 (`swagger: "2.0"`) and OpenAPI 3.0 (`openapi: "3.0.x"`), including inline and `$ref` schemas for request bodies and parameters.