Hydra piggybacks on the browser sessions you already have — Slack, iMessage, LinkedIn and more — into a single local bridge. No bots, no API keys, no IT approval.
One layer across every conversation
Three surfaces, one job: get your conversations onto your machine, where an agent that knows you can act on them.
The Chrome extension calls each platform's API as you, in your own session — same IP, same device. No bots, no OAuth, indistinguishable from normal use.
Everything lands in a local bridge on your Mac — a rolling 24-hour snapshot, on disk, encrypted. Nothing is uploaded. No account, no cloud, no telemetry.
Your agent reads the bridge and hands you a morning briefing: what's urgent, what's noise, drafts ready to approve. It proposes — you click send.
Not another feed to scroll. A ranked shortlist of what actually needs you — with replies already drafted, ready to approve.
“Any update on the attribution dashboard? It's blocking the board deck.”
“Perfect — I'll send the plan over first thing tomorrow 👌”
“Loved the demo. Could you intro me to your eng lead this week?”
Hydra reads your sessions and your messages. That only works if you can see exactly what it does — so it's open source and stays on your machine.
Tokens and conversations never leave your machine. Works fully offline. No phone-home.
Structured JSON, not just a UI. The agent proposes actions; you approve; the extension executes.
A present-tense snapshot — last 24h to 7d, not an archive. Stale data just re-fetches.
Every line is inspectable. The bar for Full Disk Access: you can see what it does, and it doesn't phone home.
Where a real API exists, Hydra uses it. The local gog CLI talks to Google's official APIs — your tokens stay in the macOS keychain, and nothing leaves the machine.
Your inbox through the official Gmail API — read, triaged, and searchable locally. Reply in-thread, with your approval before anything sends.
Your agenda as a first-class primitive — events, attendees, and meeting links, so an agent knows not just who wrote you but when you're seeing them.
Some of the highest-signal context never touches a public API — it lives on your machine. Hydra reads it there, locally, and it stays there.
Reads Messages straight from your Mac's local database — no phone bridge, no cloud round-trip.
Your macOS Contacts name and unify your People — the identity bridge that turns handles into the same real human across every platform.
Notification Center as a universal, real-time feed — every app you get pinged in, plus iPhone alerts mirrored through Continuity.
Hydra exposes your conversations through standard interfaces — MCP for AI agents, CLI for scripts and terminals.
A local MCP server that gives any AI agent read access to your conversations. Works with OpenClaw, Claude Desktop, Cursor, and any MCP-compatible client.
{
"mcp": {
"servers": {
"hydra": {
"command": "hydra-mcp"
}
}
}
}Query your message store from the terminal. Pipe to jq, grep through conversations, build scripts on top.
$ hydra inbox # recent across all platforms $ hydra inbox --platform linkedin $ hydra search "apartment" --json | jq . $ hydra people --search "kristian"
Want the CLI? Star the repo or tell us your use case →
Hydra's core stays open source and local-first. Pro pays for the work that keeps platform adapters, signed builds, and official releases current.
Run the local inbox, browser bridge, SQLite store, MCP server, and CLI without an account.
DownloadSupport the maintained build: official signed releases, managed adapter fixes, and one year of updates.
Buy ProAdd another year of official updates and adapter maintenance to an existing Hydra Pro license.
Renew updatesCloud sync and hosted MCP are intentionally not sold yet. They become subscription products only when the service exists.
One private hub for every conversation — open source, no account, no cloud. Don't trust us? Read every line.