Adapters
PLUR’s engine is a single thing: a typed engram store with hybrid local search. Adapters are how that engine plugs into the places agents actually run.
There are three integration depths, in order of “how invisible PLUR is”:
- Plugin / hook — fully automatic. The host runtime calls PLUR at lifecycle events without the agent asking. Best UX.
- MCP tool — the agent calls PLUR explicitly via Model Context Protocol. Works with anything that speaks MCP.
- CLI / HTTP — explicit shell-out or HTTP call. Universal escape hatch.
Most adapters combine 1 and 2. The MCP server, for instance, ships with Claude Code hooks (depth 1) and exposes MCP tools the agent can call directly (depth 2).
Pick your adapter
Section titled “Pick your adapter” MCP Claude Code, Cursor, Windsurf, Codex — any MCP client. Most common path.
OpenClaw plugin @plur-ai/claw — deepest integration, runs as a ContextEngine plugin.
Hermes (Python) plur-hermes — Python agent frameworks, auto-discovered.
CLI @plur-ai/cli — universal bridge for scripts and custom agents.
Custom (HTTP/SSE + REST) Build your own — PLUR Enterprise speaks HTTP/SSE and a REST API.
Capability matrix
Section titled “Capability matrix”| Capability | MCP | OpenClaw | Hermes | CLI | Custom |
|---|---|---|---|---|---|
| Auto-inject on session start | ✓ (CC hooks) | ✓ (built-in) | ✓ (pre_llm_call) | – | self-implemented |
| Auto-capture corrections | ✓ (CC hooks) | ✓ (built-in) | ✓ (post_llm_call) | – | self-implemented |
| Episode timeline | ✓ | ✓ | ✓ | ✓ | ✓ |
Explicit learn / recall tools | ✓ | ✓ | ✓ | ✓ | via REST |
| Knowledge Packs | ✓ | ✓ | ✓ | ✓ | ✓ |
| Sync across machines | ✓ | ✓ | ✓ | ✓ | n/a |
| Multi-user permission enforcement | – (single-user) | – | – | – | ✓ (Enterprise) |
| Server-side audit log | – | – | – | – | ✓ (Enterprise) |
Which one should you use?
Section titled “Which one should you use?”- You use Claude Code, Cursor, or Windsurf → MCP adapter.
- You use OpenClaw → OpenClaw plugin — strictly better UX than MCP because it gets lifecycle hooks.
- You’re building a Python agent with the Hermes framework → Hermes adapter.
- You’re scripting or building a custom agent → CLI, or Custom for HTTP integration.
- You’re a team with shared scopes and governance needs → PLUR Enterprise, which adds an HTTP/SSE server and REST API on top of the same engine.
Adapter versions track the core engine on a shared release cycle. The current verified pairing is @plur-ai/core@0.13.0, @plur-ai/mcp@0.13.0, @plur-ai/cli@0.13.0, @plur-ai/claw@0.10.x, plur-hermes==0.13.0.