mcp-hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port (default 80 in the image, 3000 outside) | 80 |
| PASSWORD | No | Plain-text alternative to PASSWORD_HASH | |
| DATA_PATH | No | Path to data directory (default /data) | /data |
| CONFIG_PATH | No | Path to config file (default /config/mcp.json) | /config/mcp.json |
| EXTERNAL_URL | Yes | Public base URL, e.g. https://mcp.example.net (no path) | |
| PASSWORD_HASH | No | bcrypt hash of the login password (htpasswd -bnBC 10 "" 'pw' | tr -d ':\n') | |
| TRUSTED_PROXIES | No | Comma-separated IPs/CIDRs allowed to set X-Forwarded-* |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversA | List all MCP servers available through this hub, with their status. Call this first to see what is available. Servers marked "hidden" serve their tools only via their own endpoint, but wake_server/sleep_server still manage them. |
| list_toolsA | List the tools of one MCP server with one-line descriptions. Use get_tool_schema before calling a tool for the first time. |
| get_tool_schemaA | Get the full description and JSON input schema of one tool, needed to construct arguments for call_tool. |
| call_toolA | Call a tool on one of the MCP servers. Arguments must match the schema from get_tool_schema. |
| wake_serverA | Start an on-demand server now so its first tool call is fast. No-op if it is already running. |
| sleep_serverA | Stop an on-demand server immediately instead of waiting for its idle timeout. It restarts automatically on the next tool call. |
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 6 tools
Each tool targets a distinct resource+action pair: list_servers (servers), list_tools (tools of a server), get_tool_schema, call_tool, wake_server, sleep_server. The only surface overlap (list_servers vs list_tools) is explicitly disambiguated by descriptions and different scopes.
All names follow a consistent snake_case verb-first pattern (list_, get_, call_, wake_, sleep_) with the noun clearly indicating the target. get_tool_schema is slightly longer but still fits the same convention.
Six tools is well-scoped for a hub/gateway: discovery, schema introspection, invocation, and lifecycle control. Each tool earns its place with no obvious filler.
The gateway lifecycle is fully covered (discover servers → discover tools → get schema → call → wake/sleep). Minor gaps exist, such as searching tools across all servers at once or bulk status/health reporting, but agents can work around these via list_servers + list_tools.