hyper-mcp

What is hyper-mcp?

hyper-mcp is a wrapper that aggregates multiple Model Context Protocol (MCP) servers into a single unified interface, bypassing client-side tool limits and missing concepts. It is for users whose MCP client restricts the number or variety of tools available.

How to use hyper-mcp?

Install via npm (e.g., npx hyper-mcp). Configure by creating an mcp.json file (with a backup of any existing config). The server can also accept arguments or environment variables; arguments take precedence over environment variables over the config file at ~/.cursor/hyper.mcp.json.

Key features of hyper-mcp

• Aggregates tools from multiple MCP servers into one list
• Forwards commands to the respective MCP server
• Prefers arguments over environment variables over config file
• Validates configuration with a Zod schema
• Currently supports only static tools

Use cases of hyper-mcp

• Use a client that enforces a strict tool limit
• Unify tools from different MCP servers under a single interface
• Test or develop against multiple MCP servers without client restrictions

FAQ from hyper-mcp

Does hyper-mcp support dynamic tools?

No, currently only static tools are supported. Dynamic tool support is planned.

Where is the configuration file stored?

The default location is ~/.cursor/hyper.mcp.json. You can override it with arguments or environment variables.

How does hyper-mcp resolve configuration options?

It prefers command-line arguments, then environment variables, and finally the config file at ~/.cursor/hyper.mcp.json.

How do I install hyper-mcp?

Run npx hyper-mcp and create an mcp.json file with your server entries. Replace your existing Cursor config after backing it up.

Is hyper-mcp stable?

It is actively being developed and may change. The current version supports only static tools.