Hydra DB — MCP Server

MCP (Model Context Protocol) server for Hydra DB, the state-of-the-art agentic memory. Provides tools for storing, recalling, and managing memories with knowledge-graph enriched context.

Run it two ways, same tools either way:

Local (stdio) — the npx @hydradb/mcp binary each client spawns. No server to operate; credentials live in the client's config. This is the default and everything below the Configuration section documents it.
Remote (HTTP) — one hosted process behind a URL like https://mcp.hydradb.com that many clients point at, with nothing to install. See Remote / hosted server.

Available Tools

Tool	What it does
`hydradb_query`	Search memories and knowledge together, with knowledge-graph context
`hydradb_ingest`	Save a note, a document, or a conversation
`hydradb_list`	Enumerate one family — every memory, or every knowledge source
`hydradb_inspect`	Fetch one source's full content by id
`hydradb_delete`	Remove one or more items by id, irreversibly
`hydradb_status`	Check whether an ingested source has finished indexing
`hydradb_subgraph`	Everything connected to one item — its thread, replies, parents, children, links
`hydradb_feedback`	Report whether a query's results were useful, by its `request_id`

Ids flow between these: hydradb_query, hydradb_list and hydradb_subgraph emit them; hydradb_inspect, hydradb_delete, hydradb_status and hydradb_subgraph accept them.

Graph tools (Cypher)

Hydra DB also runs property graphs you model and own end to end, queried in Cypher. This is a different product surface from the memory and knowledge above, and nothing crosses between them: hydradb_query cannot see graph data, and hydradb_graph_query cannot see memories.

Tool	What it does
`hydradb_graph_query`	Run Cypher — reads and writes
`hydradb_graph_collections`	List the graphs in a graph database
`hydradb_graph_admin`	Create a graph database; drop a collection or a database

hydradb_graph_query is annotated destructiveHint, because it runs arbitrary Cypher and DELETE is as reachable through it as MATCH. There is deliberately no separate read-only Cypher tool and no read-only mode: both would mean classifying Cypher text client-side to decide what to refuse, which is a heuristic — a promise the server can keep and a client cannot. This server does not inspect your query at all; it sends it and reports what HydraDB says. To lock the graph surface down, withhold the tools (below) — that is a real guarantee.

// Everyone Alice knows within four hops
{"query": "MATCH (a:Person {name:$n})-[:KNOWS*1..4]->(r) RETURN DISTINCT r.name AS name",
 "params": {"n": "Alice"}}

// Bulk load, re-runnable after a failure
{"query": "UNWIND $rows AS row MERGE (p:Person {ext_id: row.ext_id}) SET p += row",
 "params": {"rows": [{"ext_id": "a", "name": "Alice"}]}}

Differences from Neo4j worth knowing before you write Cypher. Each is rejected before execution, so a rejected query changes nothing and fails identically on retry:

Procedure calls (CALL db.*, CALL apoc.*) are rejected by the server, before it executes anything. CALL { ... } subqueries are fine. There is no schema tool and no apoc.meta.schema(); to learn a collection's structure, query it — MATCH (n) UNWIND labels(n) AS l RETURN l, count(*) AS c ORDER BY l.
LOAD CSV is rejected — pass data through params instead.
Existence checks are bare pattern predicates (WHERE (p)-[:KNOWS]->()); EXISTS { ... } and exists() are not accepted.
shortestPath belongs in RETURN/WITH, not MATCH p = ..., and must be directed.
EXPLAIN/PROFILE execute the query rather than planning it — do not use them to preview one.

Collections auto-create on first write, so there is no create-collection call. Requests are capped at 256 KiB (enforced locally, before upload) and large result sets are truncated server-side — paginate with ORDER BY ... SKIP $offset LIMIT $limit.

To turn the graph tools off entirely:

HYDRADB_MCP_GRAPH_TOOLS=0   # withhold all three

Deprecated aliases

The previous hydra_db_* tool names are no longer registered by default as of 1.2.0. If your mcp.json still calls them, set:

HYDRADB_MCP_LEGACY_TOOLS=1

Deprecated alias	Use instead
`hydra_db_search`	`hydradb_query`
`hydra_db_store`, `hydra_db_ingest_conversation`	`hydradb_ingest`
`hydra_db_list_memories`, `hydra_db_list_sources`	`hydradb_list`
`hydra_db_fetch_content`	`hydradb_inspect`
`hydra_db_delete_memory`	`hydradb_delete`

hydradb_query

Searches both memories and ingested knowledge sources. Returns matching chunks with their source id, a relevance score, and knowledge-graph context.

Parameter	Type	Required	Description
`query`	string	Yes	What you want to know, as a question or topic
`kind`	string	No	`memory`, `knowledge`, or `all` (default: `all`)
`max_results`	number	No	Maximum chunks to return (1-50, default: 10)
`mode`	string	No	`fast`, `thinking` (default), or `auto`
`detail`	string	No	`compact` (default) trims each chunk; `full` returns them whole
`structured`	boolean	No	Also return `structuredContent` (`resolved_scope`, `request_id`, `sources` with `inspect_args`). Default: false — text only
`graph_context`	boolean	No	Include knowledge-graph relations (default: true)
`operator`	string	No	`or`, `and`, or `phrase`. Switches the query to keyword retrieval (`query_by=text`), which is the only mode Hydra DB accepts an operator on — semantic matching is off for that query. Unset (the default) is hybrid semantic search
`source_ids`	array	No	Restrict the search to these sources
`titles`	array	No	Restrict to exact document titles (case-insensitive); resolved to source IDs before normal search
`metadata_filters`	object	No	Exact-match filters over stored metadata
`num_related_chunks`	number	No	Adjacent chunks to attach per match (0-5, default: 0)
`recency_bias`	number	No	Favour recently-updated sources when ranking, 0-1 (default: 0). Re-ranks only; it never excludes older sources
`query_apps`	boolean	No	App-aware retrieval over connector sources — exact IDs and actors, thread reconstruction, linked and parent/child items (on by default: Hydra DB applies it when omitted; pass `false` to skip)
`collections`	array	No	Search several collections at once. Pass either this or `collection`, never both

Results are text only by default: each chunk carries its source id and collection, and the header names the resolved scope. With structured: true, results also include structured resolved_scope and per-source inspect_args when the source's collection is known. Copy those arguments, including your ACL, to follow-up calls; tools never inherit a previous call's scope. With multiple collections, an ID alone is not enough: use the collection attached to that source. If it is missing, resolve the collection before inspecting. Explicit scope is never widened.

hydradb_ingest

Saves information so it outlives the session. Provide exactly one of text or turns.

Parameter	Type	Required	Description
`text`	string	No*	A note, fact, decision, or document body
`turns`	array	No*	Conversation turns, each with `user` and `assistant`
`kind`	string	No	`memory` (default) or `knowledge` for a document
`title`	string	No	Label shown in later search results — always set it
`source_id`	string	No	Identifier for this entry. Reusing one REPLACES what is stored under it
`overwrite`	boolean	No	Allow that replacement (default: true)
`infer`	boolean	No	Extract insights and graph entities (default: true)
`is_markdown`	boolean	No	Chunk on markdown structure (default: false)
`metadata`	object	No	Key/value metadata, matchable later via `metadata_filters`
`observation_date`	string	No	When the fact was true, as `YYYY-MM-DD` (e.g. `2026-07-04`), vs when it was stored
`user_name`	string	No	What to call the user, used with `turns` (default: `User`)

* Passing both is an error; passing neither is an error.

Ingestion is asynchronous — content is not searchable the instant it is saved. Use hydradb_status to confirm.

hydradb_list

Enumerates one family at a time. These are separate corpora: listing memories tells you nothing about which knowledge sources exist.

Parameter	Type	Required	Description
`kind`	string	Yes	`memory` or `knowledge`
`ids`	array	No	Restrict to these ids
`source_ids`	array	No	Deprecated alias for `ids`
`external_id`	string	No	Exact originating-system ID, such as a Confluence page ID or Drive file ID; knowledge only
`parent_external_id`	string	No	Exact provider parent ID; returns indexed direct children only. Requires `kind: "knowledge"`, `provider` and `connector_id`
`connector_id`	string	No	Exact originating connector instance from stored `additional_metadata.connector_id`; required for parent lookup, optional for other knowledge lookups
`url`	string	No	Exact original URL stored at ingestion; knowledge only, not a live web fetch
`provider`	string	No	Connector provider, such as `confluence` or `google_drive`; knowledge only
`page`	number	No	Page to return, 1-indexed (default: 1)
`page_size`	number	No	Items per page (1-100)

The response reports how many of the total it showed and how to reach the rest.

For a known document link, resolve its provider ID or exact stored URL first, then use the returned HydraDB source ID with hydradb_inspect or hydradb_query.source_ids:

{
  "name": "hydradb_list",
  "arguments": {
    "kind": "knowledge",
    "external_id": "123456",
    "provider": "confluence",
    "database": "your_database",
    "collection": "your_collection"
  }
}

Supplied selectors are combined with AND and preserve the caller's permissions. URL matching does not normalize links, follow redirects or fetch external pages. Multiple sites or copies may match an ID; inspect the candidates and pagination. No visible match in a scope is not proof a document was never ingested. For a document known only by name, use hydradb_query.titles or ordinary search instead. These selectors are rejected for kind: "memory", never silently ignored.

To enumerate indexed children, resolve the parent first, then use parent_external_id with its provider ID, provider, connector_id, and the same database, collection and ACL. Provider IDs can repeat across sites/accounts; never guess a connector ID. Missing connector metadata needs investigation before safely enumerating children. Follow next_args while has_more is true. Returned identity fields (external_id, provider, parent_external_id, connector_id) are included when stored. For descendants, use each child's children_args, track visited identities, and inspect each document separately. This is not a live provider tree: absent/stale parent metadata, permissions or incomplete ingestion can omit children. hydradb_subgraph includes other relationships and bounded traversal; it is not an exhaustive child listing.

hydradb_inspect

Fetches one source's full content by id.

Parameter	Type	Required	Description
`id`	string	Yes	The source id, from `hydradb_query` or `hydradb_list`
`source_id`	string	No	Deprecated alias for `id`
`mode`	string	No	`content` (default), `url` for a download link, or `both`
`offset`	number	No	Character offset to read from (default: 0)
`limit`	number	No	Maximum characters to return (max 20000)
`expiry_seconds`	number	No	How long a `url` link stays valid

Long sources come back in slices, and binary sources are never inlined — you get their type and size, and mode: "url" returns a download link.

Text and structured output expose the same bounded slice. Follow next_args until has_more is false, keeping the same scope and ACL. Offsets count UTF-16 code units; a 125,000-character source needs seven default-size calls, not three. complete means the current response contains the whole text. Each slice re-fetches current content; compare content_sha256 and restart if it changes. There is no pinned snapshot across calls. Reading a document index does not read every linked document.

hydradb_feedback

Records whether a query's results were actually useful. Correlated to that query by its request_id, which hydradb_query prints at the end of its output — copy it verbatim, it cannot be guessed or reconstructed.

Parameter	Type	Required	Description
`request_id`	string	Yes	The id `hydradb_query` printed for the query being rated
`feedback`	string	No	What was wrong, missing or good, in plain words (max 8000)
`rating`	string	No	`positive`, `negative` or `neutral`
`ground_truth_answer`	string	No	The answer a correct system would have given
`ground_truth_source_ids`	string[]	No	Sources that actually contain the answer (max 100)
`metadata`	object	No	Your own string labels, e.g. an eval run name (max 20)
`database`, `collection`	string	No	Scope overrides

Send text, ground truth, or both — a submission with neither records nothing and is refused. Ground truth is worth far more than prose because it is machine-checkable: source_ids turns one submission into a retrieval judgement (did the query surface these, at what rank, at all?), which is recall measured on real traffic rather than on a benchmark that stops resembling production the day it is written.

Feedback never changes the result of the query it describes and never alters stored data. Rows are labelled source: agent, because everything reaching this server came from a model — agent feedback is a different population from human feedback and is separated at write time.

hydradb_subgraph

Returns the connected subgraph of one item: every item reachable from it through item-level links — explicit relations declared at ingest, a shared thread, parent/child hierarchy — traversed breadth-first. Use it when one result is not enough and you need what surrounds it: the rest of a Slack thread, the replies under a ticket, the documents a page links to.

Parameter	Type	Required	Description
`id`	string	Yes	The item to start from, from `hydradb_query` or `hydradb_list`
`kind`	string	No	`knowledge` (default) or `memory` — the two graphs are separate
`depth`	number	No	Hops to traverse (default 5, max 10)
`max_sources`	number	No	Cap on members returned (default 200, max 1000)
`database`, `collection`	string	No	Scope overrides

Each member carries its id, title, depth from the start item and how it was reached — discovered_relation is the mechanism (same_thread, parent, child, or a relates_to type such as reply_to) and discovered_via the id of the member it was reached from, so the list is also a tree. structuredContent carries those same members, in the same order, plus relations: the edges among them as {from, to, type}, so a client can rebuild the graph and not just the list. truncated means max_sources clipped the traversal; structural_link_count and structural_truncated report the structural graph (entities, comments, attachments, actors) around the members. Chunk-level entity relations are not included; those come from hydradb_query.

hydradb_delete

Removes items by id. Irreversible.

Parameter	Type	Required	Description
`ids`	array	No*	The ids to delete — accepts several at once
`id`	string	No*	A single id
`kind`	string	No	`memory` (default) or `knowledge`

* Provide one of them.

hydradb_status

Checks whether ingested sources have finished indexing.

Parameter	Type	Required	Description
`ids`	array	Yes	The source ids to check

Configuration

Get Your Credentials

Get your Hydra DB API Key from Hydra DB
Get your database name from the Hydra DB dashboard

Environment Variables

Variable	Description	Default
`HYDRADB_API_KEY`	Your Hydra DB API key	Required
`HYDRADB_DATABASE`	Your Hydra DB database (tenant scope)	Required
`HYDRADB_COLLECTION`	Collection (sub-tenant) for partitioning	none — unset means the workspace's own collection; the model can also name one per call via `collection`/`collections` (see `hydradb_list_collections`)
`HYDRADB_BASE_URL`	Base URL override	`https://api.hydradb.com`
`HYDRADB_LOG_LEVEL`	Log level: DEBUG, INFO, WARN, ERROR	`ERROR`
`HYDRADB_TIMEOUT_SECONDS`	Per-attempt request timeout	`30`
`HYDRADB_MAX_RETRIES`	Retries per request (0 disables)	`2`
`HYDRADB_MCP_LEGACY_TOOLS`	Register the deprecated `hydra_db_*` tools	off
`HYDRADB_GRAPH_DATABASE`	Default graph database for the Cypher tools	`HYDRADB_DATABASE`
`HYDRADB_GRAPH_COLLECTION`	Default graph collection	`default`
`HYDRADB_MCP_GRAPH_TOOLS`	Register the graph tools (`0` withholds them)	on

A graph database is a different namespace from the memory database: the same name can exist as both, and Cypher aimed at the wrong one reads an empty graph rather than failing. Every graph tool also takes database and collection per call, overriding these defaults.

The legacy HYDRA_DB_* names — HYDRA_DB_API_KEY, HYDRA_DB_TENANT_ID, HYDRA_DB_SUB_TENANT_ID, HYDRA_DB_BASE_URL, HYDRA_DB_LOG_LEVEL — remain honoured as deprecated aliases (canonical wins when both are set; using an alias prints a one-time warning naming its replacement).

Claude Desktop

{
  "mcpServers": {
    "hydradb": {
      "command": "npx",
      "args": ["-y", "@hydradb/mcp@latest"],
      "env": {
        "HYDRADB_API_KEY": "your-api-key",
        "HYDRADB_DATABASE": "your-database"
      }
    }
  }
}

Cursor & Windsurf

Client	Config File
Cursor	`~/.cursor/mcp.json`
Windsurf	`~/.codeium/windsurf/mcp_config.json`

{
  "mcpServers": {
    "hydradb": {
      "command": "npx",
      "args": ["-y", "@hydradb/mcp@latest"],
      "env": {
        "HYDRADB_API_KEY": "your-api-key",
        "HYDRADB_DATABASE": "your-database"
      }
    }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "hydradb": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@hydradb/mcp@latest"],
      "env": {
        "HYDRADB_API_KEY": "your-api-key",
        "HYDRADB_DATABASE": "your-database"
      }
    }
  }
}

Custom Sub-Tenant

To partition data, set the HYDRADB_COLLECTION environment variable:

{
  "mcpServers": {
    "hydradb": {
      "command": "npx",
      "args": ["-y", "@hydradb/mcp@latest"],
      "env": {
        "HYDRADB_API_KEY": "your-api-key",
        "HYDRADB_DATABASE": "your-database",
        "HYDRADB_COLLECTION": "my-project"
      }
    }
  }
}

Remote / hosted server

Everything above spawns the server locally over stdio. The same server also runs as a long-lived HTTP endpoint that many clients reach at one URL — nothing to install or update per user. This is what powers a hosted deployment like https://mcp.hydradb.com, and what you run yourself with npm run start:http or the Docker image.

The tool surface is identical; only how a client connects and authenticates changes.

Point a client at a URL

MCP clients that support a remote (streamable-http) server take a URL and headers instead of a command:

{
  "mcpServers": {
    "hydradb": {
      "url": "https://mcp.hydradb.com",
      "headers": {
        "Authorization": "Bearer YOUR_HYDRADB_API_KEY",
        "X-HydraDB-Database": "your-database"
      }
    }
  }
}

Every request carries its own credentials, so one hosted process serves any number of independent users. The headers a request may send:

Header	Maps to	Required
`Authorization: Bearer <key>`	Hydra DB API key (`X-HydraDB-Api-Key` also accepted)	Yes*
`X-HydraDB-Database`	Default database (tenant scope)	Yes*
`X-HydraDB-Collection`	Default collection (sub-tenant); unset means the workspace's own collection	No
`X-HydraDB-Graph-Database`	Default graph database for the Cypher tools; defaults to the request's database	No
`X-HydraDB-Graph-Collection`	Default graph collection; defaults to `default`	No

* Unless the server was started with HYDRADB_API_KEY / HYDRADB_DATABASE in its environment (single-tenant self-host, below), in which case a request may omit them and fall back to the server's own credentials. A request that supplies neither a header nor a server-side default is refused: 401 with no key, 400 with a key but no database.

Every tool additionally accepts optional database and collection parameters directly in its arguments (e.g. hydradb_query with {"query": "...", "database": "tenant_b"}), allowing multi-tenant agents to switch tenant scope per tool call while falling back to the session defaults when omitted.

Base URL, request timeout and retry count are operator settings read from the server's environment and are never taken from a request header.

Run the HTTP server

Node:

npm ci && npm run build
# Single-tenant: the server holds one account; clients send no credentials.
HYDRADB_API_KEY=your-key HYDRADB_DATABASE=your-database npm run start:http
# Multi-tenant: no account in the env; every client sends its own headers.
BIND_ADDRESS=0.0.0.0 ALLOWED_HOSTS=mcp.hydradb.com npm run start:http

Docker:

docker build -t hydradb-mcp .
# Single-tenant
docker run -p 8080:8080 -e HYDRADB_API_KEY=your-key -e HYDRADB_DATABASE=your-database hydradb-mcp
# Multi-tenant (clients authenticate per request)
docker run -p 8080:8080 -e ALLOWED_HOSTS=mcp.hydradb.com hydradb-mcp

The primary MCP endpoint is / (with /mcp supported as an alias); GET /health is an unauthenticated liveness probe. The image binds 0.0.0.0 inside the container (the host controls exposure with -p) and runs as an unprivileged user.

Sign in with HydraDB (OAuth)

With three extra variables the hosted server also speaks the MCP authorization flow: a client that arrives with no credentials gets a 401 pointing at /.well-known/oauth-protected-resource, discovers the HydraDB dashboard as its authorization server, opens the browser, and the user signs in and picks a database. No key is ever pasted into a client.

Variable	Description
`HYDRADB_OAUTH_ISSUER`	The authorization server, e.g. `https://app.hydradb.com`. Must match its `NEXTAUTH_URL` exactly
`HYDRADB_MCP_PUBLIC_URL`	This server's public URL as clients see it, e.g. `https://mcp.hydradb.com`. Tokens minted for any other audience are refused
`HYDRADB_OAUTH_INTROSPECTION_SECRET`	Shared secret the issuer's `/api/oauth/introspect` expects; must equal the dashboard's `MCP_INTROSPECTION_SECRET`

All three are required together. With any of them missing, OAuth stays off and the server behaves exactly as before: no new routes, no new headers. Token introspection answers are memoised for up to 30 seconds, so disconnecting an app from the dashboard takes effect within that window.

OAuth is purely additive. API keys in Authorization / X-HydraDB-Api-Key headers, the X-HydraDB-Database header and the single-tenant environment fallback all keep working unchanged on the same URL.

Server environment variables

These configure the HTTP process itself (the stdio server ignores them). All the HYDRADB_* variables from Environment Variables also apply — as the single-tenant default and as operator settings.

Variable	Description	Default
`PORT`	Port to listen on	`8080`
`BIND_ADDRESS`	Interface to bind (`0.0.0.0` to accept off-host)	`127.0.0.1`
`ALLOWED_HOSTS`	Extra `Host` headers to accept (comma-separated); loopback always allowed	(loopback only)
`ALLOWED_ORIGINS`	CORS origins for browser clients (comma-separated; `*` allows any)	(none)
`TRUST_PROXY`	Express `trust proxy` when behind a reverse proxy: a hop count, `true`, or a subnet preset (`loopback`)	off

Security

The defaults are safe for local use and must be widened deliberately for a public deployment — see SECURITY.md:

Bind loopback by default. BIND_ADDRESS stays 127.0.0.1 until you set otherwise; 0.0.0.0 exposes the server on every interface and logs a warning.
Host allowlist. Requests whose Host is not loopback or in ALLOWED_HOSTS get 421 Misdirected Request — a DNS-rebinding defence. Add your public hostname when binding publicly.
CORS is closed by default. No cross-origin browser request is accepted until you list its origin in ALLOWED_ORIGINS. Non-browser clients (no Origin header) are unaffected.
Terminate TLS in front. Run the server behind a reverse proxy / load balancer that handles HTTPS; do not expose plain HTTP to the internet.

How It Works

The server talks to Hydra DB through the generated @hydradb/sdk (pinned exactly), behind a thin hand-owned wrapper in src/hydra. The wrapper owns scope injection, envelope unwrapping and error translation; the tools call it and render the results.

hydradb_query retrieves relevant memories and returns graph-enriched context (entity paths, chunk relations, extra context). Supports fast and thinking recall modes.
hydradb_ingest stores a note (text) or a conversation (turns) as a memory, with configurable infer, is_markdown, title, and source_id. Hydra DB extracts insights and builds a knowledge graph automatically.
hydradb_list browses stored memories (kind: memory) or ingested knowledge sources (kind: knowledge, with an optional source_ids filter).
hydradb_inspect retrieves the original ingested content of a source, with mode options (content, url, or both).
hydradb_delete removes a memory or knowledge source by ID.

Development

npm ci
npm run build
HYDRADB_API_KEY=your-key HYDRADB_DATABASE=your-database npm start

For development with auto-reload:

HYDRADB_API_KEY=your-key HYDRADB_DATABASE=your-database npm run dev

To run the HTTP transport locally (see Remote / hosted server):

HYDRADB_API_KEY=your-key HYDRADB_DATABASE=your-database npm run dev:http
# then: curl localhost:8080/health

Testing

# unit + conformance tests (wrapper driven against a mocked SDK transport)
npm test

# just the shared conformance vectors
npm run test:conformance

# live integration test against Hydra DB (drives the wrapper end to end)
RUN_LIVE_TESTS=true HYDRADB_API_KEY=your-key HYDRADB_DATABASE=your-database npm run test:integration

Troubleshooting

API Key Issues: Ensure HYDRADB_API_KEY is set correctly
Connection Errors: Check your internet connection and API key validity
Tool Not Found: Make sure the package is installed and the command path is correct
Debug Logging: Set HYDRADB_LOG_LEVEL=DEBUG for verbose output

Contributing / Developer Setup

Get up and running quickly with the bootstrap script:

git clone https://github.com/usecortex/hydradb-mcp.git
cd hydradb-mcp
make bootstrap

This will install dependencies, build the project, and create a .env file from .env.example. Edit .env with your HydraDB credentials, then:

make dev          # Start MCP server in dev mode (auto-reload)
make test         # Run unit tests
make test-all     # Run unit + integration tests
make check-types  # Type-check without emitting

Run make help to see all available targets.

Name		Name	Last commit message	Last commit date
.github		.github
conformance		conformance
scripts		scripts
src		src
tests		tests
tools/oxlint/anti-slop		tools/oxlint/anti-slop
.dockerignore		.dockerignore
.env.example		.env.example
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRACT.md		CONTRACT.md
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
SECURITY.md		SECURITY.md
biome.json		biome.json
oxlint.config.ts		oxlint.config.ts
package-lock.json		package-lock.json
package.json		package.json
scope.png		scope.png
tsconfig.json		tsconfig.json

Navigation Menu

Repository files navigation

Hydra DB — MCP Server

Available Tools

Graph tools (Cypher)

Deprecated aliases

hydradb_query

hydradb_ingest

hydradb_list

hydradb_inspect

hydradb_feedback

hydradb_subgraph

hydradb_delete

hydradb_status

Configuration

Get Your Credentials

Environment Variables

Claude Desktop

Cursor & Windsurf

VS Code

Custom Sub-Tenant

Remote / hosted server

Point a client at a URL

Run the HTTP server

Sign in with HydraDB (OAuth)

Server environment variables

Security

How It Works

Development

Testing

Troubleshooting

Contributing / Developer Setup

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Hydra DB — MCP Server

Available Tools

Graph tools (Cypher)

Deprecated aliases

hydradb_query

hydradb_ingest

hydradb_list

hydradb_inspect

hydradb_feedback

hydradb_subgraph

hydradb_delete

hydradb_status

Configuration

Get Your Credentials

Environment Variables

Claude Desktop

Cursor & Windsurf

VS Code

Custom Sub-Tenant

Remote / hosted server

Point a client at a URL

Run the HTTP server

Sign in with HydraDB (OAuth)

Server environment variables

Security

How It Works

Development

Testing

Troubleshooting

Contributing / Developer Setup

About

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages