What can @benborla29/mcp-server-mysql do?

schema-based mysql query execution via mcp protocol, write-enabled database mutation operations, mcp protocol server implementation for mysql, parameterized query construction with injection prevention, cursor ide and smithery ecosystem integration, connection pooling and lifecycle management

@benborla29/mcp-server-mysql

MCP ServerFree

MCP server for interacting with MySQL databases with write operations support

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

schema-based mysql query execution via mcp protocol

Medium confidence

Exposes MySQL database queries through the Model Context Protocol using a standardized tool schema that Claude and other MCP clients can invoke. Implements MCP server architecture with tool definitions that map to SQL execution, allowing LLM agents to construct and run SELECT, INSERT, UPDATE, DELETE queries against MySQL databases by calling remote procedures rather than direct SQL strings.

Solves for

Enable Claude to query a MySQL database and retrieve structured results for analysis or decision-makingAllow AI agents to perform CRUD operations on database records without direct SQL injection riskIntegrate MySQL data access into multi-step AI workflows where database state affects downstream decisions

Best for

AI developers building Claude-powered database applications

Teams deploying LLM agents that need persistent data access

Cursor IDE users automating database-driven workflows

Requires

Node.js 16+

MySQL 5.7+ or MariaDB 10.2+

Active MySQL connection with network accessibility

Limitations

No built-in query result pagination — large result sets may exceed MCP message size limits

No transaction support — each query executes independently without ACID guarantees across multiple operations

No query optimization hints — LLM-generated queries may be inefficient without developer guidance

What makes it unique

Implements MCP server pattern specifically for MySQL, bridging LLM tool-calling with relational database operations through standardized protocol rather than custom API wrappers or direct SQL exposure

vs alternatives

Provides native MCP integration for MySQL unlike REST API wrappers, enabling direct Claude/Cursor integration without additional HTTP abstraction layers

write-enabled database mutation operations

Medium confidence

Supports INSERT, UPDATE, DELETE, and PATCH operations through MCP tool schema, allowing LLM agents to modify database state directly. Implements parameterized query construction to prevent SQL injection while enabling safe mutation of records based on AI-generated instructions, with operation-specific tool definitions that map to standard HTTP-style semantics (POST for create, PUT for replace, PATCH for partial update).

Solves for

Allow Claude to create new database records based on conversation context or analysis resultsEnable AI agents to update existing records with computed values or correctionsSupport database cleanup or state transitions triggered by LLM decision logic

Best for

Applications requiring AI-driven data entry or record updates

Autonomous agents managing database state as part of workflow execution

Systems where LLM output directly affects persistent data

Requires

MySQL user with INSERT, UPDATE, DELETE privileges on target tables

Table schema known to MCP server configuration

Client-side validation or LLM prompt engineering to prevent invalid mutations

Limitations

No rollback mechanism — failed mutations cannot be automatically reverted

No audit logging built-in — mutations lack automatic tracking of who/when/what changed

No constraint validation before execution — database constraints may reject mutations after LLM constructs them

What makes it unique

Exposes write operations through MCP tool schema with HTTP-style semantics (POST/PUT/PATCH/DELETE), enabling LLM agents to perform mutations with the same tool-calling interface as read operations rather than requiring separate mutation APIs

vs alternatives

Allows safe write operations from LLM agents through parameterized queries and MCP protocol constraints, reducing injection risk compared to exposing raw SQL strings to Claude

mcp protocol server implementation for mysql

Medium confidence

Implements the Model Context Protocol server specification, handling MCP message routing, tool schema registration, and client lifecycle management. Exposes MySQL operations as MCP tools with JSON schema definitions that clients discover and invoke, managing the bidirectional communication channel between MCP clients (Claude, Cursor) and the MySQL database through standardized protocol messages.

Solves for

Enable seamless integration with Claude and Cursor without custom client codeProvide standardized tool discovery so clients know what database operations are availableHandle protocol-level concerns like message serialization, error handling, and connection state

Best for

Developers integrating MySQL with Claude or Cursor IDE

Teams standardizing on MCP for tool integration across multiple services

Organizations using Smithery or mcp-get/mcp-put for MCP server management

Requires

Node.js 16+ with npm or yarn

MCP client that supports tool-calling (Claude 3.5+, Cursor 0.42+)

Network connectivity between MCP client and server

Limitations

MCP protocol overhead adds ~50-100ms per request compared to direct HTTP calls

Tool schema must be pre-defined — dynamic schema discovery not supported

No built-in authentication beyond MySQL credentials — relies on network isolation or client-side validation

What makes it unique

Implements MCP server specification as a Node.js package, handling protocol-level concerns (message routing, schema registration, lifecycle) so developers only configure MySQL connection details rather than implementing protocol mechanics

vs alternatives

Provides out-of-the-box MCP server for MySQL unlike building custom MCP implementations, reducing boilerplate and enabling immediate integration with Claude/Cursor

parameterized query construction with injection prevention

Medium confidence

Constructs SQL queries using parameterized statements with bound variables rather than string concatenation, preventing SQL injection attacks. Implements query building logic that separates SQL structure from data values, ensuring that user-provided or LLM-generated values cannot alter query semantics or access unintended data.

Solves for

Safely execute LLM-generated database queries without risk of injection attacksAllow Claude to construct WHERE clauses and filter conditions without exposing raw SQLPrevent accidental or malicious SQL injection through tool parameters

Best for

Production systems where LLM agents access databases with sensitive data

Applications requiring compliance with security standards (SOC 2, HIPAA)

Teams without dedicated security review for every LLM-generated query

Requires

MySQL driver with parameterized query support (mysql2/promise)

Tool schema that defines allowed columns and operations

LLM prompt engineering to ensure generated parameters match expected types

Limitations

Parameterized queries cannot use dynamic table/column names — schema must be pre-defined

Complex queries with conditional logic may require multiple tool invocations

Performance overhead of parameter binding is negligible but adds ~1-2ms per query

What makes it unique

Implements parameterized query binding at the MCP tool layer, ensuring all LLM-generated database operations are injection-safe by design rather than relying on downstream validation

vs alternatives

Prevents SQL injection at the protocol level unlike systems that expose raw SQL strings to LLMs, providing defense-in-depth for database security

cursor ide and smithery ecosystem integration

Medium confidence

Packages the MySQL MCP server for direct installation and use within Cursor IDE and Smithery MCP registry, enabling one-command setup without manual configuration. Supports mcp-get, mcp-put, mcp-post, mcp-delete, mcp-patch, mcp-options, and mcp-head HTTP-style semantics for tool invocation, allowing Cursor users to access MySQL databases directly from the editor through the MCP ecosystem.

Solves for

Install and configure MySQL database access in Cursor IDE with minimal setupDiscover and use MySQL tools through Smithery registry without manual server deploymentAccess database operations directly from Cursor's AI assistant without external tools

Best for

Cursor IDE users building database-driven applications

Teams using Smithery for centralized MCP server management

Developers who want plug-and-play database integration without DevOps

Requires

Cursor IDE 0.42+

npm or yarn for package installation

MySQL connection details (host, port, user, password, database)

Limitations

Cursor integration requires Cursor 0.42+ with MCP support

Smithery registry discovery depends on package being published and indexed

HTTP-style semantics (mcp-get, mcp-put, etc.) are semantic conventions, not true REST — actual transport is MCP protocol

What makes it unique

Packages MySQL MCP server as an npm module compatible with Cursor IDE and Smithery registry, enabling IDE-native database access through standardized MCP discovery and installation rather than manual server deployment

vs alternatives

Provides native Cursor integration unlike generic MCP servers, allowing developers to query databases directly from the editor without context-switching to external tools

connection pooling and lifecycle management

Medium confidence

Manages MySQL connection pooling to reuse database connections across multiple tool invocations, reducing connection overhead and improving throughput. Implements connection lifecycle management including initialization, health checks, and graceful shutdown, ensuring that the MCP server maintains a stable connection pool to the MySQL database throughout its runtime.

Solves for

Improve performance of repeated database queries by reusing connectionsHandle connection failures gracefully without crashing the MCP serverManage resource cleanup when the MCP server shuts down

Best for

Applications with high-frequency database access from Claude/Cursor

Production deployments requiring stable, long-running MCP servers

Systems where connection overhead is a performance bottleneck

Requires

MySQL driver with connection pooling support (mysql2/promise)

Sufficient database user connections available (pool size + buffer)

Network stability to maintain persistent connections

Limitations

Connection pool size is fixed at server startup — cannot dynamically scale based on load

No built-in connection timeout configuration — relies on MySQL server timeout settings

Pool exhaustion (all connections in use) causes queuing without explicit backpressure to client

What makes it unique

Implements connection pooling at the MCP server layer, managing MySQL connections transparently so clients invoke tools without awareness of underlying connection reuse or pool state

vs alternatives

Provides built-in connection pooling unlike stateless MCP implementations, reducing per-query connection overhead for high-frequency database access patterns

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @benborla29/mcp-server-mysql, ranked by overlap. Discovered automatically through the match graph.

MCP Server32

mysql_mcp_server

A Model Context Protocol (MCP) server that enables secure interaction with MySQL databases

mcp protocol server implementation with stdio transportmcp-compliant database resource discovery and enumerationsql query execution with validation and error handling via mcp tools

3 shared capabilities

MCP Server23

mysql-mcp-tool

A MySQL MCP tool for Studio/Claude Desktop

mysql connection management via mcp protocolsql query execution with result streaming

2 shared capabilities

MCP Server24

user-postgresql-mcp

A PostgreSQL MCP server built with @modelcontextprotocol/sdk.

mcp protocol message handling and routingpostgresql query execution via mcp protocol

2 shared capabilities

MCP Server34

@supabase/mcp-server-supabase

MCP server for interacting with Supabase

postgresql table crud operations via mcp protocol

1 shared capability

MCP Server28

@iflow-mcp/garethcott_enhanced-postgres-mcp-server

Enhanced PostgreSQL MCP server with read and write capabilities. Based on @modelcontextprotocol/server-postgres by Anthropic.

postgresql query execution via mcp protocol

1 shared capability

MCP Server28

@coinbase/cds-mcp-server

Coinbase Design System - MCP Server

mcp-server-lifecycle-and-protocol-handling

1 shared capability

Best For

✓AI developers building Claude-powered database applications
✓Teams deploying LLM agents that need persistent data access
✓Cursor IDE users automating database-driven workflows
✓Applications requiring AI-driven data entry or record updates
✓Autonomous agents managing database state as part of workflow execution
✓Systems where LLM output directly affects persistent data
✓Developers integrating MySQL with Claude or Cursor IDE
✓Teams standardizing on MCP for tool integration across multiple services

Known Limitations

⚠No built-in query result pagination — large result sets may exceed MCP message size limits
⚠No transaction support — each query executes independently without ACID guarantees across multiple operations
⚠No query optimization hints — LLM-generated queries may be inefficient without developer guidance
⚠Single connection pool per server instance — concurrent requests from multiple clients may queue
⚠No rollback mechanism — failed mutations cannot be automatically reverted
⚠No audit logging built-in — mutations lack automatic tracking of who/when/what changed

Requirements

Node.js 16+MySQL 5.7+ or MariaDB 10.2+Active MySQL connection with network accessibilityMCP-compatible client (Claude, Cursor, or custom MCP host)MySQL user with INSERT, UPDATE, DELETE privileges on target tablesTable schema known to MCP server configurationClient-side validation or LLM prompt engineering to prevent invalid mutationsNode.js 16+ with npm or yarn

Input / Output

Accepts: SQL query strings, connection parameters (host, port, user, password, database), INSERT statements with column/value pairs, UPDATE statements with WHERE clauses, DELETE statements with WHERE clauses, PATCH operations with partial field updates, MCP protocol messages (JSON-RPC 2.0 format), tool invocation requests with parameters, parameter values (strings, numbers, dates, booleans), column names from pre-defined schema, WHERE clause operators (=, <, >, IN, LIKE, etc.), MCP server configuration (connection parameters), tool invocation requests from Cursor UI, connection configuration (host, port, user, password, database, pool size)

Produces: JSON-serialized result sets, query execution status, error messages with SQL context, affected row count, last insert ID, mutation success/failure status, MCP protocol responses, tool execution results, error responses with diagnostic context, safely executed query results, parameter binding errors if types mismatch, database query results displayed in Cursor, mutation confirmations, error messages with context, connection status, pool utilization metrics (if exposed)

UnfragileRank

Adoption15%(30% weight)

Quality14%(25% weight)

Ecosystem50%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit @benborla29/mcp-server-mysql→

Package Details

npm

Registry

2.0.8

Version

Weekly Downloads

About

MCP server for interacting with MySQL databases with write operations support

Alternatives to @benborla29/mcp-server-mysql

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @benborla29/mcp-server-mysql?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities6 decomposed

schema-based mysql query execution via mcp protocol

Medium confidence

Solves for

Best for

AI developers building Claude-powered database applications

Teams deploying LLM agents that need persistent data access

Cursor IDE users automating database-driven workflows

Requires

Node.js 16+

MySQL 5.7+ or MariaDB 10.2+

Active MySQL connection with network accessibility

Limitations

No built-in query result pagination — large result sets may exceed MCP message size limits

No transaction support — each query executes independently without ACID guarantees across multiple operations

No query optimization hints — LLM-generated queries may be inefficient without developer guidance

What makes it unique

vs alternatives

Provides native MCP integration for MySQL unlike REST API wrappers, enabling direct Claude/Cursor integration without additional HTTP abstraction layers

write-enabled database mutation operations

Medium confidence

Solves for

Best for

Applications requiring AI-driven data entry or record updates

Autonomous agents managing database state as part of workflow execution

Systems where LLM output directly affects persistent data

Requires

MySQL user with INSERT, UPDATE, DELETE privileges on target tables

Table schema known to MCP server configuration

Client-side validation or LLM prompt engineering to prevent invalid mutations

Limitations

No rollback mechanism — failed mutations cannot be automatically reverted

No audit logging built-in — mutations lack automatic tracking of who/when/what changed

No constraint validation before execution — database constraints may reject mutations after LLM constructs them

What makes it unique

vs alternatives

Allows safe write operations from LLM agents through parameterized queries and MCP protocol constraints, reducing injection risk compared to exposing raw SQL strings to Claude

mcp protocol server implementation for mysql

Medium confidence

Solves for

Best for

Developers integrating MySQL with Claude or Cursor IDE

Teams standardizing on MCP for tool integration across multiple services

Organizations using Smithery or mcp-get/mcp-put for MCP server management

Requires

Node.js 16+ with npm or yarn

MCP client that supports tool-calling (Claude 3.5+, Cursor 0.42+)

Network connectivity between MCP client and server

Limitations

MCP protocol overhead adds ~50-100ms per request compared to direct HTTP calls

Tool schema must be pre-defined — dynamic schema discovery not supported

No built-in authentication beyond MySQL credentials — relies on network isolation or client-side validation

What makes it unique

vs alternatives

Provides out-of-the-box MCP server for MySQL unlike building custom MCP implementations, reducing boilerplate and enabling immediate integration with Claude/Cursor

parameterized query construction with injection prevention

Medium confidence

Solves for

Best for

Production systems where LLM agents access databases with sensitive data

Applications requiring compliance with security standards (SOC 2, HIPAA)

Teams without dedicated security review for every LLM-generated query

Requires

MySQL driver with parameterized query support (mysql2/promise)

Tool schema that defines allowed columns and operations

LLM prompt engineering to ensure generated parameters match expected types

Limitations

Parameterized queries cannot use dynamic table/column names — schema must be pre-defined

Complex queries with conditional logic may require multiple tool invocations

Performance overhead of parameter binding is negligible but adds ~1-2ms per query

What makes it unique

Implements parameterized query binding at the MCP tool layer, ensuring all LLM-generated database operations are injection-safe by design rather than relying on downstream validation

vs alternatives

Prevents SQL injection at the protocol level unlike systems that expose raw SQL strings to LLMs, providing defense-in-depth for database security

cursor ide and smithery ecosystem integration

Medium confidence

Solves for

Best for

Cursor IDE users building database-driven applications

Teams using Smithery for centralized MCP server management

Developers who want plug-and-play database integration without DevOps

Requires

Cursor IDE 0.42+

npm or yarn for package installation

MySQL connection details (host, port, user, password, database)

Limitations

Cursor integration requires Cursor 0.42+ with MCP support

Smithery registry discovery depends on package being published and indexed

HTTP-style semantics (mcp-get, mcp-put, etc.) are semantic conventions, not true REST — actual transport is MCP protocol

What makes it unique

vs alternatives

Provides native Cursor integration unlike generic MCP servers, allowing developers to query databases directly from the editor without context-switching to external tools

connection pooling and lifecycle management

Medium confidence

Solves for

Improve performance of repeated database queries by reusing connectionsHandle connection failures gracefully without crashing the MCP serverManage resource cleanup when the MCP server shuts down

Best for

Applications with high-frequency database access from Claude/Cursor

Production deployments requiring stable, long-running MCP servers

Systems where connection overhead is a performance bottleneck

Requires

MySQL driver with connection pooling support (mysql2/promise)

Sufficient database user connections available (pool size + buffer)

Network stability to maintain persistent connections

Limitations

Connection pool size is fixed at server startup — cannot dynamically scale based on load

No built-in connection timeout configuration — relies on MySQL server timeout settings

Pool exhaustion (all connections in use) causes queuing without explicit backpressure to client

What makes it unique

Implements connection pooling at the MCP server layer, managing MySQL connections transparently so clients invoke tools without awareness of underlying connection reuse or pool state

vs alternatives

Provides built-in connection pooling unlike stateless MCP implementations, reducing per-query connection overhead for high-frequency database access patterns

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @benborla29/mcp-server-mysql

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@benborla29/mcp-server-mysql

Capabilities6 decomposed

schema-based mysql query execution via mcp protocol

write-enabled database mutation operations

mcp protocol server implementation for mysql

parameterized query construction with injection prevention

cursor ide and smithery ecosystem integration

connection pooling and lifecycle management

Related Artifactssharing capabilities

mysql_mcp_server

mysql-mcp-tool

user-postgresql-mcp

@supabase/mcp-server-supabase

@iflow-mcp/garethcott_enhanced-postgres-mcp-server

@coinbase/cds-mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @benborla29/mcp-server-mysql

Are you the builder of @benborla29/mcp-server-mysql?

Get the weekly brief

Data Sources

@benborla29/mcp-server-mysql

Capabilities6 decomposed

schema-based mysql query execution via mcp protocol

write-enabled database mutation operations

mcp protocol server implementation for mysql

parameterized query construction with injection prevention

cursor ide and smithery ecosystem integration

connection pooling and lifecycle management

Related Artifactssharing capabilities

mysql_mcp_server

mysql-mcp-tool

user-postgresql-mcp

@supabase/mcp-server-supabase

@iflow-mcp/garethcott_enhanced-postgres-mcp-server

@coinbase/cds-mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @benborla29/mcp-server-mysql

Are you the builder of @benborla29/mcp-server-mysql?

Get the weekly brief

Data Sources