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

What it enables

Give agents tools without rebuilding the backend.

The MCP server is the fastest way to expose RushDB to assistants and coding agents. The important part is not just access; it is discovery-first access that reduces hallucinated labels, fields, and query operators.

Hosted or local connection

Use hosted OAuth for web assistants or a local npx server for desktop and coding clients.

Database operations as tools

Agents can browse structure, query records, manage relationships, run bulk operations, export data, and use transactions.

Discovery before execution

The documented workflow starts with ontology, classifies intent, loads the query spec when needed, and then builds the tool call.

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.

Flow

Agent request to grounded query

RushDB MCP is designed around discovery before action, so the agent checks available structure before constructing record searches or mutations.

User asks

Load ontology

Classify intent

Load query spec

Execute tool

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": ["-y", "@rushdb/mcp-server"],
      "env": {
        "RUSHDB_API_KEY": "your-key"
      }
    }
  }
}

Know the operational boundary.

MCP-compatible clients

Compatibility depends on the client implementing MCP. Use the setup path documented for the client you are connecting.

Read the MCP server guide

Skills complement runtime tools

MCP gives agents tools. Agent skills can add task-specific instructions for querying, modeling, and persistent memory workflows.

Read about agent skills