DB-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_LIMIT | No | The maximum number of rows allowed for query results | |
| CUBE_API_URL | Yes | The URL of the Cube.js API endpoint (e.g., http://localhost:4000/cubejs-api/v1) | |
| DENY_MEMBERS | No | Comma-separated list of Cube members (measures or dimensions) to block for security or PII reasons (e.g., Users.email,Users.ssn) | |
| CUBE_JWT_SECRET | Yes | The secret used for Cube.js JWT authentication (should be at least 32 characters) |
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 |
|---|---|
| catalog.searchB | Search the data catalog for available measures, dimensions, and segments. Use this to discover what data is available for querying. |
| catalog.describeB | Get detailed information about a specific member including its definition, type, and related members. |
| query.semanticC | Execute a governed semantic query against the data warehouse. Queries are validated against governance policies before execution. |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: catalog.describe provides detailed metadata about a specific member, catalog.search enables discovery of available data elements, and query.semantic executes governed queries. The descriptions clearly differentiate between metadata lookup, discovery, and query execution functions.
All tools follow a consistent dot-separated naming pattern (catalog.describe, catalog.search, query.semantic) with clear verb-noun combinations. The naming convention is uniform throughout the set, making it easy to understand the tool hierarchy and relationships.
With only 3 tools, the set feels somewhat thin for a database/warehouse MCP server. While the tools cover key functions (metadata, discovery, querying), typical database interfaces would include more operations like data modification, schema management, or connection handling. The count is borderline minimal but functional.
The tools cover discovery (search), metadata inspection (describe), and query execution, but there are notable gaps for a complete database interface. Missing are data modification operations (insert/update/delete), schema management tools, connection/configuration management, and monitoring/debugging capabilities. The surface enables read operations but lacks write capabilities.