Durable Objects keep state in private SQLite databases with no query path outside the dashboard. This adds one: discover the classes, read the schema of an instance, then run SELECTs against it - read-only by design.
An unofficial MCP server for Durable Object storage, deployed as a Worker of your own that binds to your DO namespaces and calls a query method on each instance. It lists the classes it can reach, describes the tables inside one named instance, and runs read-only SQL against them.
- The Durable Object classes the Worker is bound to
- The tables and columns inside one instance, by class and name
- Read-only SQL run against that instance's storage
- Authentication at the edge through Cloudflare Access, with JWTs verified against the Access JWKS and PKCE enforced on the client
Your own Cloudflare deployment: the Worker binds to DO namespaces by script_name, and access is governed by a Cloudflare Access policy, so revoking a user in your identity provider cuts their session at the next token refresh. Bind only the namespaces you need - Durable Objects routinely hold session tokens, personal data and conversation history, and everything bound is readable by whoever the policy admits.
One command — claude mcp add --transport http do-explorer https://your-worker.workers.dev/mcp