SQL MCP Server
# SQL MCP Server
A Model Context Protocol (MCP) server implementation for SQL databases, providing a standardized interface for interacting with SQL databases through the MCP protocol.
## Installation
<details>
<summary><b>Install in Widsurf</b></summary>
```json
{
"mcpServers": {
"sql-mcp": {
"command": "npx",
"args": ["@adetxt/sql-mcp"]
}
}
}
```
</details>
<details>
<summary><b>Install in Cursor</b></summary>
```json
{
"mcpServers": {
"sql-mcp": {
"command": "npx",
"args": ["@adetxt/sql-mcp"]
}
}
}
```
</details>
<details>
<summary><b>Install in VS Code</b></summary>
```json
{
"mcp": {
"servers": {
"sql-mcp": {
"type": "stdio",
"command": "npx",
"args": ["@adetxt/sql-mcp"]
}
}
}
```
</details>
## License
MIT
## Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
## Support
For support, please open an issue in the [GitHub repository](https://github.com/adetxt/sql-mcp/issues).
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: execute_query runs queries, get_columns lists columns in a table, and get_tables lists tables in a database. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern (execute_query, get_columns, get_tables) with clear, descriptive verbs and nouns. No deviations or mixed conventions are present.
With only 3 tools, the server feels thin for an SQL domain, lacking operations like insert, update, delete, or schema modifications. While the tools are well-defined, the count is borderline low for comprehensive database interaction.
The tool set is severely incomplete for an SQL server, missing essential CRUD operations (e.g., insert, update, delete) and schema management tools. This will cause significant agent failures when trying to perform common database tasks beyond basic queries and metadata retrieval.