Semantic D1 MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| D1_DEV_DATABASE_ID | Yes | Your development D1 database ID | |
| D1_PROD_DATABASE_ID | No | Your production D1 database ID (optional) | |
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token with D1 access | |
| D1_DEV_DATABASE_NAME | Yes | Your development D1 database name | |
| CLOUDFLARE_ACCOUNT_ID | Yes | Your Cloudflare account ID | |
| D1_PROD_DATABASE_NAME | No | Your production D1 database name (optional) | |
| D1_STAGING_DATABASE_ID | No | Your staging D1 database ID (optional) | |
| D1_STAGING_DATABASE_NAME | No | Your staging D1 database name (optional) |
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 |
|---|---|
| analyze_database_schemaB | Analyze D1 database schema structure, tables, columns, indexes, and relationships with optional sample data |
| get_table_relationshipsB | Extract and analyze foreign key relationships between tables in the database |
| validate_database_schemaB | Validate database schema integrity and detect potential issues (missing primary keys, orphaned foreign keys, etc.) |
| suggest_schema_optimizationsB | Analyze schema and suggest performance optimizations (missing indexes, redundant indexes, etc.) |
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 4 tools
Each tool has a clearly distinct purpose: schema analysis, relationship extraction, optimization suggestions, and validation. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., analyze_database_schema, get_table_relationships). The naming is uniform and predictable, enhancing readability and usability.
With 4 tools, the server is well-scoped for database schema analysis. Each tool serves a specific, essential function without redundancy, making the count appropriate for the domain.
The toolset covers key aspects of schema analysis (structure, relationships, optimizations, validation), but lacks tools for executing changes or interacting with data directly. However, the provided tools form a coherent set for analysis purposes.