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.

• 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).

Development

Install dependencies:

Build the server:

For development with auto-rebuild:

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

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.json or 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:

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.

• 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).

Development

Install dependencies:

Build the server:

For development with auto-rebuild:

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

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.json or 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:

The Inspector will provide a URL to access debugging tools in your browser.