M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
H

HyperTool MCP

Community
Gateway / proxy
Give your AI the best tools from all your MCPs 🎯

This gateway aggregates or proxies other MCP servers; it only becomes useful once you connect real servers behind it.

How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #327 of 438
Stars
★ 155 Popular
Transport
stdio (local process)
Runtime
Node.js 18+
Credentials
No credential needed
License
Other / unspecified
Last commit
⚠
Tools
2
43FMRS · D

HyperTool MCP addresses a common pain point in AI tool management with dynamic toolsets, improving tool selection accuracy. Its persona feature accelerates setup. The context measurement feature is useful but should be treated as approximate.

Strongest · Documentation 11/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
8/20
Maintenance
8/20
Documentation
11/20
Setup experience
10/20
Why each score
Reliability 6/20
The source repository only includes README and manifest; no actual code, tests, or CI workflows are provided. The README describes features like dynamic tool registration and toolset switching, but there is no executable evidence that these work as described. Therefore, reliability is rated low because key paths are unverified and error handling is unknown.
Security and permissions 8/20
No obvious malicious code is present in the README. The server proxies multiple MCP servers and dynamically exposes tools, which involves managing credentials for various servers, but the README does not disclose how credentials are stored or if least privilege is applied. No evidence of irreversible operations by default. However, without source code review, security implementation details cannot be confirmed, so the score is conservative.
Maintenance 8/20
The repository has 155 stars and 9 open issues, but no data on commit frequency, release history, or issue response times. The license is marked 'NOASSERTION', which is concerning. Despite active development indicated by version 0.0.42, lack of license and versioning details lowers the score.
Documentation 11/20
The README is very detailed with quick start, feature list, FAQ, and screenshots. It provides configuration examples for various scenarios. However, there is a lack of in-depth documentation on advanced configuration, troubleshooting, and limitations. Some linked guides may not exist. Since no source code is available, documented features may be inaccurate.
Setup experience 10/20
The README provides clear installation steps: copy config, modify JSON, and use npx command. The example configuration is directly usable. However, automated setup tools are not detailed, and platform compatibility is not explicitly stated. Without actual testing, installation steps may fail in some environments.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or codeUses the network

Best for

  • Developers using AI coding assistants with multiple MCP servers
  • Teams looking to improve AI tool selection accuracy
  • Users who want to organize toolsets to match their workflows

Not for

  • Users with only one or two MCP servers and few tools
  • AI applications that don't require complex tool management

Required permissions

  • Read and write local configuration (~/.toolprint/hypertool-mcp/) to store toolsets and preferences
  • Launch and manage child processes to proxy MCP servers
  • Communicate with MCP clients over stdio

Risks and side effects

  • Proxied MCP servers may have permissions associated with their tools, such as filesystem access or remote API calls. Users should review the permissions granted to those servers.
  • Misconfiguration can lead to tools not being available. Ensure .mcp.hypertool.json is correctly formatted and contains valid server configurations.
  • Context measurement uses BPE-based approximations and is not exact token counts, so optimization decisions may not be precise.

Setup

Before you start

Runtime：Node.js 18+

  1. Copy your existing .mcp.json to .mcp.hypertool.json
  2. Replace .mcp.json with the HyperTool configuration as shown above
  3. Restart your AI client
  4. Create toolsets via interactive commands, e.g., "Create a toolset called 'coding' with git and docker tools"
claude_desktop_config.json 
{
  "mcpServers": {
    "hypertool": {
      "command": "npx",
      "args": [
        "-y",
        "@toolprint/hypertool-mcp",
        "mcp",
        "run",
        "--mcp-config",
        ".mcp.hypertool.json"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "hypertool": {
      "command": "npx",
      "args": [
        "-y",
        "@toolprint/hypertool-mcp",
        "mcp",
        "run",
        "--mcp-config",
        ".mcp.hypertool.json"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add hypertool -- npx -y @toolprint/hypertool-mcp mcp run --mcp-config .mcp.hypertool.json

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the hypertool entry to your client's mcpServers config and restarting, ask the AI to run 'list-available-tools'; if tools from your configured MCP servers appear with token estimates, the proxy is working.

Troubleshooting

  1. If the server doesn't start, check Node.js version is >=18 and validate the syntax of .mcp.hypertool.json.
  2. If tools aren't showing, ensure a toolset has been created and is active (use --equip-toolset).
  3. Check the configuration storage location and ensure files aren't edited while HyperTool is running.
  4. If a proxied server goes down, HyperTool will automatically reconnect, but you may need to check server health.

Things to try

Once connected, you can ask your AI assistant things like:

  • Create a toolset called 'coding' with git and docker tools
  • Switch to the coding toolset
  • Use list-available-tools to show token estimates for all tools
  • Show token usage of my currently equipped toolset with get-active-toolset

Tools 2

list-available-tools read-only
Lists all available tools with token estimates.
get-active-toolset read-only
Shows the current toolset and its token usage.

Use cases

Break free from tool limits when using more than 100 tools across multiple MCP servers
Create focused toolsets for specific tasks like development, writing, or debugging
Quickly start with pre-configured personas like web-dev or data-scientist
Measure context consumption per tool to optimize toolset design

Supported clients

Claude Desktop
Cursor
Claude CodePartial support

Listed from the project's documentation, not tested by this site.

Overview

HyperTool MCP is an MCP server that dynamically exposes tools from proxied servers based on an Agent Persona. It allows AI clients to connect to an unlimited number of MCP servers and organize their tools into focused toolsets (like playlists), overcoming tool count limits and improving tool selection accuracy. It supports pre-configured personas (e.g., web-dev, data-scientist) and context measurement to estimate token usage per tool.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 5a5175c61b35 Data synced 2026-10-19 Read the FMRS scoring method