Integrations
Hydrate ships in three integration shapes. Native hooks on Claude Code, a VS Code extension for Copilot, and MCP for everything else.
Three shapes, one store
Whichever path your agent takes, it reads from and writes to the same Hydrate fact store. The shape of the integration just decides how the agent reaches it.
| Shape | Tools | Behaviour |
|---|---|---|
| Native hooks | Claude Code |
Zero-friction. Fires on every turn automatically. The
UserPromptSubmit hook injects facts; the Stop
hook extracts them. You never call a tool by hand.
|
| VS Code extension | VS Code + Copilot | @hydrate chat participant plus three Language Model Tools
Copilot auto-invokes. Shares the same fact store as Claude Code hooks.
|
| Vibe integration | Mistral Vibe | hydrate vibe install registers the MCP server and writes
AGENTS.md with recall and capture instructions. Vibe joins
the same fact store as Claude Code and Copilot sessions.
|
| MCP | Gemini CLI, Cursor, Cline, Continue, Windsurf, Zed, Claude Desktop |
The model chooses to call Hydrate tools. One binary
(hydrate-mcp) speaks MCP over stdio and every MCP-capable
client gets hydrate_recall,
hydrate_save_fact, and hydrate_list_projects.
|
Shipped today
- Claude Code - first-class via hooks. Setup at /docs/install.
- VS Code + Copilot - via extension. See the Copilot page.
- Mistral Vibe - via MCP. Run
hydrate vibe install. - Gemini CLI - via MCP. Setup at /docs/integrations/gemini-cli.
Roadmap
Every integration below is on the roadmap for the weeks after beta launch.
The MCP protocol wiring is the same pattern as Gemini CLI - if you want
to pilot one of these before the official setup docs land, the
hydrate-mcp binary runs unchanged and each client has its
own MCP-server config format. Ping us at
[email protected] and we'll
send you the client-specific snippet.
- Cursor - soon. Same MCP pattern as Gemini.
- Cline - soon.
- Continue.dev - soon.
- Windsurf - soon.
- Zed - soon.
- Claude Desktop - soon.
The architectural choice
One hydrate-mcp binary, N clients, a documented per-tool config
snippet for each. We didn't write a bespoke plugin for every agent; we shipped
the protocol and let each client point at the same binary.