Cloudflare D1 Database MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API Token with D1:Edit permissions | |
| CLOUDFLARE_ACCOUNT_ID | Yes | Your Cloudflare Account ID | |
| CLOUDFLARE_D1_DATABASE_ID | Yes | Your Cloudflare D1 Database ID | |
| CLOUDFLARE_D1_DATABASE_NAME | Yes | Your Cloudflare D1 Database Name |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| d1_queryC | Run a SQL query against the configured Cloudflare D1 database. |
| d1_list_tablesB | List tables available in the Cloudflare D1 database. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one lists tables (metadata operation) and the other executes SQL queries (data operation). There is no overlap or ambiguity between these functions, making it impossible for an agent to confuse them.
Both tools follow a consistent 'd1_verb_noun' naming pattern with clear, descriptive names. The prefix 'd1_' identifies the domain, and the verb-noun structure (list_tables, query) is uniformly applied across all tools.
With only 2 tools, this server feels severely under-scoped for a database management system. While the tools cover basic operations, typical database interfaces require more functionality (e.g., create/delete tables, schema management, transaction support) to be practically useful for agents.
The toolset is significantly incomplete for database operations. While listing tables and running queries are foundational, there are major gaps: no table creation/deletion, no schema modification, no transaction control, and no specialized query helpers. This will cause agent failures for common database workflows.