MCP-Hub-MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
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. Before starting any task based on the user's request, always begin by using this tool to get a list of any additional tools that may be available for use. |
| call-toolC | Call a specific tool from a specific server |
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 2 tools
The two tools have completely distinct purposes with no overlap: one is for calling specific tools from servers, while the other is for listing all available tools. An agent can easily tell them apart as they serve different functions in the tool management workflow.
The tool names follow a consistent verb_noun pattern (call-tool, list-all-tools) with clear actions and objects. The hyphenated style is used consistently, though 'list-all-tools' includes a modifier ('all') which is a minor deviation from a pure verb_noun structure.
With only 2 tools, the server feels thin for its apparent purpose of managing MCP tools across servers. While it covers basic operations (call and list), more comprehensive tool management (e.g., discover servers, configure connections) is missing, making the scope underdeveloped.
The tool surface is severely incomplete for managing an MCP hub. It lacks essential operations such as discovering or connecting to servers, managing server configurations, or handling errors. The two tools provide only minimal functionality, leaving significant gaps that will hinder agent workflows.