MCP server

Give agents a direct path to structured memory.

The RushDB MCP server exposes database operations as tools for MCP-compatible clients. Agents can discover structure before they build queries.

Start free View docs

Agent integrations drift when every client gets custom glue code.

A handwritten tool layer needs to expose records, queries, relationships, and error handling consistently. Every new client becomes another integration to maintain.

Before

Build custom database tools for each agent
Teach query syntax in long prompt files
Reimplement schema discovery
Maintain separate integration code per client

With RushDB

Connect an MCP-compatible client
Browse labels and properties through tools
Query and mutate records through one server
Use discovery-first guidance before complex queries

How it works

Start with the smallest useful path.

Add the MCP server

Configure the local package or a hosted MCP connection in a compatible client.

Discover before querying

Use labels, properties, ontology, or the query-builder prompt so the agent works against the real project shape.

Keep operations structured

Create records, attach relationships, run searches, export data, and manage transactions through explicit tools.

Implementation sketch

Add one local MCP server config.

Exact host configuration varies by MCP client. The docs include quickstarts, available tools, examples, and troubleshooting.

{
  "mcpServers": {
    "rushdb": {
      "command": "npx",
      "args": ["@rushdb/mcp-server"],
      "env": {
        "RUSHDB_API_KEY": "your-key"
      }
    }
  }
}