MCP of Mcps
Merge every MCP server into one endpoint, and let tools pass data to each other without going through the model.Read full description
eliavamarLABSCO SUMMARY
Exposing it on the network is two decisions, not one.
serve executes your local code when a tool is called, so it stays on loopback until you pass --host. Before you do, set keys: any non-empty value in MCP_GEN_API_KEYS turns bearer auth on, and a bad token is rejected with 401 before the transport, so no tool code runs. Use the environment variable rather than --api-key in production — a flag is visible to anyone who can list processes.
What it is
A generator that reads your exported TypeScript functions and derives MCP tool, resource and prompt definitions from them. The type checker produces the JSON Schema and the JSDoc produces the descriptions, so nothing is added to your code.
What you get
mcp-gen <file.ts>emits the tool schemas as JSON on stdout, with parameter names, types, required-ness and descriptions all taken from the codemcp-gen devopens a live playground that watches the file, renders an input form per tool, runs it in the browser and shows the result, the generatedinputSchemaand the raw JSON-RPCmcp-gen serveruns a real MCP server;mcp-gen checksnapshots the tool surface and fails a build on breaking changes- Resources and prompts from the same exports — a
@resourcetag with a URI (templated when the placeholders match parameter names), a@prompttag for reusable templates, and an untagged function stays a tool - Fail-loud handling: a function that cannot be converted to valid schema is excluded and reported rather than emitted broken, and the exit code tells you which case you hit
Requirements
The npm package @zodromon/mcp-gen, version 1.2.0, installed globally or run through npx; the command is mcp-gen either way. Requires Node.js, and depends on the MCP SDK, ts-morph, typescript and jiti. serve binds 127.0.0.1 and port 3000 by default, and dev uses port 4000.
Setup effort
One command — npm install -g @zodromon/mcp-gen
USE CASES
01
Exposing functions you already wrote as tools
Point the generator at the file; the schema comes from the types you already declared.
02
Trying a tool before wiring up a client
The playground renders a form from the inferred schema and runs the tool through the same path the server uses.
03
Stopping a tool contract from changing silently
Snapshot the surface and fail CI on a removal, a rename or a new required parameter.
04
Publishing data and prompt templates too
Tag a function as a resource with a URI, or as a prompt, and it registers alongside the tools.
BEFORE YOU INSTALL
What to know first
Requires
npm on PATH
INSTALLATION
Connect your client
This project publishes no client configuration, so the entry for your client is yours to write.
Server setup
TERMINAL
npm install -g @zodromon/mcp-gen
