Agent Hub MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_HUB_DATA_DIR | No | Storage directory for Agent Hub MCP data | ~/.agent-hub |
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 | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| register_agentC | Register an agent with the hub |
| send_messageB | Send a message to another agent or broadcast to all agents |
| get_messagesC | Retrieve messages for an agent |
| get_hub_statusA | Get overview of hub activity, agents, and collaboration opportunities |
| create_featureC | Create a new feature for multi-agent collaboration |
| create_taskB | Create a task within a feature with agent delegations |
| create_subtaskC | Create implementation subtasks within a delegation |
| get_featuresC | Get list of features with optional filtering |
| get_featureB | Get complete feature data including tasks, delegations, and subtasks |
| accept_delegationC | Accept a delegation assigned to an agent |
| update_subtaskC | Update subtask status and provide output/context |
| syncA | Comprehensive sync with the hub - get messages, workload, and status in one call |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Active Agents | List of all active agents in the hub |
| Collaboration Opportunities | Current collaboration sessions and opportunities |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: registration, feature/task/subtask creation and retrieval, messaging, delegation acceptance, and a composite sync tool. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_feature, get_messages, accept_delegation). The only exception is 'sync', which is a single verb but serves as a comprehensive operation.
12 tools cover the hub's domain: agent registration, feature/task/subtask management, messaging, delegation, status, and sync. This is well-scoped for a multi-agent collaboration server without being excessive.
The toolset covers core workflows: registration, CRUD for features/tasks/subtasks, messaging, delegation, and status. Minor gaps like update for features/tasks or delete operations are absent but not critical for the hub's purpose.