hyper-mcp
About
Unlocks all of MCP for your favourite agent 🌩️
Details
- Author
- kranners
- Downloads
- 375
- Categories
- Other, AI
Jump to
- 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
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
hyper-mcpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
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.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"hyper-mcp": {
"hyper": {
"command": "npx",
"args": [
"hyper-mcp"
]
}
}
}
}McpServers
{
"hyper": {
"command": "npx",
"args": [
"hyper-mcp"
]
}
}hyper-mcp
A MCP server wrapper for using the entire Model Context Protocol without tool
limits or missing concepts.
See the Model Context Protocol documentation to see what your MCP client of choice is lacking.
> [!WARNING]
> This tool is actively being developed, and currently only supports static tools.
Installation
Example installation will be assuming you're using Cursor.
1. Start by making a backup of your current mcp.json file.
> [!TIP]
> The default location is ~/.cursor/hyper.mcp.json.
> To rename your existing Cursor config:
> mv ~/.cursor/mcp.json ~/.cursor/hyper.mcp.json
2. Create a new mcp.json file where the old one was, with these contents:
{
"mcpServers": {
"hyper": {
"command": "npx",
"args": [
"hyper-mcp",
],
}
}
}
The server will prefer arguments over environment variables over
~/.cursor/hyper.mcp.json.
TODO
Need to:
- [x] Read in the config file (mcp.json), can take in an argument or a env var
- [x] Validate it's in the correct format (zod schema)
Startup
- [x] Load a new client for each MCP entry - [x] List all tools - [x] Add all those to a registerRuntime
- [x] Expose that list via the tools endpoint - [x] Take in commands - [x] Forward them through to the respective MCP server - [x] Forward the results backSupport
- [ ] Update transport command to support Nix, etc - [ ] Update connections to pass through MCP host environment (is this needed?) - [ ] Update tools to support dynamic tools, eg changingSpice
- [ ] CI & releases - [ ] Support SSE servers - [ ] Also load all prompts & resources - [ ] Optionally blacklist or prefer tools - [ ] Expose all of the other things as well - [ ] Instructions tool, configurable help message - [ ] Templatable help message?Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
