MCP.so
ログイン

Swagger MCP Server

@danishjsheikh

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

danishjsheikh

投稿者

凯 田

Swagger MCP Server について

mcp server which will dynamically define tools based on swagger

Swagger MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "swagger_loader": {
      "command": "swagger-mcp",
      "args": [
        "--specUrl=<swagger/doc.json_url>"
      ]
    }
  }
}

Swagger MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is swagger-mcp?

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. It is designed for MCP clients to enable LLM-driven API interaction.

How to use swagger-mcp?

Install via go install github.com/danishjsheikh/swagger-mcp@latest, then run it with a spec URL. Use flags like --specUrl, --sse, --http, --security, and --includePaths to configure authentication, transports, and endpoint filtering. Integrate with MCP clients (e.g., mcphost) via a .mcp.json config.

Key features of swagger-mcp

  • Dynamically generates MCP tools from Swagger/OpenAPI specs
  • Supports Swagger 2.0 and OpenAPI 3.0
  • Handles path, query, header parameters and request bodies
  • Honors required/optional fields from schema required arrays
  • Runs in stdio, SSE, or StreamableHTTP mode
  • Supports authentication: basic, bearer, API key
  • Allows path/method include/exclude filtering

Use cases of swagger-mcp

  • Enable LLMs to call any API documented by an OpenAPI spec
  • Quickly prototype an MCP server for a REST API without manual coding
  • Filter specific endpoints or HTTP methods for focused LLM interactions
  • Integrate with MCP-compatible clients like mcphost for agentic workflows

よくある質問

1

What spec formats does swagger-mcp support?

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

2

What runtime dependencies are required?

An LLM model API key (OpenAI, Claude, or local models via Ollama) and any MCP client (e.g., `mcphost`). The server itself is a Go binary.

3

How do I pass authentication credentials?

Use the `--security` flag (`basic`, `bearer`, or `apiKey`) along with the corresponding flag (`--basicAuth`, `--bearerAuth`, or `--apiKeyAuth`). For API key, specify passAs (header/query/cookie) and the key-value pair.

4

Can I filter which endpoints become tools?

Yes, use `--includePaths` or `--excludePaths` for path filtering and `--includeMethods` or `--excludeMethods` for HTTP method filtering.

5

How does swagger-mcp handle request bodies?

Swagger 2.0 `in: body` parameters and OpenAPI 3.0 `requestBody.content.<media-type>.schema` are supported. Fields in the `required` array become required MCP tool arguments; others are optional.

コメント

「その他」の他のコンテンツ