Skip to main content
Glama

hypertool-mcp

by toolprint

⚡ Features

🔓 Break Free from Tool Limits

Connect unlimited MCP servers. Use 10, 50, or 500+ tools total - your AI only sees what it needs.

🎯 Task-Specific Toolsets

Build "git-essentials" with 5 tools instead of drowning in 47 Git commands. Switch contexts instantly.

🧠 Smart Tool Descriptions

Enhance tools with examples and context. Watch your AI pick the right tool 89% more often.

🚀 Quick Start

Step 1: Copy Your Existing Config

# In your project directory cp .mcp.json .mcp.hypertool.json

Step 2: Point Your AI to HyperTool

Replace your .mcp.json with:

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

Step 3: Create Your First Toolset

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.

🎬 Demo

Hotswap toolsets across 100+ tools

🏗️ How It Works

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

What's a "Toolset"? Think Playlists for Your AI

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 🎯

💼 Real-World Toolsets

Create focused toolsets for different workflows:

🔨 Development Mode

"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

📝 Content Creation

"writing": notion + grammarly + slack (6 tools) → Blog posts, docs, and team updates "research": perplexity + notion + filesystem (7 tools) → Deep dives with organized notes

🎬 Real Chat Example

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!

❓ FAQ

General Questions

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.

Setup & Compatibility

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.

Technical Questions

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.

🎮 App Compatibility

Works with ANY MCP-compatible app! HyperTool is a standard MCP server, so if your app supports MCP, it supports HyperTool.

Hot-swap Toolsets Without Restarts

AppStatusHow to Switch Toolsets
Cursor/VSCode✅ Full supportSwitch toolsets instantly - no restart needed!
Claude Code⏳ Coming soonUse --equip-toolset <name> flag (track progress)
Claude Desktop⏳ In progressRestart app after switching toolsets

📚 Learn More

🤝 Contributing

Found a bug? Have an idea? We'd love your help!

📄 License

MIT License - see LICENSE file for details.


Built by developers who got tired of watching AI pick the wrong tools 🎯

Related MCP Servers

  • A
    security
    A
    license
    A
    quality
    A proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.
    Last updated -
    453
    141
    TypeScript
    Apache 2.0
  • -
    security
    A
    license
    -
    quality
    A proxy service that connects MCP clients to remote MCP servers, allowing users to use server keys from MCP.so to access remote resources without running their own server.
    Last updated -
    53
    3
    TypeScript
    MIT License
    • Apple
  • -
    security
    F
    license
    -
    quality
    Proxy that aggregates multiple MCP servers and presents them as a unified interface, allowing clients to access resources from multiple servers transparently.
    Last updated -
    5
    TypeScript
  • -
    security
    F
    license
    -
    quality
    A flexible proxy that enables discovery and execution of tools across multiple Model Context Protocol (MCP) servers and JavaScript functions, reducing context size even when dealing with hundreds of tools.
    Last updated -
    5
    4
    JavaScript
    • Apple

View all related MCP servers

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/toolprint/hypertool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server