AI agents using Markdown + RAG score 0% recall on "why?" questions. The same agents using Right Reasons score 100%. Tested across 48 sessions with 2
Most database access work still happens through a UI a human drives. Right Reasons MCP server moves it into the conversation instead. AI agents using Markdown + RAG score 0% recall on "why?" questions. The same agents using Right Reasons score 100%. Tested across 48 sessions with 2 independent judges. Full experiment results →.
The server publishes 14 tools. What each one is for:
list_objects — List objects filtered by layer, type, search, validation statusget_object — Full details of a single objectlist_relations — List relations with assertion explanationsget_relation_assertion — Full assertion history for a relationtraverse_graph — Navigate the ontology graph — trace "why?" chainsget_schema_info — All object types (14) and relation types (20)get_authentication_trail — Audit trail: who proposed, confirmed, validatedget_explanation_packet — Complete context for an object in one callquery_sql — Read-only SQL for advanced queriescreate_session — Start an EPICAL intake sessionpropose_object — Stage a candidate object (requires authentication before promotion)propose_relation — Stage a candidate relationConfiguration is passed through the environment: RR_DOLT_HOST, RR_DOLT_PORT, RR_DOLT_DATABASE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Right Reasons's toolset — list_objects, get_object, list_relations and 11 more — is a fair guide to whether it matches your workflow. It is maintained by right-reasons; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list_objects | List objects filtered by layer, type, search, validation status |
| get_object | Full details of a single object |
| list_relations | List relations with assertion explanations |
| get_relation_assertion | Full assertion history for a relation |
| traverse_graph | Navigate the ontology graph — trace "why?" chains |
| get_schema_info | All object types (14) and relation types (20) |
| get_authentication_trail | Audit trail: who proposed, confirmed, validated |
| get_explanation_packet | Complete context for an object in one call |
| query_sql | Read-only SQL for advanced queries |
| create_session | Start an EPICAL intake session |
| propose_object | Stage a candidate object (requires authentication before promotion) |
| propose_relation | Stage a candidate relation |
| promote_candidate | Promote authenticated candidate to canonical |
| generate_ops_contract | Auto-generate reasoning envelope from ontology for external work |
| Variable | Description | Required |
|---|---|---|
| RR_DOLT_HOST | Endpoint or connection string the server talks to. | Optional |
| RR_DOLT_PORT | Configuration value read at startup. | Optional |
| RR_DOLT_DATABASE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.