McpHub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPHUB_CONFIG | No | Path to the McpHub configuration file. Defaults to ~/.mcp-hub/hub.json. | ~/.mcp-hub/hub.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_listA | 列出已安装的子 MCP、绑定策略与当前运行实例。 |
| mcp_getA | 查看某个子 MCP 的完整配置与实例 Key。 |
| mcp_installB | 安装(注册)一个子 MCP。strategy 可选 global / per_project / per_file;args/env/cwd 支持 ${PROJECT_ROOT} ${DB_PATH} 等模板。 |
| mcp_updateB | 修改子 MCP 配置;改动会自动重启该 MCP 的现有实例。 |
| mcp_removeB | 卸载子 MCP 并关闭它的全部实例。 |
| mcp_restartA | 重启指定子 MCP(不传 name 则重启全部),下次调用时按最新配置惰性重建。 |
| mcp_set_contextA | 设置默认项目上下文;后续 mcp_call 未显式传 project 时使用它。传空值则清除。 |
| mcp_toolsC | 发现某个子 MCP 暴露的工具。会按需启动该项目的实例。 |
| mcp_callB | 代理执行子 MCP 的工具。project 决定绑定到哪个项目(sqlite 会指向该项目的库文件)。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct operation: lifecycle CRUD, restart, context setting, tool discovery, and proxied invocation. list/get and tools/call are clearly separated by scope, so misselection is unlikely.
All tools use the mcp_ prefix and snake_case, and most follow a verb_noun or verb pattern. mcp_tools is noun-based while mcp_set_context is a longer verb phrase, which is a minor inconsistency.
Nine tools are well scoped for a sub-MCP manager: lifecycle operations, context, discovery, and invocation are all covered without filler. The count matches the server's purpose.
The surface covers CRUD lifecycle management plus restart, context, tool discovery, and proxied calls. Minor gaps exist around diagnostics/logs or explicit enable/disable controls, but core workflows are complete.