MCP.so
ログイン

MCP Gateway

@mcp-ecosystem

基本情報

カテゴリ

クラウドとインフラ

ライセンス

MIT

トランスポート

stdio

作者

mcp-ecosystem

投稿者

lambda lambda

MCP Gateway について

🧩 MCP Gateway - A lightweight gateway service that instantly transforms existing MCP Servers and APIs into MCP servers with zero code changes. Features Docker deployment and management UI, requiring no infrastructure modifications.

MCP Gateway の設定

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

{
  "mcpServers": {
    "mcp-gateway": {
      "command": "fake-mcp-gateway"
    }
  }
}

MCP Gateway のツール

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

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

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

概要

What is MCP Gateway?

MCP Gateway (Unla) is a lightweight, highly available gateway service written in Go that allows individuals and organizations to convert existing MCP Servers and APIs into MCP Protocol–compliant endpoints through configuration only, with zero code changes. It is platform-agnostic and supports bare metal, VMs, ECS, and Kubernetes deployments.

How to use MCP Gateway?

Deploy with Docker using environment variables (secret key, admin credentials), then access the built-in web UI at port 8080 to add MCP Server configurations via YAML. After setup, use the exposed SSE or Streamable HTTP endpoints (port 5235) to connect your MCP client.

Key features of MCP Gateway

  • Convert RESTful APIs to MCP Servers via YAML configuration
  • Proxy existing MCP services without code changes
  • Support for MCP SSE and Streamable HTTP transports
  • Built-in management UI for configuration and monitoring
  • Multi-tenant support with persistent, recoverable sessions
  • OAuth-based pre-authentication for MCP Servers
  • Hot-reloading configuration from disk, SQLite, PostgreSQL, or MySQL

Use cases of MCP Gateway

  • Transform legacy REST APIs into MCP-compliant endpoints
  • Aggregate multiple MCP servers behind a single gateway
  • Enable multi-tenant access to MCP resources
  • Deploy MCP infrastructure without modifying existing code

よくある質問

1

Does MCP Gateway require code changes to my existing APIs or MCP Servers?

No. MCP Gateway is configuration-driven — you only need to provide a YAML configuration; no code changes are needed.

2

What deployment options are supported?

Docker, Kubernetes/Helm, bare metal, VMs, and ECS are all supported.

3

What MCP transport protocols does MCP Gateway support?

MCP Gateway supports both MCP SSE and MCP Streamable HTTP transports.

4

What backends can MCP Gateway use for configuration persistence?

It supports Disk, SQLite, PostgreSQL, and MySQL for storing and syncing configurations.

5

Does MCP Gateway support authentication for upstream MCP Servers?

Yes, it supports OAuth-based pre-authentication for MCP Servers.

コメント

「クラウドとインフラ」の他のコンテンツ