mcp-coco
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-coco Ask Hermes: what is the capital of France?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP CoCo
MCP Bridge: OpenClaw ↔ Hermes Agent
MCP CoCo is a stable, persistent MCP (Model Context Protocol) server that connects OpenClaw (via mcporter) to Hermes Agent (NousResearch). It provides a robust bridge allowing either agent to send messages, continue conversations, and check health.
Unified Comm Tool
MCP CoCo exposes Hermes Agent's messaging capabilities as MCP tools — accessible from any MCP client (OpenClaw, Claude Desktop, Cursor, etc.).
Send a message → Wait for reply → Continue conversation. All through MCP.
Related MCP server: MCP Agent Bridge
Architecture
OpenClaw (Andul) ──mcporter──▶ MCP CoCo (daemon) ──▶ Hermes Agent CLI
│
├─ ask_hermes(prompt) → chat -q
├─ hermes_send(target) → hermes send
├─ hermes_channels() → hermes send --list
└─ coco_health() → gateway + CLI checkQuick Start
# 1. Install
node bin/cli.js --help
# 2. Test stdio mode
mcporter list --stdio "node index.js"
# 3. Add to mcporter (for persistent use from OpenClaw)
mcporter add coco --stdio "node C:\path\to\mcp-coco\index.js"
# 4. Send a message to Hermes
mcporter call coco.ask_hermes prompt="Hello Hermes"
# 5. Or run as background daemon
node index.js --daemonWindows Daemon
# Install as Windows Scheduled Task (auto-start on boot)
powershell -File scripts\install.ps1MCP Tools
Tool | Description |
| Send a prompt to Hermes, get response. Use |
| Send a message through Hermes (Telegram, Discord, etc.) |
| List available Hermes messaging channels |
| Full health check: Hermes CLI, gateway, daemon status |
Example: Multi-turn Conversation
# Turn 1 — start a new session
mcporter call coco.ask_hermes prompt="Hi, my name is Jonus"
# → { response: "Hello Jonus!", session_key: "20260624_..." }
# Turn 2 — continue the same conversation
mcporter call coco.ask_hermes prompt="What's the weather like?" session_key="20260624_..."Requirements
Node.js >= 18
Hermes Agent (
pip install hermes-agent)mcporter (comes with OpenClaw)
License
MIT
Available Tools
4 toolsask_hermesB
Send a prompt to Hermes Agent and get its response. Supports multi-turn via session_key.
Inputs: prompt (required), session_key.
coco_healthB
Check MCP CoCo bridge and Hermes Agent health status
Inputs: no named parameters.
hermes_channelsC
List available Hermes messaging channels/platforms
Inputs: platform.
hermes_sendC
Send a message through Hermes to a chat platform (Telegram, Discord, etc.)
Inputs: target (required), message (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Agent communication platform for agent to agent messaging via MCP. Messages, channels, skills.
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs.
Related MCP Servers
- 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
- AlicenseNot gradedqualityDmaintenanceA bridge server that enables Hermes Agent and OpenClaw to share tools and memory, forming a cooperative multi-agent system.MIT
- 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 gradedqualityBmaintenanceBridges OpenClaw and Hermes Agent to enable messaging, multi-turn conversations, and health checks via MCP tools.44 npmMIT