Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Dynamically expose tools from proxied servers based on an Agent Persona
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"hypertool": {
"command": "npx",
"args": [
"-y",
"@toolprint/hypertool-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add hypertool -- npx -y @toolprint/hypertool-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"hypertool": {
"command": "npx",
"args": [
"-y",
"@toolprint/hypertool-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"hypertool": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@toolprint/hypertool-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 toolprint.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.0.42)于14个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SuperCollider
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Give your AI the best tools from all your MCPs 🎯
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.json
Replace your .mcp.json with:
{
"mcpServers": { "hypertool": { "command": "npx", "args": ["-y", "@toolprint/hypertool-mcp", "mcp", "run", "--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.
Don't want to configure from scratch? Use personas - ready-to-use MCP server bundles with pre-built toolsets.
Think of personas as "app bundles" for your AI - they come with:
# 1. Clone the persona collection
git clone https://github.com/toolprint/awesome-mcp-personas
hypertool-mcp persona add awesome-mcp-personas/personas/web-dev
npx -y @toolprint/hypertool-mcp mcp run --persona web-dev
That's it! No server configuration needed. The persona brings its own servers and toolsets.
📦 Browse all available personas: awesome-mcp-personas
| Persona | Included Servers | Best For |
|---|---|---|
| web-dev | Git, Docker, Filesystem, Browser, Testing | Full-stack web development |
| data-scientist | Python, Jupyter, Database, Filesystem, Plotting | Data analysis & ML workflows |
| devops | Docker, Kubernetes, AWS, Terraform, Monitoring | Infrastructure & deployment |
| content-creator | Notion, Slack, Grammar, SEO, Social | Writing & content management |
| researcher | Perplexity, Arxiv, Wikipedia, Filesystem | Research & knowledge work |
# Standard Mode (use your existing MCP servers):
npx -y @toolprint/hypertool-mcp mcp run --mcp-config .mcp.hypertool.json
npx -y @toolprint/hypertool-mcp mcp run --persona web-dev
npx -y @toolprint/hypertool-mcp mcp run --persona web-dev --equip-toolset frontend
💡 Pro tip: Personas can be mixed with your existing servers! Add --mcp-config to include your custom servers alongside the persona's servers.
📚 Learn more: See the complete Personas Guide for detailed instructions, creating custom personas, and troubleshooting.
See exactly how much context each tool consumes. Optimize your toolsets with token estimates for every tool.
Active toolset showing token usage per tool
Why it matters:
How to use:
Ask your AI to use these MCP tools to see context information:
list-available-tools - Shows token estimates for all available toolsget-active-toolset - Shows token usage for your currently equipped toolsetEach tool displays estimated tokens and percentage of total context consumed. Perfect for building lean, efficient toolsets!
_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
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!
Explore everything HyperTool can do:
| Feature | Description | Guide |
|---|---|---|
| 🎭 Personas | Pre-configured MCP server bundles with curated toolsets. Get started instantly with ready-to-use workflows for web-dev, data science, DevOps, and more. | Personas Guide |
| 📁 Server Groups | Organize MCP servers into logical groups. Launch related servers together, switch between projects, and maintain focused contexts. | Advanced Guide |
| 📊 Context Measurement | See token estimates for every tool. Optimize your toolsets by understanding exactly how much context each tool consumes. | Context Measurement |
| 🔧 Configuration Mode | Smart separation of toolset management from operational tools. Keep your AI focused on work, not configuration. | Configuration Mode Guide |
| 🎯 Dynamic Toolsets | Build, modify, and switch between toolsets on the fly. Adapt your AI's capabilities to match your current task. | Examples & Recipes |
| 🧠 Tool Annotations | Enhance tools with custom descriptions, examples, and context. Improve your AI's tool selection accuracy by 89%. | Advanced Guide |
| 🚀 HTTP Mode | Run HyperTool as a long-lived HTTP server for persistent connections and faster response times. | Advanced Guide |
| 🔌 Unlimited Servers | Connect as many MCP servers as you need. Break free from the 100-tool limit without sacrificing performance. | Quick Start |
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: What's the difference between Personas and Standard Mode? A: Standard Mode uses your existing MCP server configurations. Personas are pre-packaged bundles that include both MCP servers AND curated toolsets - perfect for getting started quickly or trying new workflows.
*
只显示了开头部分;其余内容请在仓库中阅读