Hermes's built-in MCP server exposes messages_send(target, message), but no edit/update tool. A bridge can send new messages; it cannot update them through that API. The edit feature request and its PR remain open.
External bridge: the MCP surface
The current hermes mcp serve interface includes:
| Interface | Purpose |
|---|---|
channels_list |
Discover chat targets |
conversations_list / conversation_get |
Inspect conversations and routing context |
messages_send(target, message) |
Send a new platform message |
events_poll / events_wait |
Read conversation events |
There is no exposed message-edit or stream-publish operation. The send engine can return a platform message ID, but that does not provide an update operation. Event-reading tools do not publish ACP updates into a chat.
Official MCP documentation Current MCP implementation Send engine
Issue #21859 requests an edit action. PR #25919 remains open; its review identifies changes needed for the current messaging architecture. It is not a ready, merged capability.
Checked documentation and source; no live chat test was performed.