# How to integrate HydraDB MCP with Hermes

```json
{
  "title": "How to integrate HydraDB MCP with Hermes",
  "toolkit": "HydraDB",
  "toolkit_slug": "hydradb",
  "framework": "Hermes",
  "framework_slug": "hermes-agent",
  "url": "https://composio.dev/toolkits/hydradb/framework/hermes-agent",
  "markdown_url": "https://composio.dev/toolkits/hydradb/framework/hermes-agent.md",
  "updated_at": "2026-11-17T05:37:37.344Z"
}
```

## Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.
This guide explains the easiest and most robust way to connect your HydraDB account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.
For exact tool slugs and parameter tables, see the [tool catalog in the Composio docs](https://docs.composio.dev/toolkits/hydradb).

## Also integrate HydraDB with

- [ChatGPT](https://composio.dev/toolkits/hydradb/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/hydradb/framework/claude-cowork)
- [Atomic Agent](https://composio.dev/toolkits/hydradb/framework/atomic-agent)

## TL;DR

### What is Composio Connect?
Composio Connect is a consumer offering that lets anyone plug 1,700+ applications directly into their agent harness — including Hermes. It can:
- Search and load tools from relevant toolkits on-demand, reducing context usage.
- Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
- Manage app authentication end-to-end with zero manual overhead.

## Connect HydraDB to Hermes

### Integrating HydraDB with Hermes
### Using Composio Connect CLI
1. Install the Composio CLI
Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

```bash
curl -fsSL https://composio.dev/install | bash
```

## What is the HydraDB MCP server, and what's possible with it?

The HydraDB MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your HydraDB account. It provides structured and secure access to your databases, collections, connected data sources, contexts, and indexing workflows, so your agent can ingest data, search knowledge, manage connected providers, explore relationships, and monitor processing on your behalf.
- Knowledge ingestion and search: Have your agent add documents, application knowledge, memories, or graph data to HydraDB, then query the resulting context with filters for collections, metadata, sources, access controls, and retrieval settings.
- Database and collection management: Let the agent create, inspect, list, and remove HydraDB databases and collections, check database readiness, review usage statistics, and manage metadata schema fields.
- Connected data source management: Direct your agent to review supported connector providers, create and configure connectors, discover available resources, select resources for syncing, pause or resume connectors, trigger syncs, and check connector health.
- Context exploration and processing: Instruct your agent to inspect stored context, check ingestion status, list knowledge or memory contexts, retrieve extracted relations, and traverse related context subgraphs.
- Indexing webhook operations: Have your agent register and test indexing webhooks, manage signing secrets, review delivery attempts, retry failed deliveries, and remove webhook registrations.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `HYDRADB_ADD_CONNECTOR_RESOURCE` | Add Connector Resource | Add one discovered provider resource to an existing connector with optional routing, filters, metadata, instructions, and access control. |
| `HYDRADB_ADD_METADATA_SCHEMA_FIELDS` | Add Metadata Schema Fields | Add new fields to a database metadata schema; existing fields cannot be deleted, renamed, retyped, or reconfigured. |
| `HYDRADB_CONFIGURE_CONNECTOR_RESOURCES` | Configure Connector Resources | Activate selected discovered resources on a connector and start their sync; unlisted existing resources remain unchanged. |
| `HYDRADB_CREATE_CONNECTOR` | Create Connector | Create a HydraDB connector and store the provider authorization required to sync one external account. Obtain the provider-specific shape from List Connector Providers. |
| `HYDRADB_CREATE_DATABASE` | Create Database | Provision a HydraDB database asynchronously. This may create billable infrastructure; poll Get Database Status before ingestion. |
| `HYDRADB_DELETE_COLLECTION` | Delete Collection | Permanently delete one HydraDB collection and all of its data while leaving the database intact. |
| `HYDRADB_DELETE_CONNECTOR` | Delete Connector | Permanently delete a HydraDB connector, all resource mappings, and its stored provider authorization. |
| `HYDRADB_DELETE_CONNECTOR_RESOURCE` | Delete Connector Resource | Permanently remove one resource mapping from a HydraDB connector. |
| `HYDRADB_DELETE_CONTEXT` | Delete Context | Permanently delete specific HydraDB knowledge or memory contexts. Uses strict provider status handling so missing, indexing, and store failures cannot appear successful. |
| `HYDRADB_DELETE_DATABASE` | Delete Database | Permanently delete a HydraDB database and all associated data. This cannot be undone. |
| `HYDRADB_DELETE_INDEXING_WEBHOOK` | Delete Indexing Webhook | Unregister the account's indexing webhook and stop all future event deliveries. |
| `HYDRADB_DISABLE_WEBHOOK_SIGNING` | Disable Webhook Signing | Remove the indexing webhook signing secret. Future deliveries remain enabled but can no longer be authenticated with HydraDB signatures. |
| `HYDRADB_DISCOVER_CONNECTOR_RESOURCES` | Discover Connector Resources | List resources available through an existing connector's stored provider credentials. Discovery pagination is provider-dependent (currently Notion only); other providers may return the complete list despite limit. This may call the external provider. |
| `HYDRADB_GENERATE_WEBHOOK_SIGNING_SECRET` | Generate or Set Webhook Signing Secret | Generate or set and replace the indexing webhook signing secret. The previous secret stops working immediately and the active secret is returned only once. |
| `HYDRADB_GET_CONNECTOR` | Get Connector | Get one connector's configuration and lifecycle state by connector ID. |
| `HYDRADB_GET_CONNECTOR_STATUS` | Get Connector Status | Check a connector's overall health, sync state, errors, and per-resource health in one call. |
| `HYDRADB_GET_CONTEXT_RELATIONS` | Get Context Relations | Return extracted entity relations for one context or an entire collection, one page at a time. |
| `HYDRADB_GET_CONTEXT_STATUS` | Get Context Status | Check processing status for one or more ingested or connector-synced context IDs. |
| `HYDRADB_GET_CONTEXT_SUBGRAPH` | Get Context Subgraph | Traverse context-level relations from one context and return reachable contexts and graph evidence up to bounded depth and size. |
| `HYDRADB_GET_DATABASE_STATS` | Get Database Stats | Get knowledge and memory collection row counts for one database. |
| `HYDRADB_GET_DATABASE_STATUS` | Get Database Status | Check whether one database's scheduler, graph, and vector infrastructure is ready for ingestion. |
| `HYDRADB_GET_INDEXING_WEBHOOK` | Get Indexing Webhook | Get the account's indexing webhook URL, subscribed event types, registration state, and whether signing is configured. |
| `HYDRADB_GET_METADATA_SCHEMA` | Get Metadata Schema | Get the declared metadata fields and types for one database. |
| `HYDRADB_GET_WEBHOOK_DELIVERY` | Get Webhook Delivery | Get one indexing webhook delivery attempt by delivery ID for failure diagnosis. |
| `HYDRADB_INGEST_CONTEXT` | Ingest Context | Ingest documents, app knowledge, memories, or an explicit graph into a HydraDB database and return context IDs for asynchronous status checks. |
| `HYDRADB_INSPECT_CONTEXT` | Inspect Context | Fetch one context's stored content, enrichment, and/or a time-limited download URL. |
| `HYDRADB_LIST_COLLECTIONS` | List Collections | List the collections in one HydraDB database. |
| `HYDRADB_LIST_CONNECTOR_PROVIDERS` | List Connector Providers | List supported connector providers, or describe one provider's resource types, credential schema, and setup requirements. |
| `HYDRADB_LIST_CONNECTOR_RESOURCES` | List Connector Resources | List the resources currently configured on a connector, including routing, filters, access controls, and per-resource health metadata. |
| `HYDRADB_LIST_CONNECTORS` | List Connectors | List the connected data providers in the account, optionally filtered by provider, with optional health rollups. |
| `HYDRADB_LIST_CONTEXTS` | List Contexts | List knowledge or memory contexts in a database or collection, one bounded page at a time. |
| `HYDRADB_LIST_DATABASES` | List Databases | List HydraDB databases and preserve per-database provisioning or failure diagnostics. |
| `HYDRADB_LIST_WEBHOOK_DELIVERIES` | List Webhook Deliveries | List recent indexing webhook delivery attempts, optionally filtered by status, one page at a time. |
| `HYDRADB_QUERY_CONTEXT` | Query Context | Search a HydraDB database for ranked chunks and graph context, with optional collection, metadata, source, ACL, and retrieval controls. |
| `HYDRADB_REGISTER_INDEXING_WEBHOOK` | Register Indexing Webhook | Register or replace the organization's HTTPS endpoint and event subscriptions for HydraDB indexing events. This call can preserve the existing signing secret, generate and return a new one, or install a caller-supplied secret. |
| `HYDRADB_RETRY_WEBHOOK_DELIVERY` | Retry Webhook Delivery | Queue one failed indexing webhook delivery for another attempt. This repeats an external callback and may repeat downstream side effects. |
| `HYDRADB_SET_CONNECTOR_PAUSED` | Set Connector Paused State | Pause scheduled syncs or resume a paused HydraDB connector. Resuming immediately schedules a sync from the connector's saved positions. |
| `HYDRADB_SUBMIT_QUERY_FEEDBACK` | Submit Query Feedback | Record a rating, comment, or known ground truth for a prior HydraDB query. This optional signal does not change the original query result. HydraDB allows 100 feedback submissions per minute per organization; if rate limited, skip the report rather than retrying in a loop. |
| `HYDRADB_TEST_INDEXING_WEBHOOK` | Test Indexing Webhook | Send one test event to the currently registered indexing webhook endpoint. |
| `HYDRADB_TRIGGER_CONNECTOR_SYNC` | Trigger Connector Sync | Start a connector sync now, causing external provider reads and HydraDB ingestion. If a sync is already running, it continues; paused connectors and connectors without active resources fail. |
| `HYDRADB_UPDATE_CONNECTOR` | Update Connector | Update an existing HydraDB connector's sync cadence, default ingestion instructions, or provider credentials. Replacing credentials requires explicit confirmation. |
| `HYDRADB_UPDATE_CONNECTOR_RESOURCE` | Update Connector Resource | Replace a HydraDB connector resource's access rules or change its ingestion instructions for subsequent syncs. |
| `HYDRADB_UPDATE_CONTEXT_METADATA` | Update Context Metadata | Merge metadata into one HydraDB context or replace its access-control list without re-ingesting content. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The HydraDB MCP server provides comprehensive access to HydraDB operations through Composio. Once connected, Hermes can perform all major HydraDB actions on your behalf using natural language commands.

## Complete Code

None listed.

## Conclusion

### Way Forward
With HydraDB connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.
From here, you can extend Hermes further:
- Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
- Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
- Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.
If you run into trouble or want to share what you've built, join the [community](https://discord.com/invite/composio) or check out the [Docs](https://docs.composio.dev?cta_placement=toolkit-framework-hermes-docs) for deeper configuration options.

## How to build HydraDB MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/hydradb/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/hydradb/framework/claude-cowork)
- [Atomic Agent](https://composio.dev/toolkits/hydradb/framework/atomic-agent)

## Related Toolkits

- [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.
- [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service.
- [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows.
- [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow.
- [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows.
- [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application.
- [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities.
- [AllModels](https://composio.dev/toolkits/allmodels) - AllModels is a unified API for text-to-speech, speech-to-text, realtime voice, and voice cloning across AI providers. It gives developers one consistent way to build and manage voice features.
- [AltTextLab](https://composio.dev/toolkits/alt_text_lab) - AltTextLab is an AI service that generates accessible, SEO-aware alt text for images. It helps teams make image content easier to understand, index, and publish.
- [Anthropic administrator](https://composio.dev/toolkits/anthropic_administrator) - Anthropic administrator is an API for managing Anthropic organizational resources like members, workspaces, and API keys. It helps you automate admin tasks and streamline resource management across your Anthropic organization.
- [Api labz](https://composio.dev/toolkits/api_labz) - Api labz is a platform offering a suite of AI-driven APIs and workflow tools. It helps developers automate tasks and build smarter, more efficient applications.
- [Apiframe](https://composio.dev/toolkits/apiframe) - Apiframe is an API platform for generating and managing AI images, videos, music, uploads, assets, jobs, and custom LoRAs. It gives developers one clean API for creative AI workflows without juggling multiple model providers.
- [Apipie ai](https://composio.dev/toolkits/apipie_ai) - Apipie ai is an AI model aggregator offering a single API for accessing top AI models from multiple providers. It helps developers build cost-efficient, latency-optimized AI solutions without juggling multiple integrations.
- [Arize AX](https://composio.dev/toolkits/arize_ax) - Arize AX is an AI engineering platform for tracing, evaluating, and improving AI applications. Use it to debug LLM behavior, compare experiments, and improve production AI quality.
- [Artificial Analysis](https://composio.dev/toolkits/artificial_analysis) - Artificial Analysis is an independent benchmarking platform for AI models and API providers. Use it to compare model intelligence, coding, math, pricing, latency, throughput, and arena rankings.
- [AssemblyAI](https://composio.dev/toolkits/assemblyai) - AssemblyAI is a speech-to-text and audio intelligence API for uploaded or hosted media. Use it to turn audio and video into accurate transcripts, summaries, and insights.
- [Astica ai](https://composio.dev/toolkits/astica_ai) - Astica ai provides APIs for computer vision, NLP, and voice synthesis. Integrate advanced AI features into your app with a single API key.
- [Avoma](https://composio.dev/toolkits/avoma) - Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence. It helps teams turn conversations into searchable notes, follow-ups, coaching insights, and revenue intelligence.
- [Bigml](https://composio.dev/toolkits/bigml) - BigML is a machine learning platform that lets you build, train, and deploy predictive models from your data. Its intuitive interface and robust API make machine learning accessible and efficient.
- [Black Forest Labs](https://composio.dev/toolkits/bfl) - Black Forest Labs provides hosted FLUX models for generating and editing images and videos. It offers fast, flexible media creation with asynchronous processing and fine-tuning support.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and HydraDB MCP?

With a standalone HydraDB MCP server, the agents and LLMs can only access a fixed set of HydraDB tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from HydraDB and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Hermes?

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right HydraDB tools.

### Can I manage the permissions and scopes for HydraDB while using Tool Router?

Yes, absolutely. You can configure which HydraDB scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your HydraDB data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
