SQL Server for MySQL, PostgreSQL, and SQLite
A server for making queries to MySQL, PostgreSQL, and SQLite databases.
SQL MCP Server for MySQL, PostgreSQL, and SQLite Databases
This is a powerful MCP (Model Context Protocol) server designed for seamless interaction with SQL databases, including MySQL, PostgreSQL, and SQLite. It simplifies how to connect to database MySQL and other SQL types, making it an ideal solution for developers looking for an efficient mcp mysql database integration.
Whether you're building a new application or integrating with existing systems, this server provides the tools you need for managing your data.
Features
This mcp mysql tutorial will guide you through its core functionalities.
Tools
execute_sql_query- Execute SQL queries on a specified database. This tool is essential for running direct commands and is perfect for a mcp mysql github project or any environment where direct SQL execution is needed.- Parameters:
dbType: Type of the database (mysql, postgresql or sqlite).connectionString: Connection string for the database (file path for sqlite).query: SQL query to execute.
- Parameters:
insert_data- Insert data into a specified table.- Parameters:
dbType: Type of the database (mysql, postgresql or sqlite).connectionString: Connection string for the database (file path for sqlite).tableName: Name of the table to insert into.data: JSON object representing the data to insert (key-value pairs).
- Parameters:
Development
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
npm run watch
Installation
To use this mcp mysql server with your editor, you will generally need to configure it to recognize the server. The core principle involves providing the editor with the command to run the compiled server, typically located at build/index.js.
Configuration Examples:
Claude Desktop:
- MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"sql": {
"command": "/path/to/sql/build/index.js"
}
}
}
Other MCP-compatible editors:
The exact configuration method may vary, but here are some common locations for configuration files:
- Roo Code:
%APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\mcp_settings.json - Cursor:
%HOMEPATH%\.cursor(look for a relevant configuration file within this directory, e.g.,mcp_settings.jsonor similar). This setup allows seamless mcp mysql cursor integration.
Consult your editor's official documentation for detailed instructions on adding custom MCP servers.
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspector
The Inspector will provide a URL to access debugging tools in your browser.
Features
Tools
execute_sql_query- Execute SQL queries on a specified database.- Parameters:
dbType: Type of the database (mysql, postgresql or sqlite).connectionString: Connection string for the database (file path for sqlite).query: SQL query to execute.
- Parameters:
insert_data- Insert data into a specified table.- Parameters:
dbType: Type of the database (mysql, postgresql or sqlite).connectionString: Connection string for the database (file path for sqlite).tableName: Name of the table to insert into.data: JSON object representing the data to insert (key-value pairs).
- Parameters:
Development
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
npm run watch
Installation
To use this MCP server with your editor, you will generally need to configure it to recognize the server. The core principle involves providing the editor with the command to run the compiled server, typically located at build/index.js.
Configuration Examples:
Claude Desktop:
- MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"sql": {
"command": "/path/to/sql/build/index.js"
}
}
}
Other MCP-compatible editors:
The exact configuration method may vary, but here are some common locations for configuration files:
- Roo Code:
%APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\mcp_settings.json - Cursor:
%HOMEPATH%\.cursor(look for a relevant configuration file within this directory, e.g.,mcp_settings.jsonor similar)
Consult your editor's official documentation for detailed instructions on adding custom MCP servers.
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspector
The Inspector will provide a URL to access debugging tools in your browser.
संबंधित सर्वर
MCP Iceberg Catalog
An MCP server for interacting with Apache Iceberg catalogs and data lakes.
Pinecone
Read and write to a Pinecone vector database using the Model Context Protocol.
CData Jira Assets
A read-only MCP server for Jira Assets, powered by the CData JDBC Driver.
Supabase
Connects to Supabase platform for database, auth, edge functions and more.
Video Metadata MCP Server
Manages video metadata, including game information, teams, scores, and other sports-related data.
Unofficial Open Targets
Unofficial server for accessing Open Targets platform data for gene-drug-disease associations research.
Generect MCP
Generect MCP connects your live lead database directly to AI models like OpenAI or Claude without exports or delays. It streams enriched, up-to-date contact data (titles, firmographics, signals) straight into prompts so LLMs can personalize, score, and recommend leads automatically in real time.
Engram
Persistent memory layer for AI agents with semantic search, consolidation, and cross-session intelligence via MCP.
Outreach.io by CData
A read-only MCP server for querying live data from Outreach.io using the CData JDBC Driver.
CData Reckon Accounts Hosted
A read-only MCP server by CData that enables LLMs to query live data from Reckon Accounts Hosted. Requires a separate CData JDBC Driver.