MCP.so
ログイン

Auto MCP Server

@brizzai

基本情報

カテゴリ

その他

ライセンス

Apache-2.0

トランスポート

stdio

作者

brizzai

Auto MCP Server について

Transform any OpenAPI/Swagger definition into a fully-featured Model Context Protocol (MCP) server

Auto MCP Server の設定

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

{
  "mcpServers": {
    "auto-mcp-brizzai": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "\\"
      ]
    }
  }
}

Auto MCP Server のツール

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

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

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

概要

What is Auto MCP?

Auto MCP transforms any OpenAPI/Swagger definition into a fully-featured Model Context Protocol (MCP) server. It reads a Swagger (OpenAPI v2) or OpenAPI v3 document, generates routes on-the-fly, proxies requests to an upstream endpoint, and exposes them through MCP via STDIO, HTTP (StreamableHttp), or SSE transport. Designed for developers who want to quickly wrap REST APIs as MCP tools for AI assistants like Claude.

How to use Auto MCP?

Use the MCP Config Builder to interactively edit endpoint descriptions and filter routes, then run Auto MCP with your swagger file and optional adjustment file. Deploy via CLI, Docker, inside Claude Desktop, or as a long‑running daemon. Configure with YAML, CLI flags, or environment variables (prefixed AUTO_MCP_).

Key features of Auto MCP

  • Zero boilerplate – bring a swagger.json and start serving
  • All MCP transport modes: stdio, http (StreamableHttp), sse
  • Pluggable auth: bearer token, basic auth, API keys, OAuth2, or none
  • Runtime configuration via YAML, CLI flags, or environment variables
  • MCP Config Builder for editing endpoint descriptions and filtering routes
  • Flexible deployment: CLI, Docker, Kubernetes, or within Claude Desktop

Use cases of Auto MCP

  • Rapid prototyping: wrap any REST API as an MCP server in seconds
  • Bridge legacy services: expose internal systems as MCP endpoints without rewriting
  • Access any 3rd‑party API from chat applications like Claude
  • Minimal proxy tools: proxy APIs that already handle validation and logic

よくある質問

1

What transport modes does Auto MCP support?

Auto MCP supports STDIO (default), HTTP (StreamableHttp – the newest MCP protocol), and SSE (self‑hosted long‑running event source).

2

What authentication methods are available?

Pluggable auth includes bearer token, basic auth, API keys, OAuth2 (including OAuth 2.1 with PKCE and dynamic client registration), or no auth.

3

How do I run Auto MCP inside Claude Desktop?

Add a Docker command to your Claude Desktop MCP Servers configuration, mounting your `swagger.json` and using the `--swagger-file` flag. Claude starts the container on‑demand over STDIO.

4

Can I customize how endpoints appear to LLMs?

Yes, the MCP Config Builder lets you edit endpoint descriptions, filter unnecessary routes, preview endpoints, and generate an adjustment file to apply customizations automatically.

5

What configuration methods are supported?

YAML file, CLI flags, or environment variables (prefixed `AUTO_MCP_`). For full details, see the project’s CONFIGURATION.md.

コメント

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