MCP Hub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-all-toolsA | List ALL available tools from all connected servers. NOTE: For better performance, use find-tools with keywords first. Only use this when you need to see everything or if find-tools didn't find what you need |
| call-toolA | Call a specific tool from a specific server. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName |
| find-toolsA | Use this tool to find best tools by searching with keywords or regex patterns. If you don't have a specific tool for a task, this is the best way to discover what tools are available. |
| get-toolA | Get complete schema for a specific tool from a specific server, including inputSchema. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName |
| list-all-tools-in-serverA | List ALL tools from a specific MCP server (returns name and description only) |
| find-tools-in-serverA | Find tools matching a pattern in a specific MCP server (returns name and description only) |
| list-serversB | List all connected MCP servers |
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
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/warpdev/mcp-hub-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server