A
licenseNot graded
qualityC
maintenanceModel Context Protocol (MCP) server wrapping mcp-lint to perform static analysis and schema checking on other MCP servers.
MIT
sqlfluff-mcp-server
by gswartwood
Related Servers
Alternatives to sqlfluff-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceMCP server that integrates sql-sop SQL linter into LLM clients, enabling linting SQL queries and listing lint rules via chat tools.2MIT
- AlicenseBqualityAmaintenanceA MCP (Model Context Protocol) server for interacting with dbt.1615,934 PyPI610Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps Spectral to lint OpenAPI specifications, enabling LLMs to validate and fix API definitions.1MIT
- AlicenseAqualityDmaintenanceAn MCP server for executing Malloy queries and managing Malloy resources.52MIT
- AlicenseNot gradedqualityDmaintenanceEnables integration of Semgrep in development environments via the MCP protocol, supporting static code analysis, rule management, and scan result operations.2MIT
TDQS
A4.4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clear, distinct purpose: the three file-based tools operate on paths, the three SQL-based tools operate on raw strings, and list_dialects/clear_config_cache serve separate helper roles. No two tools overlap in a way that would confuse an agent.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: lint/fix/parse paired with file/sql, plus list_dialects and clear_config_cache. The style is uniform (lowercase with underscores) with no mixed conventions.
Tool Count5/5
Eight tools is well-scoped for a SQLFluff wrapper: it covers the core operations (lint, fix, parse) for both file and string inputs, plus a dialect listing and cache-clearing utility. No redundancy and no missing essential operation.
Completeness4/5
The tool surface covers the main SQLFluff functionality comprehensively—lint, fix, and parse for both files and raw SQL. A few advanced capabilities like rendering or rule-specific configuration are absent, but core workflows are fully supported.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive