Wire Paseo daemons, paseo-desktop, and opencode to consume mem0 MCP #45

New issue

Closed

opened 2026-07-02 07:23:15 +01:00 by nimmo · 0 comments

nimmo commented

2026-07-02 07:23:15 +01:00

Owner

Scope

Wire the mem0 MCP endpoint into Paseo daemons (vega, lyra) and paseo-desktop (electra), plus opencode, so all AI agents share a single memory store.

Deliverables

Identify mem0 MCP endpoint URL (likely http://mem0:8888/mcp or http://mem0:8888/v1/mcp/sse — verify against server routers/ after packaging)
Paseo daemon config: add mem0 MCP server to config.json daemon.mcp section via the preStart relay-config pattern already used on vega/lyra
opencode config: add mem0 as an MCP server in opencode.json (server-scoped, pointing at the Nebula-reachable endpoint)
paseo-desktop (electra): ensure MCP server config reaches desktop clients through the relay
Generate mem0 API keys per consumer (dashboard → API Keys page) and store in SOPS
Document the endpoint and key references in secrets/README.md

Consumers

Consumer	How
Paseo daemons (vega, lyra)	`daemon.mcp` in config.json, injected via preStart
paseo-desktop (electra)	MCP config in home-manager activation (like relay config)
opencode	MCP server in opencode config

Hermes (follow-up)

Hermes has no MCP adapter. This is tracked separately — not a blocker for this issue. Possible approaches:

Pipe omp context equivalent into Hermes workspace
Build a small bridge that reads mem0 memories and injects them into Hermes prompt context

## Scope Wire the mem0 MCP endpoint into Paseo daemons (vega, lyra) and paseo-desktop (electra), plus opencode, so all AI agents share a single memory store. ### Deliverables - [ ] Identify mem0 MCP endpoint URL (likely `http://mem0:8888/mcp` or `http://mem0:8888/v1/mcp/sse` — verify against server `routers/` after packaging) - [ ] Paseo daemon config: add mem0 MCP server to `config.json` `daemon.mcp` section via the `preStart` relay-config pattern already used on vega/lyra - [ ] opencode config: add mem0 as an MCP server in opencode.json (server-scoped, pointing at the Nebula-reachable endpoint) - [ ] paseo-desktop (electra): ensure MCP server config reaches desktop clients through the relay - [ ] Generate mem0 API keys per consumer (dashboard → API Keys page) and store in SOPS - [ ] Document the endpoint and key references in `secrets/README.md` ### Consumers | Consumer | How | |---|---| | Paseo daemons (vega, lyra) | `daemon.mcp` in config.json, injected via preStart | | paseo-desktop (electra) | MCP config in home-manager activation (like relay config) | | opencode | MCP server in opencode config | ### Hermes (follow-up) Hermes has no MCP adapter. This is tracked separately — not a blocker for this issue. Possible approaches: - Pipe `omp context` equivalent into Hermes workspace - Build a small bridge that reads mem0 memories and injects them into Hermes prompt context

nimmo added this to the Mem0 Memory Layer Integration milestone

2026-07-02 07:23:15 +01:00

nimmo added the

phase:mcp

service:mem0

host:vega

labels

2026-07-02 07:23:15 +01:00

nimmo closed this issue

2026-07-11 12:31:23 +01:00