Skip to main content
Glama

MySQL MCP by InsightfulPipe

Server Details

Hosted MySQL MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
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

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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 tools
execute_actionmysql Data Execute ActionA
Destructive
Inspect

Execute mysql action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions

  2. 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

prompts_menumysql PromptsA
Read-only
Inspect

Access mysql prompt catalog with 4 operations:

  1. List Public Prompts: • request='menu' - No additional params needed • Returns: All public/system prompts available for mysql

  2. List Custom Prompts: • request='menu', prompt_type='custom', workspace_id= • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details: • request='prompt_details', prompt_id= • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details: • request='prompt_details', prompt_id=, is_custom=True, workspace_id= • Returns: Full text/details of a custom prompt

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsmysql Setup HelperA
Read-only
Inspect

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 DataA
Read-only
Inspect

Query mysql data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, connection_slug AND available_actions

  2. 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

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server that allows Claude AI to interact directly with MySQL databases, enabling query execution and table information retrieval through natural language.
      1
      4 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-grade MCP server that connects Claude to multiple MySQL Docker containers on a VPS, with built-in SSH tunnel management and security features.
      -
    • A
      license
      B
      quality
      D
      maintenance
      MySQL datasource MCP server for AI clients like Cursor and Claude Desktop, enabling SQL query execution via natural language.
      1
      10 PyPI
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.