Unofficial MCP server for querying Cloudflare Durable Object SQLite storage from AI clients (Claude Code, Cursor, Windsurf, etc.). Gives AI clients
Most database access work still happens through a UI a human drives. Durable Objects MCP MCP server moves it into the conversation instead. Unofficial MCP server for querying Cloudflare Durable Object SQLite storage from AI clients (Claude Code, Cursor, Windsurf, etc.). Gives AI clients structured, read-only access to your DO storage. Connect once, discover tables, run queries.
The server publishes 3 tools. What each one is for:
list_classes — Lists queryable DO classes configured in your deploymentdescribe_schema — Returns tables and columns for a DO instanceexecute_read_query — Executes read-only SQL against a DO instanceSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: ACCESS_CLIENT_ID, ACCESS_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY. 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.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Durable Objects MCP's toolset — list_classes, describe_schema, execute_read_query — is a fair guide to whether it matches your workflow. It is maintained by spawnbase; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Durable Objects MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_classes | Lists queryable DO classes configured in your deployment |
| describe_schema | Returns tables and columns for a DO instance |
| execute_read_query | Executes read-only SQL against a DO instance |
**Cursor** (`~/.cursor/mcp.json`):
```json
{
"mcpServers": {
"do-explorer": { "url": "https://your-worker.workers.dev/mcp" }
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ACCESS_CLIENT_ID | Configuration value read at startup. | Optional |
| ACCESS_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| COOKIE_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
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.