mcp-enterprise-starter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEYS | Yes | Comma-separated list of valid API keys | |
| LOG_LEVEL | No | Logging level | info |
| ROW_LIMIT | No | Default row limit for queries | 100 |
| DATABASE_URL | Yes | PostgreSQL connection string | |
| MAX_ROW_LIMIT | No | Maximum row limit | 1000 |
| MCP_TRANSPORT | No | Transport mode: stdio or sse | stdio |
| ALLOWED_TABLES | No | Tables the agent can access | departments,users,projects |
| RATE_LIMIT_RPM | No | Requests per minute per API key | 60 |
| SENSITIVE_COLUMNS | No | Columns to mask in query results | email,ssn |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_databaseA | Execute a read-only SQL query against the database. Only SELECT statements are allowed. Results from sensitive columns (email, SSN) are automatically masked. Queries are limited to a maximum number of rows. |
| list_tablesA | List all database tables that are available for querying. Returns table names from the configured allowlist. |
| get_schemaA | Get the column schema for a specific database table, including column names, data types, nullability, and constraints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| departments table schema | Column definitions and constraints for the departments table |
| users table schema | Column definitions and constraints for the users table |
| projects table schema | Column definitions and constraints for the projects table |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing tables, getting schema for a specific table, and executing queries. No overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (get_schema, list_tables, query_database), making naming predictable.
3 tools is on the lower end but appropriate for a focused database starter. It covers essential operations without being too sparse.
Core operations (list tables, get schema, query) are present, but missing advanced features like explain plans or index info. Adequate for a starter.