mcp-query
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsA | List all configured database connections with their driver, database, and permission level. |
| list_tablesA | List all tables in a database. Args: connection: Name of the database connection to use. |
| describe_tableA | Show the structure of a database table (columns, types, keys). Args: connection: Name of the database connection to use. table: Name of the table to describe. |
| queryA | Execute a SQL query on a database connection. The query type is checked against the connection's allowed operations. Permissions can be a preset (read, write, admin) or a custom list of allowed operations (e.g. [select, insert]). Multi-statement queries are blocked. SELECT queries have an automatic row limit. Args: connection: Name of the database connection to use. sql: The SQL query to execute. |
| query_logA | Show recent query audit log entries. Args: connection: Filter by connection name (empty = all connections). limit: Maximum number of entries to return (default 20). |
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
Each tool has a clearly distinct purpose: describe_table for table structure, list_connections for available connections, list_tables for tables, query for executing SQL, and query_log for auditing. No overlaps.
All tool names follow a consistent verb_object pattern in snake_case (e.g., describe_table, list_connections). No mixing of styles or vague verbs.
With 5 tools, the server is well-scoped for its purpose of database querying. It covers essential operations without being too minimal or excessive.
The tool surface covers the main workflow: listing connections, exploring schema, executing queries, and auditing. Minor gap is lack of a tool to preview query result schema, but core functionality is complete.