Semantic Perch Intelligence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| D1_DEV_DATABASE_ID | Yes | The database ID for the development environment | |
| D1_PROD_DATABASE_ID | No | The database ID for the production environment (optional) | |
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token with D1 read permissions | |
| D1_DEV_DATABASE_NAME | Yes | The database name for the development environment | |
| CLOUDFLARE_ACCOUNT_ID | Yes | Your Cloudflare account ID | |
| D1_PROD_DATABASE_NAME | No | The database name for the production environment (optional) | |
| D1_STAGING_DATABASE_ID | No | The database ID for the staging environment (optional) | |
| D1_STAGING_DATABASE_NAME | No | The database name for the staging environment (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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
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.) |
| compare_schemasA | Compare database schemas between environments to detect drift and plan migrations with ICE-scored differences |
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 5 tools
The tools are largely distinct, but there is some overlap between 'analyze_database_schema' and 'get_table_relationships', where the former includes relationships as part of its analysis. However, each tool has a clear primary focus, so an agent can usually select the right one based on context.
All tool names follow a consistent verb_noun pattern: analyze, get, validate, suggest, compare. The naming is predictable and makes it easy to infer the action and target of each tool.
With 5 tools, the server is well-scoped for its stated purpose of database schema intelligence. Each tool covers a distinct aspect without redundancy, making the surface area manageable.
The tool set covers the full lifecycle of schema analysis: inspection, relationship mapping, validation, optimization suggestions, and comparison. There are no obvious gaps for the intended functionality.