Hydra DB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYDRA_DB_API_KEY | Yes | Your Hydra DB API key | |
| HYDRA_DB_LOG_LEVEL | No | Log level: DEBUG, INFO, WARN, ERROR | ERROR |
| HYDRA_DB_TENANT_ID | Yes | Your Hydra DB tenant identifier | |
| HYDRA_DB_SUB_TENANT_ID | No | Sub-tenant for data partitioning | hydra-db-mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hydradb_queryA | Search through Hydra DB State-of-the-art agentic memories. Returns relevant chunks with graph-enriched context including entity paths and knowledge graph relations. Use this to find previously stored information, past conversations, user preferences, or any knowledge that has been ingested into Hydra DB memory. Supports both fast semantic search and deeper thinking mode with graph traversal. |
| hydradb_ingestA | Save important information to Hydra DB State-of-the-art agentic memory. Use this to persist facts, preferences, decisions, notes, or any text the user wants remembered across sessions. Hydra DB automatically extracts insights, preferences, and builds a knowledge graph from the stored content. Supports plain text and markdown. To ingest a conversation instead of a single note, provide |
| hydradb_listA | List stored memories or ingested knowledge sources in Hydra DB. Use |
| hydradb_inspectA | Fetch the full content of a specific source by its source ID from Hydra DB. Returns the original text content that was ingested. Use this to retrieve the complete content of a previously stored source. |
| hydradb_deleteB | Delete a memory or knowledge source from Hydra DB by its ID. Use |
| hydra_db_searchA | DEPRECATED — use |
| hydra_db_storeA | DEPRECATED — use |
| hydra_db_ingest_conversationA | DEPRECATED — use |
| hydra_db_list_memoriesA | DEPRECATED — use |
| hydra_db_list_sourcesA | DEPRECATED — use |
| hydra_db_fetch_contentA | DEPRECATED — use |
| hydra_db_delete_memoryA | DEPRECATED — use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
The five current tools (hydradb_query, hydradb_ingest, hydradb_list, hydradb_inspect, hydradb_delete) each have a clear, distinct purpose. Deprecated tools are explicitly marked and can be ignored, so an agent can easily select the correct active tool.
There are two naming conventions: current tools use 'hydradb_' prefix with a single verb, while deprecated tools use 'hydra_db_' prefix with varying verb_noun structures. This inconsistency and the presence of both sets create confusion.
With 12 tools, many are deprecated duplicates. The effective set of 5 tools is well-scoped for a memory database server. The count is slightly bloated by deprecated items, but still reasonable.
The tool set covers create (ingest), read (query, list, inspect), and delete, but lacks an update/modify tool. This is a notable gap for full lifecycle management, though the surface is otherwise sufficient.