HydraDB x MCP & CLI Hackathon
HydraDB x MCP & CLI Hackathon
July 31, 6 PM PT → August 7, 6 PM PT · Virtual · $500 in prizes
Discord: https://discord.gg/t6mE9hCJzr
HydraDB is a context substrate for AI agents — Knowledge, Memories, a context graph, and one /query that merges them, personalized per user.
We shipped an MCP server and a CLI. Both work. Both expose about a third of the API. The MCP server can store and search memories — but can't ingest a document, can't run a type: "all" query, can't touch a single connector, and can't show you the graph. The CLI has the same holes and still speaks the old tenant vocabulary.
Your challenge: make the MCP server and the CLI reach everything the API can do. Nothing else. Two surfaces, one week.
MCP tracks
Full-surface server — v2
querywithtype: "all",metadata_filters,graph_context; knowledge ingestion, not just memories; source relations; ingestion status; collection scoping per call.Tools an agent uses correctly — the hard part isn't the HTTP. Design tool names, schemas, and descriptions so a model reliably picks memory vs knowledge vs all, and knows when to write. Bring evals that prove it.
CLI tracks
Connectors from the terminal — eleven endpoints, zero commands.
discover,configure,sync,status. Make connecting Notion a two-minute task.Coherent v2 CLI — one
querycommand instead of three recall verbs.database/collectionnaming. Stop demandingTENANT_IDafter login. Adddoctor, JSON everywhere, shell completions, mock mode.
Either surface
Recall inspector — show why a result came back: semantic vs BM25 vs graph traversal vs metadata filters,
fastvsthinking. Ship it as an MCP tool, a--explainflag, or a TUI.
Prefer designing to building? Open an RFC on either surface: right tool granularity for agents, collection scoping across users in one session, who decides when a memory gets written.
Judging: merged over demoed, working over ambitious. Does a new developer get further, faster, after your PR?
Warm-up bounties: npm package name disagrees between docs and README · HYDRA_DB_* vs HYDRADB_* across three tools · tenant/sub_tenant left over from the v2 rename.
To join: claim a track in #hackathon, get a key at app.hydradb.com, fork hydradb-mcp or hydradb-cli, PR before August 7 at 6 PM PT, post a 60-second demo.