MCP for making queries to MySQL, PosgreSQL
MCP for making queries to MySQL, PosgreSQL. That is what the mcp sql server mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
The server publishes 9 tools. What each one is for:
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 orParameters — - dbType: Type of the database (mysql, postgresql or sqlite)connectionString — Connection string for the database (file path for sqlite)query — SQL query to executeinsert_data — Insert data into a specified tabletableName — Name of the table to insert intodata — JSON object representing the data to insert (key-value pairs)Tools — The Tools tool exposed by this serverDebugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Sql Server's toolset — execute_sql_query, Parameters, connectionString and 6 more — is a fair guide to whether it matches your workflow. It is maintained by VlaadislavKr; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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. |
| tableName | Name of the table to insert into. |
| data | JSON object representing the data to insert (key-value pairs). |
| Tools | The Tools tool exposed by this server. |
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script: |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.