Skip to content

[FEATURE] support for remote projects in hermes plugin #1387

Description

@devlsh

Feature Description

Allow the Hermes Basic Memory plugin to connect to a self-hosted remote Basic Memory project through its Streamable HTTP MCP endpoint.

Problem This Feature Solves

The Hermes plugin currently supports local projects and Basic Memory Cloud, but cannot use a Basic Memory project hosted on another service or machine. This prevents Hermes from sharing an existing self-hosted project with other clients.

Proposed Solution

Add a remote mode that accepts a Basic Memory MCP endpoint URL.

Example configuration:

{
  "mode": "remote",
  "url": "https://memory.example.com/mcp"
}

The plugin would use the remote endpoint for its existing memory tools, retrieval, and capture behavior.

Alternative Solutions

Current workarounds are maintaining a custom plugin patch or running a separate local Basic Memory project for Hermes. Both add operational complexity or prevent clients from sharing one authoritative project.

Additional Context

Basic Memory already supports Streamable HTTP transport. This request is specifically for exposing that transport as a supported connection mode in the Hermes plugin.

Impact

This would let Hermes use centrally hosted, self-managed Basic Memory projects and share the same knowledge base with other MCP clients without requiring Basic Memory Cloud.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions