Support MCP integration for Hermes to connect ByteRover as an additional memory backend

[xiakong24]

Pre-flight checklist

• I have searched existing issues and this feature has not been requested yet

Problem statement

Request a feature that allows the project to provide an MCP-based integration for Hermes to connect with ByteRover.

Proposed solution

Currently, Hermes can connect to ByteRover through the memory provider, but the memory provider slot is limited to one and is already occupied by another service. Because of this limitation, I’m unable to use ByteRover as a memory backend in the current setup.

It would be very helpful if Hermes could support ByteRover via MCP as an external/secondary memory carrier. This would allow users to attach ByteRover without relying on the single memory provider slot, making the integration more flexible and easier to adopt in existing environments.

Alternatives considered

No response

Area

MCP Integration

Additional context

No response

Contribution

• I am willing to submit a pull request for this feature

[DatPham-6996]

Hey @xiakong24 , we're working on this, please hang tight, we will ship the best soon