Hypertool Mcp
Compose many upstream MCP servers behind one stdio proxy that exposes only the tools matching an Agent Persona so agents stay focused and within context limits.
Overview
ai.toolprint/hypertool-mcp is a MCP server for the Build phase that proxies other MCP servers and dynamically exposes only persona-matched tools over stdio.
What is this MCP server?
- npm package @toolprint/hypertool-mcp v0.0.42 with stdio transport for local MCP clients
- Dynamically surfaces tools from proxied MCP servers based on a defined Agent Persona
- Reduces tool sprawl by hiding irrelevant upstream capabilities from the active agent
- Open-source repository at github.com/toolprint/hypertool-mcp
- Fits multi-server agent setups where persona-specific tool subsets matter
- Published npm version 0.0.42
- Transport: stdio only in catalog schema
- Package identifier: @toolprint/hypertool-mcp
Community signal: 154 GitHub stars.
What problem does it solve?
Your agent sees every tool from every connected MCP server and loses focus or hits context limits when personas should only use a curated slice.
Who is it for?
Solo builders running multiple MCP backends who want persona-based tool gating without forking each upstream server.
Skip if: Single-tool MCP setups, teams that need a hosted HTTP-only remote with no local Node process, or builders who want static tool lists with zero proxy layer.
What do I get? / Deliverables
After you install the npm package and define Agent Personas, one Hypertool MCP endpoint presents a filtered, persona-appropriate tool set from your proxied servers.
- Running Hypertool stdio MCP process wired to proxied servers
- Persona definitions that control which upstream tools appear to the agent
Recommended MCP Servers
Journey fit
Hypertool sits where you integrate external tool surfaces into your agent stack during product build, before you ship hardened production routing. Persona-filtered proxying of proxied MCP servers is classic integration work: wiring tool catalogs, not writing frontend or running prod monitoring.
How it compares
MCP aggregation and persona filter proxy, not a domain API skill or hosted SaaS remote.
Common Questions / FAQ
Who is ai.toolprint/hypertool-mcp for?
Developers building agent workflows on Claude Code or Cursor who proxy several MCP servers and need persona-scoped tool exposure.
When should I use ai.toolprint/hypertool-mcp?
Use it while integrating agent tooling when tool catalogs grow large and you want each agent mode to see only relevant proxied tools.
How do I add ai.toolprint/hypertool-mcp to my agent?
Install @toolprint/hypertool-mcp from npm (0.0.42), run the stdio server per repository docs, configure proxied MCP servers and personas, then register that stdio command in your MCP client config.