pmi-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host used for Streamable HTTP. Default is '127.0.0.1'. | 127.0.0.1 |
| MCP_PORT | No | Port used for Streamable HTTP. Default is '8000'. | 8000 |
| MCP_TRANSPORT | No | Transport protocol: 'stdio' or 'streamable-http'. Default is 'stdio'. | stdio |
| MCP_BEARER_TOKEN | No | Optional bearer token (at least 32 characters) required for HTTP requests. If set, all HTTP calls must include an Authorization header with this token. | |
| MCP_TLS_KEY_FILE | No | Path to TLS private key file in PEM format. | |
| MCP_TLS_CERT_FILE | No | Path to TLS certificate file in PEM format. | |
| MCP_TLS_KEY_PASSWORD | No | Optional password for the TLS private key. | |
| SQLSERVER_AUTOCOMMIT | No | If 'false', the server commits at end of request and rolls back on error. Default is 'false'. | false |
| SQLSERVER_CONNECTION_STRING | Yes | The ADO.NET connection string for SQL Server, e.g. DRIVER={ODBC Driver 18 for SQL Server};SERVER=localhost,1433;DATABASE=my_database;UID=my_user;PWD=my_password;Encrypt=yes;TrustServerCertificate=no | |
| SQLSERVER_CONNECTION_TIMEOUT | No | Connection timeout in seconds. Default is '30'. | 30 |
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 |
|---|---|
| execute_queryA | Execute the supplied SQL text verbatim on SQL Server and return all result sets. |
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 1 tool
With only one tool, there is no possibility of selecting between overlapping tools. The single tool's purpose is clearly defined as executing SQL text.
The sole tool name 'execute_query' follows a clear and conventional verb_noun pattern. There are no other tools to create inconsistency, so the naming is perfectly coherent within the set.
A single tool feels thin for an MCP server, even if the tool itself is powerful. The count is borderline rather than extreme, as the tool could conceivably serve a narrow SQL execution purpose.
The execute_query tool can perform any SQL operation, including CRUD and metadata queries via system catalogs, so core functionality is present. However, there are no built-in convenience tools for schema discovery or non-query execution, requiring agents to work around this via SQL text.