[{"_1":2,"_317":-5,"_318":-5},"loaderData",{"_3":4,"_22":23,"_24":25,"_263":264},"root",{"_5":6,"_7":8},"toasts",[],"visitor",{"_9":10,"_11":12},"viewportWidth",1280,"visitorSession",{"_13":14,"_16":17,"_18":-5,"_19":20,"_21":-5},"attributes",[15],"BOT","id",7058884,"membership","referenceId","01971406-43e3-74e8-b880-2f000258007a","userAccount","routes/_public/_layout",{},"routes/_public/mcp/servers/~namespace/~slug/_pages/_layout",{"_26":27,"_82":-5,"_83":40,"_29":84,"_179":180,"_261":262},"availableLocales",[28,40,47,54,61,68,75],{"_29":30,"_33":37,"_38":39},"mcpServer",{"_31":32,"_33":34,"_35":36},"description","Ein Proxyserver, der mehrere MCP-Server vereint und eine nahtlose Verwaltung von Tools, Eingabeaufforderungen und Ressourcen über die MetaMCP-App ermöglicht.","name","MetaMCP MCP-Server","readme","# MetaMCP MCP-Server\n\n : Das eine MCP zur Verwaltung all Ihrer MCPs\n\nDer MetaMCP MCP Server ist ein Proxyserver, der mehrere MCP-Server zu einem einzigen zusammenführt. Er ruft Tool-/Prompt-/Ressourcenkonfigurationen aus der MetaMCP-App ab und leitet Tool-/Prompt-/Ressourcenanfragen an den richtigen zugrunde liegenden Server weiter.\n\n[![Schmiedeabzeichen](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\nMetaMCP App-Repository: \n\n## Installation\n\n### Installation über Smithery\n\nManchmal funktioniert Smithery (lokal in Windsurf bestätigt), manchmal ist es aber instabil, da MetaMCP die Besonderheit hat, andere MCPs darauf laufen zu lassen. Falls dies nicht funktioniert, ziehen Sie bitte eine manuelle Installation in Erwägung.\n\nSo installieren Sie den MetaMCP MCP-Server für Claude Desktop automatisch über [Smithery](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp) :\n\n```bash\nnpx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude\n```\n\n### Manuelle Installation\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## Verwendung\n\n### Verwendung als Stdio-Server (Standard)\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### Verwendung als SSE-Server\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\nMit der SSE-Transportoption startet der Server einen Express.js-Webserver, der am `/sse` -Endpunkt auf SSE-Verbindungen wartet und am `/messages` -Endpunkt Nachrichten akzeptiert.\n\n### Verwendung mit Docker\n\nWenn Sie den Server in einem Docker-Container ausführen und eine Verbindung zu Diensten auf dem Hostcomputer herstellen, verwenden Sie die Option `--use-docker-host` um Localhost-URLs automatisch zu transformieren:\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\nDadurch werden alle localhost- oder 127.0.0.1-URLs in `host.docker.internal` umgewandelt, sodass der Container ordnungsgemäß eine Verbindung zu den auf dem Host ausgeführten Diensten herstellen kann.\n\n### Befehlszeilenoptionen\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio or sse) (default: \"stdio\")\n --port Port to use for SSE transport (default: \"12006\")\n --require-api-auth Require API key in SSE URL path\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n -h, --help display help for command\n```\n\n## Umgebungsvariablen\n\n* `METAMCP_API_KEY` : API-Schlüssel für MetaMCP\n* `METAMCP_API_BASE_URL` : Basis-URL für die MetaMCP-API\n* `USE_DOCKER_HOST` : Wenn auf „true“ gesetzt, werden localhost-URLs zur Docker-Kompatibilität in host.docker.internal umgewandelt\n\n## Entwicklung\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## Highlights\n\n* Kompatibel mit JEDEM MCP-Client\n* Mit der Multi-Workspaces-Ebene können Sie mit nur einem Klick zu einem anderen Satz von MCP-Konfigurationen wechseln.\n* Dynamische GUI-Updates von MCP-Konfigurationen.\n* Namespace-Isolierung für verbundene MCPs.\n\n## Architekturübersicht\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## Credits\n\n* Inspirationen und etwas Code (in diesem Projekt überarbeitet) von ","German","tag","de-DE",{"_29":41,"_33":45,"_38":46},{"_31":42,"_33":43,"_35":44},"A proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.","MetaMCP MCP Server","# MetaMCP MCP Server\n\n[https://metamcp.com](https://metamcp.com): The One MCP to manage all your MCPs\n\nMetaMCP MCP Server is a proxy server that joins multiple MCP⁠ servers into one. It fetches tool/prompt/resource configurations from MetaMCP App⁠ and routes tool/prompt/resource requests to the correct underlying server.\n\n[![smithery badge](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\n\n $\"MetaServer$ \n\n\nMetaMCP App repo: https://github.com/metatool-ai/metatool-app\n\n## Installation\n\n### Installing via Smithery\n\nSometimes Smithery works (confirmed in Windsurf locally) but sometimes it is unstable because MetaMCP is special that it runs other MCPs on top of it. Please consider using manual installation if it doesn't work instead.\n\nTo install MetaMCP MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp):\n\n```bash\nnpx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude\n```\n\n### Manual Installation\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## Usage\n\n### Using as a stdio server (default)\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### Using as an SSE server\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\nWith the SSE transport option, the server will start an Express.js web server that listens for SSE connections on the `/sse` endpoint and accepts messages on the `/messages` endpoint.\n\n### Using as a Streamable HTTP server\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport streamable-http --port 12006\n```\n\nWith the Streamable HTTP transport option, the server will start an Express.js web server that handles HTTP requests. You can optionally use `--stateless` mode for stateless operation.\n\n### Using with Docker\n\nWhen running the server inside a Docker container and connecting to services on the host machine, use the `--use-docker-host` option to automatically transform localhost URLs:\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\nThis will transform any localhost or 127.0.0.1 URLs to `host.docker.internal`, allowing the container to properly connect to services running on the host.\n\n### Configuring stderr handling\n\nFor STDIO transport, you can control how stderr is handled from child MCP processes:\n\n```bash\n# Use inherit to see stderr output from child processes\nmcp-server-metamcp --metamcp-api-key --stderr inherit\n\n# Use pipe to capture stderr (default is ignore)\nmcp-server-metamcp --metamcp-api-key --stderr pipe\n\n# Or set via environment variable\nMETAMCP_STDERR=inherit mcp-server-metamcp --metamcp-api-key \n```\n\nAvailable stderr options:\n- `ignore` (default): Ignore stderr output from child processes\n- `inherit`: Pass through stderr from child processes to the parent\n- `pipe`: Capture stderr in a pipe for processing\n- `overlapped`: Use overlapped I/O (Windows-specific)\n\n### Command Line Options\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio, sse, or streamable-http) (default: \"stdio\")\n --port Port to use for SSE or Streamable HTTP transport, defaults to 12006 (default: \"12006\")\n --require-api-auth Require API key in SSE or Streamable HTTP URL path\n --stateless Use stateless mode for Streamable HTTP transport\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n --stderr Stderr handling for STDIO transport (overlapped, pipe, ignore, inherit) (default: \"ignore\")\n -h, --help display help for command\n```\n\n## Environment Variables\n\n- `METAMCP_API_KEY`: API key for MetaMCP\n- `METAMCP_API_BASE_URL`: Base URL for MetaMCP API\n- `USE_DOCKER_HOST`: When set to \"true\", transforms localhost URLs to host.docker.internal for Docker compatibility\n- `METAMCP_STDERR`: Stderr handling for STDIO transport (overlapped, pipe, ignore, inherit). Defaults to \"ignore\"\n\n## Development\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## Highlights\n\n- Compatible with ANY MCP Client\n- Multi-Workspaces layer enables you to switch to another set of MCP configs within one-click.\n- GUI dynamic updates of MCP configs.\n- Namespace isolation for joined MCPs.\n\n## Architecture Overview\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## Credits\n\n- Inspirations and some code (refactored in this project) from https://github.com/adamwattis/mcp-proxy-server/","English","en-US",{"_29":48,"_33":52,"_38":53},{"_31":49,"_33":50,"_35":51},"Un servidor proxy que unifica múltiples servidores MCP, lo que permite una gestión fluida de herramientas, indicaciones y recursos a través de la aplicación MetaMCP.","Servidor MCP MetaMCP","# Servidor MCP MetaMCP\n\n : El único MCP para administrar todos sus MCP\n\nEl servidor MCP de MetaMCP es un servidor proxy que integra varios servidores MCP en uno solo. Obtiene las configuraciones de herramientas, avisos y recursos de la aplicación MetaMCP y dirige las solicitudes de herramientas, avisos y recursos al servidor subyacente correcto.\n\n[![insignia de herrería](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\nRepositorio de la aplicación MetaMCP: \n\n## Instalación\n\n### Instalación mediante herrería\n\nA veces, Smithery funciona (confirmado en Windsurf localmente), pero a veces es inestable porque MetaMCP es especial y ejecuta otros MCP sobre él. Si no funciona, considere instalarlo manualmente.\n\nPara instalar MetaMCP MCP Server para Claude Desktop automáticamente a través de [Smithery](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp) :\n\n```bash\nnpx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude\n```\n\n### Instalación manual\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## Uso\n\n### Usar como servidor stdio (predeterminado)\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### Uso como servidor SSE\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\nCon la opción de transporte SSE, el servidor iniciará un servidor web Express.js que escucha conexiones SSE en el punto final `/sse` y acepta mensajes en el punto final `/messages` .\n\n### Uso con Docker\n\nAl ejecutar el servidor dentro de un contenedor Docker y conectarse a los servicios en la máquina host, use la opción `--use-docker-host` para transformar automáticamente las URL del host local:\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\nEsto transformará cualquier URL localhost o 127.0.0.1 a `host.docker.internal` , lo que permitirá que el contenedor se conecte correctamente a los servicios que se ejecutan en el host.\n\n### Opciones de línea de comandos\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio or sse) (default: \"stdio\")\n --port Port to use for SSE transport (default: \"12006\")\n --require-api-auth Require API key in SSE URL path\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n -h, --help display help for command\n```\n\n## Variables de entorno\n\n* `METAMCP_API_KEY` : Clave API para MetaMCP\n* `METAMCP_API_BASE_URL` : URL base para la API de MetaMCP\n* `USE_DOCKER_HOST` : cuando se establece en \"verdadero\", transforma las URL del host local a host.docker.internal para compatibilidad con Docker\n\n## Desarrollo\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## Reflejos\n\n* Compatible con CUALQUIER cliente MCP\n* La capa de espacios de trabajo múltiples le permite cambiar a otro conjunto de configuraciones de MCP con un solo clic.\n* Actualizaciones dinámicas de GUI de configuraciones de MCP.\n* Aislamiento de espacio de nombres para MCP unidos.\n\n## Descripción general de la arquitectura\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## Créditos\n\n* Inspiraciones y algo de código (refactorizado en este proyecto) de ","Spanish","es-ES",{"_29":55,"_33":59,"_38":60},{"_31":56,"_33":57,"_35":58},"複数の MCP サーバーを統合し、MetaMCP アプリを介してシームレスなツール、プロンプト、およびリソース管理を可能にするプロキシサーバー。","MetaMCP MCP サーバー","# MetaMCP MCP サーバー\n\n : すべての MCP を管理できる 1 つの MCP\n\nMetaMCP MCPサーバーは、複数のMCPサーバーを1つに統合するプロキシサーバーです。MetaMCPアプリからツール/プロンプト/リソースの設定を取得し、ツール/プロンプト/リソースのリクエストを適切な基盤サーバーにルーティングします。\n\n[![鍛冶屋のバッジ](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\nMetaMCP アプリリポジトリ: \n\n## インストール\n\n### Smithery経由でインストール\n\nSmitheryは時々動作します（Windsurfでローカル環境で確認済み）。ただし、MetaMCPは他のMCPをその上で実行するという特殊な環境であるため、不安定になる場合があります。動作しない場合は、手動インストールをご検討ください。\n\n[Smithery](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)経由で Claude Desktop 用の MetaMCP MCP Server を自動的にインストールするには:\n\n```bash\nnpx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude\n```\n\n### 手動インストール\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## 使用法\n\n### stdio サーバーとして使用する (デフォルト)\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### SSEサーバーとして使用する\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\nSSE トランスポートオプションを使用すると、サーバーは`/sse`エンドポイントで SSE 接続をリッスンし、 `/messages`エンドポイントでメッセージを受け入れる Express.js Web サーバーを起動します。\n\n### Dockerでの使用\n\nDocker コンテナ内でサーバーを実行し、ホストマシン上のサービスに接続する場合は、 `--use-docker-host`オプションを使用して、localhost URL を自動的に変換します。\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\nこれにより、localhost または 127.0.0.1 の URL が`host.docker.internal`に変換され、コンテナがホスト上で実行されているサービスに適切に接続できるようになります。\n\n### コマンドラインオプション\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio or sse) (default: \"stdio\")\n --port Port to use for SSE transport (default: \"12006\")\n --require-api-auth Require API key in SSE URL path\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n -h, --help display help for command\n```\n\n## 環境変数\n\n* `METAMCP_API_KEY` : MetaMCPのAPIキー\n* `METAMCP_API_BASE_URL` : MetaMCP API のベース URL\n* `USE_DOCKER_HOST` : 「true」に設定すると、Docker との互換性のために localhost URL を host.docker.internal に変換します。\n\n## 発達\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## ハイライト\n\n* あらゆるMCPクライアントと互換性あり\n* マルチワークスペースレイヤーを使用すると、ワンクリックで別の MCP 構成セットに切り替えることができます。\n* MCP 構成の GUI 動的更新。\n* 結合された MCP の名前空間の分離。\n\n## アーキテクチャの概要\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## クレジット\n\n* からのインスピレーションと一部のコード（このプロジェクトでリファクタリング）","Japanese","ja-JP",{"_29":62,"_33":66,"_38":67},{"_31":63,"_33":64,"_35":65},"여러 개의 MCP 서버를 통합하는 프록시 서버로, MetaMCP 앱을 통해 원활한 도구, 프롬프트 및 리소스 관리를 가능하게 합니다.","MetaMCP MCP 서버","# MetaMCP MCP 서버\n\n : 모든 MCP를 관리할 수 있는 단일 MCP\n\nMetaMCP MCP 서버는 여러 MCP 서버를 하나로 연결하는 프록시 서버입니다. MetaMCP 앱에서 도구/프롬프트/리소스 구성을 가져와 도구/프롬프트/리소스 요청을 올바른 기본 서버로 라우팅합니다.\n\n[![대장간 배지](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\nMetaMCP 앱 저장소: \n\n## 설치\n\n### Smithery를 통해 설치\n\nSmithery가 작동하는 경우도 있지만(Windsurf 로컬에서 확인됨), MetaMCP가 다른 MCP를 실행하는 특수한 환경이라 불안정할 때도 있습니다. 작동하지 않으면 수동 설치를 고려해 보세요.\n\n[Smithery를](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp) 통해 Claude Desktop에 MetaMCP MCP 서버를 자동으로 설치하려면:\n\n지엑스피1\n\n### 수동 설치\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## 용법\n\n### stdio 서버로 사용(기본값)\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### SSE 서버로 사용\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\nSSE 전송 옵션을 사용하면 서버는 `/sse` 엔드포인트에서 SSE 연결을 수신하고 `/messages` 엔드포인트에서 메시지를 수락하는 Express.js 웹 서버를 시작합니다.\n\n### Docker와 함께 사용\n\nDocker 컨테이너 내부에서 서버를 실행하고 호스트 머신의 서비스에 연결하는 경우 `--use-docker-host` 옵션을 사용하여 로컬호스트 URL을 자동으로 변환합니다.\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\n이렇게 하면 모든 localhost 또는 127.0.0.1 URL이 `host.docker.internal` 로 변환되어 컨테이너가 호스트에서 실행되는 서비스에 적절하게 연결할 수 있습니다.\n\n### 명령줄 옵션\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio or sse) (default: \"stdio\")\n --port Port to use for SSE transport (default: \"12006\")\n --require-api-auth Require API key in SSE URL path\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n -h, --help display help for command\n```\n\n## 환경 변수\n\n* `METAMCP_API_KEY` : MetaMCP용 API 키\n* `METAMCP_API_BASE_URL` : MetaMCP API의 기본 URL\n* `USE_DOCKER_HOST` : \"true\"로 설정하면 Docker 호환성을 위해 localhost URL을 host.docker.internal로 변환합니다.\n\n## 개발\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## 하이라이트\n\n* 모든 MCP 클라이언트와 호환 가능\n* 다중 작업 공간 레이어를 사용하면 한 번의 클릭으로 다른 MCP 구성 세트로 전환할 수 있습니다.\n* MCP 구성의 GUI 동적 업데이트.\n* 결합된 MCP에 대한 네임스페이스 격리.\n\n## 아키텍처 개요\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## 크레딧\n\n* 에서 영감을 얻은 코드와 일부 코드(이 프로젝트에서 리팩토링됨)","Korean","ko-KR",{"_29":69,"_33":73,"_38":74},{"_31":70,"_33":71,"_35":72},"Прокси-сервер, объединяющий несколько серверов MCP, обеспечивая бесперебойное управление инструментами, подсказками и ресурсами через приложение MetaMCP.","MetaMCP MCP-сервер","# MetaMCP MCP-сервер\n\n : Единый MCP для управления всеми вашими MCP\n\nMetaMCP MCP Server — это прокси-сервер, который объединяет несколько серверов MCP⁠ в один. Он извлекает конфигурации инструментов/подсказок/ресурсов из MetaMCP App⁠ и направляет запросы инструментов/подсказок/ресурсов на правильный базовый сервер.\n\n[![значок кузнеца](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\nРепозиторий приложения MetaMCP: \n\n## Установка\n\n### Установка через Smithery\n\nИногда Smithery работает (подтверждено локально в Windsurf), но иногда он нестабилен, потому что MetaMCP особенный, он запускает другие MCP поверх себя. Пожалуйста, рассмотрите возможность ручной установки, если это не работает.\n\nЧтобы автоматически установить MetaMCP MCP Server для Claude Desktop через [Smithery](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp) :\n\n```bash\nnpx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude\n```\n\n### Ручная установка\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## Использование\n\n### Использование в качестве stdio-сервера (по умолчанию)\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### Использование в качестве сервера SSE\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\nПри использовании опции транспорта SSE сервер запустит веб-сервер Express.js, который прослушивает соединения SSE на конечной точке `/sse` и принимает сообщения на конечной точке `/messages` .\n\n### Использование с Docker\n\nПри запуске сервера внутри контейнера Docker и подключении к службам на хост-машине используйте параметр `--use-docker-host` для автоматического преобразования URL-адресов localhost:\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\nЭто преобразует все URL-адреса localhost или 127.0.0.1 в `host.docker.internal` , что позволит контейнеру правильно подключаться к службам, работающим на хосте.\n\n### Параметры командной строки\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio or sse) (default: \"stdio\")\n --port Port to use for SSE transport (default: \"12006\")\n --require-api-auth Require API key in SSE URL path\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n -h, --help display help for command\n```\n\n## Переменные среды\n\n* `METAMCP_API_KEY` : API-ключ для MetaMCP\n* `METAMCP_API_BASE_URL` : Базовый URL для API MetaMCP\n* `USE_DOCKER_HOST` : если установлено значение «true», URL-адреса localhost преобразуются в host.docker.internal для совместимости с Docker.\n\n## Разработка\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## Основные моменты\n\n* Совместимо с ЛЮБЫМ клиентом MCP\n* Слой Multi-Workspaces позволяет переключаться на другой набор конфигураций MCP одним щелчком мыши.\n* Динамические обновления конфигураций MCP через графический интерфейс.\n* Изоляция пространства имен для присоединенных MCP.\n\n## Обзор архитектуры\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## Кредиты\n\n* Вдохновение и немного кода (рефакторинг которого выполнен в этом проекте) с ","Russian","ru-RU",{"_29":76,"_33":80,"_38":81},{"_31":77,"_33":78,"_35":79},"统一多个 MCP 服务器的代理服务器，通过 MetaMCP App 实现无缝的工具、提示和资源管理。","MetaMCP MCP 服务器","# MetaMCP MCP 服务器\n\n ：一个 MCP 来管理您所有的 MCP\n\nMetaMCP MCP 服务器是一个代理服务器，它将多个 MCP 服务器合并为一个。它从 MetaMCP 应用获取工具/提示/资源配置，并将工具/提示/资源请求路由到正确的底层服务器。\n\n[![铁匠徽章](https://smithery.ai/badge/@metatool-ai/mcp-server-metamcp)](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)\n\nMetaMCP 应用程序仓库： \n\n## 安装\n\n### 通过 Smithery 安装\n\nSmithery 有时可以正常工作（已在 Windsurf 本地确认），但有时不稳定，因为 MetaMCP 比较特殊，它在其上运行其他 MCP。如果无法正常工作，请考虑手动安装。\n\n要通过[Smithery](https://smithery.ai/server/@metatool-ai/mcp-server-metamcp)自动为 Claude Desktop 安装 MetaMCP MCP 服务器：\n\n```bash\nnpx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude\n```\n\n### 手动安装\n\n```bash\nexport METAMCP_API_KEY=\nnpx -y @metamcp/mcp-server-metamcp@latest\n```\n\n```json\n{\n \"mcpServers\": {\n \"MetaMCP\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@metamcp/mcp-server-metamcp@latest\"],\n \"env\": {\n \"METAMCP_API_KEY\": \"\"\n }\n }\n }\n}\n```\n\n## 用法\n\n### 用作 stdio 服务器（默认）\n\n```bash\nmcp-server-metamcp --metamcp-api-key \n```\n\n### 用作 SSE 服务器\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006\n```\n\n使用 SSE 传输选项，服务器将启动一个 Express.js Web 服务器，该服务器监听`/sse`端点上的 SSE 连接并接受`/messages`端点上的消息。\n\n### 与 Docker 一起使用\n\n在 Docker 容器内运行服务器并连接到主机上的服务时，使用`--use-docker-host`选项自动转换 localhost URL：\n\n```bash\nmcp-server-metamcp --metamcp-api-key --transport sse --port 12006 --use-docker-host\n```\n\n这会将任何 localhost 或 127.0.0.1 URL 转换为`host.docker.internal` ，从而允许容器正确连接到主机上运行的服务。\n\n### 命令行选项\n\n```\nOptions:\n --metamcp-api-key API key for MetaMCP (can also be set via METAMCP_API_KEY env var)\n --metamcp-api-base-url Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)\n --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API\n --transport Transport type to use (stdio or sse) (default: \"stdio\")\n --port Port to use for SSE transport (default: \"12006\")\n --require-api-auth Require API key in SSE URL path\n --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)\n -h, --help display help for command\n```\n\n## 环境变量\n\n* `METAMCP_API_KEY` ：MetaMCP 的 API 密钥\n* `METAMCP_API_BASE_URL` ：MetaMCP API 的基本 URL\n* `USE_DOCKER_HOST` ：设置为“true”时，将 localhost URL 转换为 host.docker.internal 以实现 Docker 兼容性\n\n## 发展\n\n```bash\n# Install dependencies\nnpm install\n\n# Build the application\nnpm run build\n\n# Watch for changes\nnpm run watch\n```\n\n## 亮点\n\n* 与任何 MCP 客户端兼容\n* 多工作区层使您能够一键切换到另一组 MCP 配置。\n* MCP 配置的 GUI 动态更新。\n* 加入的 MCP 的命名空间隔离。\n\n## 架构概述\n\n```mermaid\nsequenceDiagram\n participant MCPClient as MCP Client (e.g. Claude Desktop)\n participant MetaMCP-mcp-server as MetaMCP MCP Server\n participant MetaMCPApp as MetaMCP App\n participant MCPServers as Installed MCP Servers in Metatool App\n\n MCPClient ->> MetaMCP-mcp-server: Request list tools\n MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status\n MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status\n\n loop For each listed MCP Server\n MetaMCP-mcp-server ->> MCPServers: Request list_tools\n MCPServers ->> MetaMCP-mcp-server: Return list of tools\n end\n\n MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists\n MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools\n\n MCPClient ->> MetaMCP-mcp-server: Call tool\n MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server\n MCPServers ->> MetaMCP-mcp-server: Return tool response\n MetaMCP-mcp-server ->> MCPClient: Return tool response\n```\n\n## 致谢\n\n* 灵感和一些代码（在本项目中重构）来自","Chinese","zh-CN","githubUser","locale",{"_85":86,"_87":88,"_13":102,"_111":42,"_112":42,"_113":114,"_117":118,"_141":-5,"_16":142,"_143":144,"_145":146,"_33":43,"_157":131,"_158":159,"_163":-5,"_164":165,"_166":-5,"_167":168,"_173":-5,"_153":127,"_174":-5,"_175":-5,"_132":176,"_177":178},"addedAt","2025-02-20T22:00:35.088088569Z","argumentsJsonSchema",{"_89":90,"_99":100,"_94":101},"properties",{"_91":92,"_96":97},"METAMCP_API_KEY",{"_31":93,"_94":95},"Required. Obtained from MetaMCP App's \"API Keys\" page (https://metamcp.com/api-keys).","type","string","METAMCP_API_BASE_URL",{"_31":98,"_94":95},"Optional override for MetaMCP App URL (e.g. http://localhost:12005).","required",[91],"object",[103,104,105,106,107,108,109,110],"category:code-execution","category:developer-tools","category:autonomous-agents","hosting:remote-capable","language:typescript","security_grade:a","quality_grade:a","license_grade:a","descriptionMarkdown","descriptionPlainText","githubProject",{"_35":44,"_115":116},"url","https://github.com/metatool-ai/mcp-server-metamcp","githubRepository",{"_119":120,"_121":122,"_123":124,"_125":126,"_33":127,"_128":129,"_134":135,"_136":137,"_139":140},"defaultBranch","main","fullName","metatool-ai/mcp-server-metamcp","githubTreeId",122930,"language","TypeScript","mcp-server-metamcp","owner",{"_130":131,"_132":133},"login","metatool-ai","uid","jmt0uamr5w","recentStargazers",6,"spdxLicense",{"_33":138},"Apache 2.0","stargazers",119,"glamaJson",1041,"inspectable",true,"integrations",[147],{"_148":149,"_31":155,"_132":156},"brand",{"_150":151,"_33":152,"_153":154},"logoSvgPath","M23.99 2.115A12.223 12.223 0 0 0 12 10.149 12.223 12.223 0 0 0 .01 2.115a12.23 12.23 0 0 0 5.32 10.604 6.562 6.562 0 0 1 2.845 5.423v3.754h7.65v-3.754a6.561 6.561 0 0 1 2.844-5.423 12.223 12.223 0 0 0 5.32-10.604Z","Mermaid","slug","mermaid","The README includes a Mermaid sequence diagram to illustrate the architecture of the MetaMCP MCP Server, showing how it interacts with MCP clients, the MetaMCP App, and installed MCP servers.","50v04qutdy","namespace","npmPackage",{"_33":160,"_161":162},"@metamcp/mcp-server-metamcp","weeklyDownloads",1489,"prompts","redditPostForeignId","1iuxbqe","resources","scores",{"_169":170,"_171":170,"_172":170},"license",100,"quality","security","simpleIcon","supportedPlatforms","tools","0po36lc7i6","updatedAt","2025-05-29T19:00:38.991991131Z","meta",[181,184,186,193,196,198,201,204,207,210,213,215,218,221,223,225,227,229,231],{"_182":183},"title","MetaMCP MCP Server | Glama",{"_185":42,"_33":31},"content",{"_187":188,"_189":190,"_191":192},"href","https://glama.ai/mcp/servers/@metatool-ai/mcp-server-metamcp","rel","canonical","tagName","link",{"_185":43,"_194":195},"property","og:title",{"_185":42,"_194":197},"og:description",{"_185":199,"_194":200},"https://glama.ai/logo.png","og:logo",{"_185":202,"_194":203},"https://glama.ai/mcp/servers/@metatool-ai/mcp-server-metamcp/og-image","og:image",{"_185":205,"_194":206},"630","og:image:height",{"_185":208,"_194":209},"1200","og:image:width",{"_185":211,"_194":212},"website","og:type",{"_185":188,"_194":214},"og:url",{"_185":216,"_194":217},"Glama – MCP Hosting Platform","og:site_name",{"_185":219,"_33":220},"summary_large_image","twitter:card",{"_185":216,"_33":222},"twitter:title",{"_185":42,"_33":224},"twitter:description",{"_185":202,"_33":226},"twitter:image",{"_185":205,"_33":228},"twitter:image:height",{"_185":208,"_33":230},"twitter:image:width",{"_232":233},"script:ld+json",{"_234":235,"_236":237},"@context","http://schema.org","@graph",[238],{"_234":239,"_240":241,"_242":243},"https://schema.org","@type","BreadcrumbList","itemListElement",[244,251,255,259],{"_240":245,"_246":247,"_33":248,"_249":250},"ListItem","item","https://glama.ai/","Glama","position",1,{"_240":245,"_246":252,"_33":253,"_249":254},"https://glama.ai/mcp","MCP",2,{"_240":245,"_246":256,"_33":257,"_249":258},"https://glama.ai/mcp/servers","Servers",3,{"_240":245,"_246":188,"_33":43,"_249":260},4,"visitorIsMaintainer",false,"routes/_public/mcp/servers/~namespace/~slug/_pages/reviews/_route",{"_82":-5,"_29":265,"_179":281,"_316":-5},{"_85":86,"_87":266,"_13":271,"_111":42,"_112":42,"_113":272,"_117":273,"_141":-5,"_16":142,"_143":144,"_145":276,"_33":43,"_157":131,"_158":279,"_163":-5,"_164":165,"_166":-5,"_167":280,"_173":-5,"_153":127,"_174":-5,"_175":-5,"_132":176,"_177":178},{"_89":267,"_99":270,"_94":101},{"_91":268,"_96":269},{"_31":93,"_94":95},{"_31":98,"_94":95},[91],[103,104,105,106,107,108,109,110],{"_35":44,"_115":116},{"_119":120,"_121":122,"_123":124,"_125":126,"_33":127,"_128":274,"_134":135,"_136":275,"_139":140},{"_130":131,"_132":133},{"_33":138},[277],{"_148":278,"_31":155,"_132":156},{"_150":151,"_33":152,"_153":154},{"_33":160,"_161":162},{"_169":170,"_171":170,"_172":170},[282,284,286,288,290,291,292,293,294,295,296,297,298,299,300,301,302,303,304],{"_182":283},"Reviews | MetaMCP MCP Server | Glama",{"_185":285,"_33":31},"Read community reviews and feedback for MetaMCP MCP Server. Discover user experiences, ratings, strengths, and potential limitations of this MCP implementation from actual users.",{"_187":287,"_189":190,"_191":192},"https://glama.ai/mcp/servers/@metatool-ai/mcp-server-metamcp/reviews",{"_185":289,"_194":195},"Reviews | MetaMCP MCP Server",{"_185":285,"_194":197},{"_185":199,"_194":200},{"_185":202,"_194":203},{"_185":205,"_194":206},{"_185":208,"_194":209},{"_185":211,"_194":212},{"_185":287,"_194":214},{"_185":216,"_194":217},{"_185":219,"_33":220},{"_185":216,"_33":222},{"_185":285,"_33":224},{"_185":202,"_33":226},{"_185":205,"_33":228},{"_185":208,"_33":230},{"_232":305},{"_234":235,"_236":306},[307],{"_234":239,"_240":241,"_242":308},[309,310,311,312,313],{"_240":245,"_246":247,"_33":248,"_249":250},{"_240":245,"_246":252,"_33":253,"_249":254},{"_240":245,"_246":256,"_33":257,"_249":258},{"_240":245,"_246":188,"_33":43,"_249":260},{"_240":245,"_246":287,"_33":314,"_249":315},"Reviews",5,"review","actionData","errors"]

Rate & Review

MCP directory API