MCP server
Expose your saved QoreDB connections to AI agents through a read-only Model Context Protocol server. Mutations are blocked at the source.
qore-mcp is a read-only Model Context Protocol server for QoreDB. It lets an AI agent — Claude, or any MCP-capable client — discover and query the database connections you already saved in the desktop app, without ever being able to change your data.
It reuses the same engine and the same vault as the desktop app, so the agent inherits your saved connections with no extra credential wiring. Every session is opened read-only and the existing safety gates reject any mutation, so the worst an agent can do is read.
How it works
- Transport: stdio. The MCP client spawns the
qore-mcpbinary and speaks JSON-RPC over standard input/output. There's no network port to open. - Shared credentials. Connections and passwords are read from the same OS keyring and config directory as the desktop app (the vault, project
default). If the desktop can connect, so can the server. - Read-only by construction. Every session is opened with
read_only = true. The same preflight and execute gates used by the app reject any mutation before it reaches the database.
Tools exposed
The server advertises five tools to the agent:
| Tool | What it does |
|---|---|
list_connections | List saved connections (id, name, driver, host, database, environment). |
list_namespaces | List databases/schemas for a connection. |
list_tables | List tables/collections in a namespace. |
describe_table | Columns and keys of a table/collection. |
run_query | Run a read-only query and return the rows. |
Together these let an agent explore a schema and answer questions about the data — "how many orders shipped last week?", "what columns does the customers table have?" — while mutations stay impossible.
Building and registering it
Build the binary from the QoreDB workspace, then register it with your MCP client:
cargo build -p qore-mcp --release # produces target/release/qore-mcp
claude mcp add qoredb -- /absolute/path/to/target/release/qore-mcpSet QOREDB_CONFIG_DIR if your config lives outside the desktop app's default directory.
Where to go next
- Command-line access for the same connections from scripts and CI
- AI features for the in-app AI assistant
- Best practices for safe access patterns
Stay updated on new releases
Subscribe to get product releases, new drivers notifications, and technical tutorials.