mcp-coco
Related Servers
Alternatives to mcp-coco
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceBridges OpenClaw and Hermes Agent to enable messaging, multi-turn conversations, and health checks via MCP tools.44 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with OpenClaw agents via MCP, supporting natural language queries and session management.3-
- AlicenseNot gradedqualityCmaintenanceBridges MCP-compatible AI clients to over 100 Hermes Agent skills for web browsing, file management, code execution, GitHub operations, and more.1MIT
- AlicenseNot gradedqualityDmaintenanceA bridge server that enables Hermes Agent and OpenClaw to share tools and memory, forming a cooperative multi-agent system.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server and local HTTP bridge designed to integrate remote upstream MCP tools into OpenClaw skills or local environments. It enables users to generate skill wrappers and proxy tool calls via a local HTTP bridge for use in Claude Desktop, Cursor, or OpenClaw.Apache 2.0
- AlicenseAqualityCmaintenanceExposes local OpenClaw agents as standard MCP tools so any MCP-compatible client can list agents, dispatch tasks, wait for or cancel runs, read session history, and receive voice-optimized replies.5MIT
TDQS
Scored across 4 tools
ask_hermes (prompt/response with the agent) and hermes_send (push a message to a chat platform) are the only pair that could be confused, but the descriptions draw a reasonable line between conversational prompting and outbound messaging. hermes_channels and coco_health are clearly distinct from both.
The set mixes verb-first (ask_hermes) with noun-first (hermes_send, hermes_channels, coco_health) and inconsistent prefixes (hermes_ vs coco_). Names are readable but there is no predictable pattern an agent can rely on.
Four tools is small but each one covers a distinct capability of a bridge/agent server (prompt, outbound message, channel discovery, health). It sits just below a comfortable scope since there is little room for session or message-management operations.
Core operations exist, but there is no way to inspect or manage sessions (list/reset), no history or inbound message read from channels, and no channel-level configuration. Agents will hit dead ends when they need to review or clean up prior Hermes conversations.