MySQL MCP by InsightfulPipe
Server Details
Hosted MySQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- Insightful-Pipe/mysql-mcp-server
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
The tools are mostly distinct: query_data is read-only SQL, execute_action is write SQL/DDL, query_contexts is a planning helper, and prompts_menu is a prompt catalog. There is minor potential confusion between execute_action and available_actions returned by query_contexts, and both query_data and execute_action are labeled as Step 3 final tools, but the read/write split is clear enough in the descriptions.
Three tools follow a clear verb_noun pattern: query_contexts, query_data, and execute_action. prompts_menu is noun_noun and does not describe its list/get operations, but it remains readable and is the only notable deviation.
Four tools is a reasonable, well-scoped surface for a MySQL MCP: read, write, planning/context discovery, and prompt access. Each tool has a plausible role, and the set is not bloated or dangerously thin.
The core database lifecycle is covered: query_contexts helps discover accounts/actions, query_data handles reads, and execute_action handles writes and DDL. Dedicated schema/table introspection or transaction-control tools are absent, but those operations can largely be performed through SQL, so the gaps are minor.
Available Tools
4 toolsexecute_actionmysql Data Execute ActionADestructiveInspect
Execute mysql action (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before executing.
execute_action runs write SQL (INSERT/UPDATE/DELETE/DDL). Writes succeed only if your workspace role allows writes and the connected database role has the needed privileges.
Inputs: body (required). Returns: object
query_contextsmysql Setup HelperARead-onlyInspect
Helper for planning InsightfulPipe mysql requests.
Step 1: request='accounts' – Retrieve workspace_id, brand_id, connection_slug, other source metadata, AND available_actions (all read-only actions you can call).
Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, and notes for each action.
Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).
Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.
Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object
query_datamysql DataARead-onlyInspect
Query mysql data (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before querying.
query_data accepts read-only SQL only: a single SELECT (or EXPLAIN) statement. Write statements (INSERT/UPDATE/DELETE/DDL) are rejected here - send them through execute_action.
Inputs: body (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Hosted SQL Server MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Hosted X Ads MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Hosted PostgreSQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Hosted Notion MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server that allows Claude AI to interact directly with MySQL databases, enabling query execution and table information retrieval through natural language.14 npm4MIT
- AlicenseCqualityDmaintenanceAn MCP server that enables MySQL database integration with Claude. You can execute SQL queries and manage database connections.29MIT
- FlicenseNot gradedqualityDmaintenanceA production-grade MCP server that connects Claude to multiple MySQL Docker containers on a VPS, with built-in SSH tunnel management and security features.-
- AlicenseBqualityDmaintenanceMySQL datasource MCP server for AI clients like Cursor and Claude Desktop, enabling SQL query execution via natural language.110 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.