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_toolB | 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/ni-c/mcp-hub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server