Skip to main content
Beyond Claude Code / Codex, MCP, CLI, and Hermes, HydraDB ships plugins for a growing set of coding agents and frameworks. The editor/agent plugins run on the same shared engine as the Claude Code plugin, so their config keys, environment overrides, and capture/search/ingest modes are identical; see Claude Code / Codex for the full reference.
Credentials are the same everywhere: an API key and a tenant ID from the HydraDB dashboard, set as HYDRADB_API_KEY and HYDRADB_DATABASE.

Coding agents & editors

OpenClaw

Cursor

Muse Code

Grok Build

OpenCode

OpenClaw

Automatically captures conversations, recalls relevant context with knowledge-graph connections, and injects it before every AI turn.
1

Install

Clone the repo and install from the local checkout:
Requires OpenClaw 2026.6.0 or later (openclaw --version).
2

Configure

Set credentials in the environment (or in the plugin config block plugins.entries.hydradb.config), then restart the gateway:
Optional: HYDRADB_COLLECTION (sub-tenant scope) and HYDRADB_BASE_URL. Turn capture reads conversation messages, which OpenClaw gates for non-bundled plugins; enable it with plugins.entries.hydradb.hooks.allowConversationAccess: true.
Lifecycle hooks: before_prompt_build recalls relevant memory and prepends it to the prompt, after_tool_call syncs edited files, agent_end captures the completed turn, and session_start syncs workspace docs. Manual actions come from the shipped skills: query, ingest, doctor, setup, and last-recall. Repo: hydradb-openclaw-plugin.

Cursor

Persistent, cross-session memory for Cursor: recalls relevant notes on each prompt, syncs your markdown docs into HydraDB, and saves conversations as durable memories.
1

Bootstrap & set credentials

Requires Node.js 18+ and npm.
2

Install in Cursor

Install via Cursor’s plugin/marketplace flow pointing at this checkout.
Repo: hydradb-cursor-plugin.

Muse Code

Memory for Muse Code, Meta’s terminal coding agent. Muse Code’s hooks cannot inject context back to the model, so recall is agent-invoked through MCP or skills, while hooks handle automatic capture and doc sync.
1

Add the MCP server

API-key requests to the MCP server require the X-HydraDB-Database header (your database ID). See the MCP reference for all supported headers.
2

Set credentials & run with the required flags

Only use --yolo in a workspace you trust. It bypasses command approval, so any project hooks loaded by --trust-workspace run against your local environment. In untrusted checkouts, prefer an approval profile that permits only the recall skill’s node call instead of --yolo.
Repo: hydradb-muse-code-plugin.

Grok Build

Automatic long-term memory for Grok Build, xAI’s coding agent. Grok Build’s plugin system is Claude-Code-compatible, so this is a full plugin with real per-prompt auto-recall (not just MCP tools).
1

Set credentials

2

Install in Grok Build

Use /marketplace to browse and install (from a local checkout, or via the catalog once listed).
MCP alternative: grok mcp add hydradb --url https://mcp.hydradb.com. The plugin already gives automatic recall, so MCP is optional. Repo: hydradb-grok-plugin.

OpenCode

Native plugin for OpenCode that hooks the session lifecycle to recall context at prompt time, sync workspace docs, and capture turns.
1

Install & set credentials

Add the plugin to your opencode.json; OpenCode installs it from npm:
Requires Bun (OpenCode’s runtime) and Node.js 18+.
2

Run with tool approval

Tool calls need approval. Run with --auto or approve hydradb_recall interactively:
Repo: hydradb-opencode-plugin. Package: hydradb-opencode-plugin.

Framework integrations

Python integrations that give your agents and chains persistent memory backed by HydraDB. These use the public API only; no HydraDB SDK required.

CrewAI

LangChain

CrewAI

HydraDB as external memory for CrewAI agents. Crews recall relevant history on each task and persist their outputs into HydraDB, so memory survives across runs.
Implements CrewAI’s Storage interface via ExternalMemory, available in CrewAI 1.0-1.10. On 1.11+ (which restructured memory around an embedding-based StorageBackend), use HydraDB over MCP instead. Outputs are stored as knowledge via the public /context/ingest path; search uses POST /query.
Repo: hydradb-crewai-plugin. Package: crewai-hydradb.

LangChain

HydraDB integration for LangChain: persistent, cross-session memory and retrieval for your chains and agents.
Requires langchain-core >= 0.3. Writes use the public knowledge path, so add_text/add_conversation store as knowledge; recall kind may be "memory", "knowledge", or "both". Ingestion is asynchronous, so recall a source only after it finishes indexing.
Repo: hydradb-langchain-plugin. Package: langchain-hydradb.

Source & Show Support

If any of these integrations make your workflow smarter, please star the open-source repos that power them.

hydradb-openclaw-plugin

hydradb-cursor-plugin

hydradb-muse-code-plugin

hydradb-grok-plugin

hydradb-opencode-plugin

hydradb-crewai-plugin

hydradb-langchain-plugin