sql-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SQL_USER | Yes | The database user (e.g., sa). | |
| SQL_SERVER | Yes | The SQL Server hostname or instance. | |
| SQL_DATABASE | Yes | The database name. | |
| SQL_PASSWORD | Yes | The database password. | |
| SQL_CONNECTIONS | No | Optional comma-separated list of additional database aliases. For each alias, define SQL_<ALIAS>_SERVER, SQL_<ALIAS>_DATABASE, SQL_<ALIAS>_USER, and SQL_<ALIAS>_PASSWORD. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List the database aliases this server is configured to connect to. |
| queryA | Run a read-only SELECT query against the database and return the results as rows. |
| list_tablesB | List all tables and views in the database. |
| describe_tableA | List the columns and types for a given table. |
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 distinct purpose: list_tables returns the table list, describe_table provides schema for one table, list_databases shows configured connections, and query executes arbitrary SELECT statements. There's no overlap; an agent can easily determine which tool to use for a given task.
The first three tools follow a clear verb_noun pattern (list_tables, describe_table, list_databases). The fourth tool, 'query', is a single verb and doesn't fit the pattern cleanly, but it's still intuitive and not confusing.
With only 4 tools, the server is well-scoped for its purpose. Each tool is essential for database exploration and querying, and the count is within the ideal 3-15 range. The small number avoids redundancy and keeps the interface focused.
For a read-only SQL query server, the surface is complete: list databases to see connections, list tables, describe a table's schema, and run arbitrary SELECT queries. There are no obvious gaps for the stated purpose, and the read-only constraint is explicit.