Connect unlimited MCP servers. Use 10, 50, or 500+ tools total - your AI only sees what it needs.
Build "git-essentials" with 5 tools instead of drowning in 47 Git commands. Switch contexts instantly.
Enhance tools with examples and context. Watch your AI pick the right tool 89% more often.
# In your project directory
cp .mcp.json .mcp.hypertool.jsonReplace your .mcp.json with:
{
"mcpServers": {
"hypertool": {
"command": "npx",
"args": ["-y", "@toolprint/hypertool-mcp", "--mcp-config", ".mcp.hypertool.json"]
}
}
}Restart your AI and try:
You: "Create a toolset called 'coding' with git and docker tools"
AI: "Created 'coding' toolset with 15 focused tools"
You: "Switch to coding toolset"
AI: "Equipped! I now have just the tools needed for development"
That's it! Your AI is now focused and effective. 🎉
💡 Want automated setup? Try our interactive setup command - see Advanced Guide for details.
📚 Configuration Mode: HyperTool uses a smart Configuration Mode to keep toolset management separate from your operational tools. Learn more in the Configuration Mode Guide.
Targeted toolsets across any number of MCPs. Swap to the best toolset for a goal with a tool call. Dynamic tool registration.
Before: Tool Chaos 😵
┌─────────────┐ ┌─────────────────────────────┐
│ Claude/ │──▶│ 50+ tools from 8 servers │
│ Cursor │ │ ❌ Wrong picks │
│ │ │ ❌ Slow decisions │
│ │ │ ❌ Confused context │
└─────────────┘ └─────────────────────────────┘
After: Expert Mode 🎯
┌─────────────┐ ┌──────────────┐ ┌─────────────────┐
│ Claude/ │──▶│ HyperTool │──▶│ ALL Your Tools │
│ Cursor │ │ (Local) │ │ (Same servers) │
└─────────────┘ └──────────────┘ └─────────────────┘
│
▼
┌─────────────────┐
│ Smart Toolsets │
│ 🔨 coding (5) │ ← "I'm coding now"
│ 📝 writing (3) │ ← "I'm writing now"
│ 📊 analysis (4) │ ← "I'm analyzing now"
└─────────────────┘
✅ Expert picks every time
Just like Spotify playlists organize your music, toolsets organize your AI tools:
ALL YOUR TOOLS (64 total) YOUR TOOLSETS
┌────────────────────────────┐ ┌──────────────────┐
│ 🐳 Docker (19 tools) │ │ 🔨 "coding" │
│ • build_image │ ┌───▶ │ • git.status │
│ • create_container │ │ │ • git.commit │
│ • run_container │ │ │ • docker.build │
│ • stop_container │ │ │ • docker.run │
│ • [... 15 more] │ │ │ • github.pr │
├────────────────────────────┤ │ └──────────────────┘
│ 🔀 Git (12 tools) │───┤
│ • status │ │ ┌──────────────────┐
│ • commit │ │ │ 📝 "writing" │
│ • push │ └───▶ │ • notion.create │
│ • [... 9 more] │ │ • slack.send │
├────────────────────────────┤ │ • grammarly.fix │
│ 📝 Notion (8 tools) │─────┐ └──────────────────┘
│ 💬 Slack (6 tools) │ │
│ 📊 Linear (10 tools) │ │ ┌──────────────────┐
│ 🧪 Testing (9 tools) │ └─▶ │ 🐛 "debugging" │
└────────────────────────────┘ │ • logs.search │
│ • docker.logs │
AI sees ALL 64 tools = confused 😵 │ • traces.view │
└──────────────────┘
AI sees 3-5 tools = focused 🎯
Create focused toolsets for different workflows:
"deep-coding": git + docker + filesystem (12 tools)
→ Everything you need for feature development
"code-review": git + github + linear (10 tools)
→ Review PRs, update tickets, merge with confidence
"debugging": logs + docker + traces + alerts (8 tools)
→ Find and fix issues fast
"writing": notion + grammarly + slack (6 tools)
→ Blog posts, docs, and team updates
"research": perplexity + notion + filesystem (7 tools)
→ Deep dives with organized notes
Organize your MCP servers into logical groups for easy management:
# Create a development group
hypertool-mcp mcp group create development -d "All development servers"
# Add servers to the group
hypertool-mcp mcp group add development git-server docker-server filesystem-server
# Run with a specific group
hypertool-mcp --group development
# List all groups
hypertool-mcp mcp group list
# Show servers in a group
hypertool-mcp mcp group show developmentServer groups make it easy to:
- 🚀 Launch related servers together
- 📊 Organize servers by project or environment
- 🔄 Switch between different server configurations
- 🎯 Maintain focused tool contexts
You: "I need to debug our API"
AI: "I'll switch to the debugging toolset for better focus"
[Now has: logs, traces, curl, docker]
You: "Actually, let's write the incident report"
AI: "Switching to writing toolset"
[Now has: notion, slack, templates]
💡 Pro tip: Start with 3-5 tools per toolset. Your AI will thank you!
Q: How is this different from just using MCP servers directly? A: HyperTool lets you use unlimited MCP servers without hitting the 100-tool limit, and dynamically switches between focused toolsets for better AI performance.
Q: Can I use multiple toolsets at once?
A: In stdio mode (default), use --equip-toolset <name> when launching. HTTP mode supports one active toolset but you can switch anytime.
Q: Where are my toolsets stored?
A: Locally in ~/.toolprint/hypertool-mcp/. Explore the directory to see your configurations.
Q: Does this work with Claude Desktop / Cursor / Claude Code? A: Yes! Cursor has full hot-swapping support. Claude Desktop works with restart. Claude Code hot-swap coming soon.
Q: What if an MCP server goes down? A: HyperTool monitors health and automatically reconnects when servers come back. Your toolsets stay intact.
Q: Can I share toolsets with my team? A: Import/export is coming soon! For now, you can copy and share toolset files - they'll work if your team has the same MCP servers configured.
Q: How do I add tools from a new MCP server?
A: Just add the server to your .mcp.hypertool.json config. It's automatically available for toolsets.
Q: Can I use this in production? A: Yes! For enterprise support, contact us.
Works with ANY MCP-compatible app! HyperTool is a standard MCP server, so if your app supports MCP, it supports HyperTool.
| App | Status | How to Switch Toolsets |
|---|---|---|
| Cursor/VSCode | ✅ Full support | Switch toolsets instantly - no restart needed! |
| Claude Code | ⏳ Coming soon | Use --equip-toolset <name> flag (track progress) |
| Claude Desktop | ⏳ In progress | Restart app after switching toolsets |
📚 Learn More
- 🔬 Research & Performance - Why focused toolsets work
- 🚀 Advanced Features - Tool annotations, HTTP mode, CLI
- 🔧 Troubleshooting - Common issues and solutions
- 📖 Examples & Recipes - Toolset patterns for every workflow
- Node.js 18+
- Python 3.8+ (for pre-commit hooks)
# Clone and install
git clone https://github.com/toolprint/hypertool-mcp.git
cd hypertool-mcp
just setup-dev # Installs dependencies and pre-commit hooksThis project uses pre-commit hooks to ensure code quality:
# Install pre-commit hooks (included in setup-dev)
just setup-pre-commit
# Run hooks manually
just pre-commit-check # On staged files
just pre-commit-check-all # On all files
# Skip hooks for emergency commits (use sparingly)
SKIP=eslint,typescript git commit -m "emergency fix"just build # Build the project
just test # Run tests
just lint # Run linting
just format # Format code
just typecheck # Check types
just pre-publish-checks # Run all quality checksThe hypertool-mcp service subcommand is currently disabled and will exit with a
notification when invoked.
Found a bug? Have an idea? We'd love your help!
MIT License - see LICENSE file for details.
Built by developers who got tired of watching AI pick the wrong tools 🎯
Built with ❤️ by Toolprint
© 2025 OneGrep, Inc.