sql-sop-mcp
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lint_sqlA | Lint a SQL string with sql-sop. Catches dangerous patterns (DELETE/UPDATE without WHERE, SQL injection via string concat, DROP COLUMN, ADD NOT NULL without DEFAULT), SARGability mistakes (function on indexed column, leading-wildcard LIKE, OR across columns), 5 T-SQL specific rules (NOLOCK, xp_cmdshell, deprecated outer join, etc.), and 5 Python source rules for sqlalchemy.text() / cursor.execute() injection. 38 rules in total. Returns one JSON object listing every finding plus a human-readable summary. |
| list_rulesA | List every rule sql-sop ships with. Useful for explaining a finding's full description, picking which rules to disable for a project, or for an LLM to discover what it can use lint_sql to catch. |
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 2 tools
The two tools serve entirely different functions: lint_sql performs analysis, while list_rules provides reference information. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (lint_sql, list_rules) with lowercase and underscores, making them predictable.
With exactly 2 tools, the server is tightly scoped for SQL linting: one core analysis tool and one supporting rule listing tool. This is appropriate for the domain.
The server covers the primary linting action and rule discovery, but lacks a tool to configure or disable specific rules, which may be needed for practical use. Minor gap.