Mcptoon

What mcptoon MCP server does

The mcptoon MCP server acts as a local decoupling layer for MCP tools. It does not bundle the third-party MCP servers you choose. Instead, you install those servers separately, register their commands or URLs with mcptoon, and let mcptoon expose a consolidated interface for discovery and calls.

By default, agents can read a compact names-only manifest rather than every registered tool schema. This is intended to reduce the context consumed by large MCP tool collections. The project reports a measured reduction from 71,929 to 581 tokens for a 255-tool benchmark, although results depend on the tools and tokenizer in use.

How it works

The mcptoon MCP server stores the local server configuration and connects to registered MCP servers when commands are run. mcptoon add registers a server, including stdio commands such as an npm-based server. mcptoon manifest lists available tools in a compact form, and mcptoon call invokes a selected tool with JSON arguments.

The serve command exposes the configured collection as one stdio MCP server. sync supports connecting agent configurations to the shared setup, while quickstart can discover servers already present on the machine, configure them, and list their tools. Output can use JSON, TOON, SLIM, or compact modes; --toon is available for reducing call-result size, and manifest --slim produces a smaller discovery representation.

Setup and configuration

Install the package with Python and add the servers you want to use:

pip install mcptoon
mcptoon add everything --stdio npx -y @modelcontextprotocol/server-everything
mcptoon manifest
mcptoon call everything echo '{"message":"hi"}'

mcptoon demo --quick provides a local demonstration without requiring an API key or one of the user's MCP servers. mcptoon demo-server provides an 11-tool demonstration server implemented with the Python standard library. The README also documents a Claude Code plugin that installs the CLI and configures the bridge, but the core workflow is available from the terminal.

Tools and capabilities

• Register MCP servers from stdio commands or URLs.
• Discover registered tools through a compact manifest.
• Call tools by server and tool name with JSON input.
• Serve all configured servers through one stdio MCP endpoint.
• Synchronize the shared configuration with supported agent workflows.
• Format discovery and call output as JSON, TOON, SLIM, or compact data.
• Run a local demonstration and view token-size comparisons.

Limitations and notes

mcptoon MCP server does not replace or install the MCP servers it manages. Those servers remain separate installations and must be supplied by the user. The project is local, requires no API key, and states that it sends no data to an external service. Benchmark reductions are measured examples rather than a guaranteed result for every tool collection. Removing mcptoon does not remove the separately installed MCP servers.