Meta Mcp Proxy
@nullplatform
A flexible Model Context Protocol (MCP) proxy that enables discovery and execution of tools across multiple MCP servers and JavaScript functions. Enabling to have a reduced context event if you have houndreds of tools. This mcp act as wrapper of other mcps (or libraries) doing a
Overview
What is Meta Mcp Proxy?
Meta Mcp Proxy is a flexible Model Context Protocol (MCP) proxy that enables discovery and execution of tools across multiple MCP servers and JavaScript functions. It acts as a wrapper around other MCPs or libraries, doing a kind of local Retrieval Augmented Generation (RAG) to reduce context size by providing the LLM with two methods: discover and execute.
How to use Meta Mcp Proxy?
Install by adding a configuration entry to your Claude desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json) with the command npx and args ["@nullplatform/meta-mcp-proxy","-f","config.json"], then create a config.json file specifying discoverDescriptionExtras, discoverLimit, and an mcpServers object containing server definitions with command, args, env, and transport.
Key features of Meta Mcp Proxy
- Unified tool discovery across multiple MCP servers.
- Proxy execution of tool calls to the appropriate server.
- Smart search with fuzzy matching for finding the best tool.
- Expose custom JavaScript functions as MCP tools.
- Configurable via files or command-line arguments.
Use cases of Meta Mcp Proxy
- Aggregating dozens of MCP servers into a single interface to avoid context overload.
- Enabling an LLM to discover relevant tools from a large toolset without sending all tool definitions.
- Wrapping custom JavaScript libraries as MCP tools for AI consumption.
FAQ from Meta Mcp Proxy
How does Meta Mcp Proxy reduce context size?
It provides the LLM with only two methods (discover and execute) and asks the LLM to be concise about discovery, using a local RAG approach to retrieve relevant tools on demand.
What is the configuration file format?
The config.json should include discoverDescriptionExtras (recommended), discoverLimit, and an mcpServers object where each server defines command, args, env, and transport (defaults to stdio).
What runtime dependencies does Meta Mcp Proxy require?
It is installed via npx, so Node.js and npm are required. The proxy itself runs JavaScript and can execute other MCP servers defined in configuration.
Does Meta Mcp Proxy support authentication or custom transports?
Yes, each MCP server in the configuration can include environment variables (env) and specify a transport type (currently shown as "stdio" in examples).
How do I help the LLM choose the right tool?
Set discoverDescriptionExtras in configuration to provide detailed context about the purpose of the tools and for what topics the LLM should use them.
