Skip to main content
HydraDB plugins give coding agents memory that lasts across sessions: they recall relevant notes when you send a prompt, sync your workspace docs into HydraDB, and save conversations as durable memories. Every plugin on this page runs on the same engine, so they share the commands, modes, and config variables at the end of the page. Each needs an API key and a database ID from the HydraDB dashboard, set as HYDRADB_API_KEY and HYDRADB_DATABASE.

Claude Code

Codex

Cursor

OpenCode

Muse Code

Grok Build

To use HydraDB from any other MCP client, connect the MCP server instead.

Claude Code

1

Install the plugin

Run these commands inside Claude Code:
2

Get credentials

3

Set environment variables

To verify the values are set:
4

Run setup and verify

HYDRADB_COLLECTION must be set explicitly. To use the default collection, set it to an empty string ("") rather than omitting it. These names need plugin 1.1.0 or later. The older names HYDRA_DB_API_KEY, HYDRADB_TENANT_ID, and HYDRADB_SUB_TENANT_ID still work, but print a deprecation warning.
HYDRADB_COLLECTION strategy:
  • Use a workspace-specific value (e.g., claude-my-project) for project-isolated memory.
  • Use a shared value to carry memory across all sessions and workspaces.
Once configured, the plugin runs in the background: it syncs workspace docs on session start, recalls relevant context before each prompt, and captures conversation memory after each response.

Codex

The Codex plugin recalls relevant notes when you send a prompt, syncs your markdown docs into HydraDB, and saves conversations as durable memories, the same behavior and the same engine as the Claude Code plugin above. The JSON config keys, capture/search/ingest modes, and environment variables are identical; only the install flow differs.
1

Install the plugin

Requires Node.js 18+ and npm. Then add a local marketplace entry in your project’s .agents/plugins/marketplace.json pointing at this plugin folder and enable it in .codex/config.toml. See the Codex plugin docs for the current install flow.
2

Get credentials

3

Set environment variables

Set HYDRADB_COLLECTION to an empty string for the default collection, or a workspace-specific value for project-isolated memory.
The Commands, Modes, and Config Variables below apply to Codex unchanged.

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.

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.

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.
Everything from here on applies to every plugin on this page.

Commands


Modes

captureMode: how conversations are saved

searchMode: what is recalled at prompt time

ingestionMode: where workspace docs are synced

recallMode: speed vs. depth

By default, HydraDB syncs each conversation pair (user and assistant) that does not include the ignoreMarker (hydra-ignore). For manual-only capture, set captureMode to off and use /hydradb:save-session or /hydradb:remember <text>.

Config Variables

Required

Core behavior

Limits

Timeouts

File filtering

By default, HydraDB includes .md and .mdx files in workspace sync. To include additional file types, extend includeGlobs in your config file.

Advanced


Config File Location Priority

The plugin resolves config in this order (later sources override earlier ones):
  1. Built-in defaults
  2. HYDRADB_PLUGIN_CONFIG env var (absolute path to a JSON file)
  3. ${CLAUDE_PLUGIN_DATA}/config.json
  4. .hydradb-plugin-data/config.json
  5. .hydradb-plugin.json (workspace-shared, safe to commit to git)
  6. .hydradb-plugin.local.json (workspace-local, add to .gitignore)
  7. Environment variable overrides

Suggested Modes


Suggested Configs

Minimal (env vars only)

Maximum recall

Manual-save only (no auto-capture)


Source code