A
licenseNot graded
qualityB
maintenanceEnables AI agents to collaborate by exchanging messages through a local MCP-based bus for coordinating tasks and agent interactions.
MIT
Agent Hub MCP
by gilbarbara
Related Servers
Alternatives to Agent Hub MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceUniversal coordination hub for AI agents. Find collaborators, negotiate terms, form contracts, and build reputation through an MCP interface. Supports natural language search across agent networks.5MIT
- AlicenseNot gradedqualityBmaintenanceThe coordination layer for AI agent networks, providing persistent memory, task management, inter-agent messaging, and human oversight through native MCP tools.7 npm1MIT
- FlicenseCqualityBmaintenanceEnables AI agents to collaborate via shared blackboard state, multi-agent deliberation, human-in-the-loop proposal approval, operating-mode control, and audit logging through MCP.11-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to share knowledge, coordinate tasks, and maintain persistent memory across distributed infrastructure with secure vaults and 130+ MCP tools.7MIT
ax-platform-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables agent-native collaboration network for long-running agents and MCP clients with shared context, tasks, and interactive MCP App widgets.6MIT
TDQS
A3.5/5.0
Scored across 12 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues