mcp model-context-protocol mysql cursor n8n
mcp model-context-protocol mysql cursor n8n. Exposed over MCP by the @davewind/mysql mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A Model Context Protocol server that provides read-only access to Mysql databases. This server enables LLMs to inspect database schemas and execute read-only queries.
Everything the assistant can do here goes through one of these:
query — Execute read-only SQL queries against the connected databaseInput — sql (string): The SQL query to executeTools — The Tools tool exposed by this serverResources — The server provides schema information for each table in the database:Test — The Test tool exposed by this server@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
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. @Davewind/Mysql's toolset — query, Input, Tools and 2 more — is a fair guide to whether it matches your workflow. It is maintained by dave-wind; 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 |
|---|---|
| query | Execute read-only SQL queries against the connected database |
| Input | sql (string): The SQL query to execute |
| Tools | The Tools tool exposed by this server. |
| Resources | The server provides schema information for each table in the database: |
| Test | The Test tool exposed by this server. |
{
"mcpServers": {
"mysql-mcp-server-dave-wind": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
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.