Docs
Run SimplyMCP
From a checkout of the proxy source (Node 20+), put the proxy between your MCP client and your server. Point your client at this command instead of the server's own command:
npx tsx src/cli.ts -- node /path/to/your-mcp-server.js
What happens
- Compress. tools/list schemas lose $schema, title copies, empty additionalProperties, markdownDescription, examples, outputSchema and _meta.
- Tier. The full catalog is stashed. The client gets a core set plus one local tool,
prestige_expand_tools. Lean lists stay a no-op. - Expand, then call.
prestige_expand_toolsis answered locally and not forwarded; it returns full schemas for hidden names. tools/call for any real upstream name still forwards byte-identical.
Options
npx tsx src/cli.ts --no-tier -- node /path/to/your-mcp-server.js npx tsx src/cli.ts --core-tools create_issue,search_code -- node /path/to/your-mcp-server.js npx tsx src/cli.ts --no-compress -- node /path/to/your-mcp-server.js PRESTIGE_TIERED=0 npx tsx src/cli.ts -- node /path/to/your-mcp-server.js
--no-tierorPRESTIGE_TIERED=0: turn tiering off.--core-tools a,b: choose the core set that stays in tools/list.--no-compress: turn compression off. Compression and tiering are independent.
JSON-RPC on stdout. Debug log on stderr.