Meta-Dynamic

Bundled MCP Connector - Think MCP-to-MCP. You will only need one SSE endpoint to your Claude config.

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

Meta-Dynamic MCP Server is a single proxy that aggregates multiple remote MCP endpoints and presents them through one unified SSE interface. It simplifies connecting an LLM client to many specialized MCP backends by handling transport, namespacing, and routing in one place.

How to use

You deploy Meta-Dynamic MCP Server to expose a single SSE endpoint that your MCP-capable client can subscribe to. Add each remote MCP you want to proxy in one centralized place, then point your client to the proxy at /sse. The proxy takes care of multiplexing requests to the appropriate backend and namespace them so tools and resources stay organized.

How to install

Prerequisites are Node.js version 16 or higher and npm (or Yarn). You also need one or more MCP servers you want to proxy.

Step-by-step commands to set up the project locally:

git clone <repo-url> meta-dynamic-server
cd meta-dynamic-server
npm install

Additional setup steps

Run the development server in watch mode to reload on changes, or build and run the compiled output for production.

npm run dev

npm run build
npm start

Configuration: adding remotes (MCP backends)

Add the MCP backends you want to proxy by listing them in the remotes configuration. Each remote needs a unique alias, a URL to the MCP endpoint, and the transport type you will use to communicate with it.

const remotes = [
  { name: "math",      url: "http://localhost:8083/mcp",  transport: "httpStream" },
  { name: "coingecko", url: "https://mcp.api.coingecko.com/sse", transport: "sse" },
  // add more MCP endpoints here
];

new MetaDynamicServer(remotes).start(8080);

Your proxy endpoints

The proxy exposes a single SSE stream at port 8080 by default and provides a POST path for messages. Use the following endpoints to interact with the proxy.

SSE stream URL: http://localhost:8080/sse

Message POST URL: http://localhost:8080/messages

Available tools

Resources API

Access and namespace lists such as resources/list and resources/read across proxied MCP servers.

Tools API

Aggregate tool usage and route tool invocations to the appropriate remote MCP.