{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-benborla29mcp-server-mysql","slug":"npm-benborla29mcp-server-mysql","name":"@benborla29/mcp-server-mysql","type":"mcp","url":"https://www.npmjs.com/package/@benborla29/mcp-server-mysql","page_url":"https://unfragile.ai/npm-benborla29mcp-server-mysql","categories":["mcp-servers"],"tags":["node","mcp","ai","cursor","mcp-server","modelcontextprotocol","smithery","mcp-get","mcp-put","mcp-post","mcp-delete","mcp-patch","mcp-options","mcp-head"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-benborla29mcp-server-mysql__cap_0","uri":"capability://tool.use.integration.schema.based.mysql.query.execution.via.mcp.protocol","name":"schema-based mysql query execution via mcp protocol","description":"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.","intents":["Enable Claude to query a MySQL database and retrieve structured results for analysis or decision-making","Allow AI agents to perform CRUD operations on database records without direct SQL injection risk","Integrate 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"],"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"],"requires":["Node.js 16+","MySQL 5.7+ or MariaDB 10.2+","Active MySQL connection with network accessibility","MCP-compatible client (Claude, Cursor, or custom MCP host)"],"input_types":["SQL query strings","connection parameters (host, port, user, password, database)"],"output_types":["JSON-serialized result sets","query execution status","error messages with SQL context"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-benborla29mcp-server-mysql__cap_1","uri":"capability://tool.use.integration.write.enabled.database.mutation.operations","name":"write-enabled database mutation operations","description":"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).","intents":["Allow Claude to create new database records based on conversation context or analysis results","Enable AI agents to update existing records with computed values or corrections","Support 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"],"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","No transaction grouping — multiple related mutations execute independently"],"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"],"input_types":["INSERT statements with column/value pairs","UPDATE statements with WHERE clauses","DELETE statements with WHERE clauses","PATCH operations with partial field updates"],"output_types":["affected row count","last insert ID","mutation success/failure status"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-benborla29mcp-server-mysql__cap_2","uri":"capability://tool.use.integration.mcp.protocol.server.implementation.for.mysql","name":"mcp protocol server implementation for mysql","description":"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.","intents":["Enable seamless integration with Claude and Cursor without custom client code","Provide standardized tool discovery so clients know what database operations are available","Handle 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"],"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","Single server instance per database — no built-in clustering or failover"],"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"],"input_types":["MCP protocol messages (JSON-RPC 2.0 format)","tool invocation requests with parameters"],"output_types":["MCP protocol responses","tool execution results","error responses with diagnostic context"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-benborla29mcp-server-mysql__cap_3","uri":"capability://safety.moderation.parameterized.query.construction.with.injection.prevention","name":"parameterized query construction with injection prevention","description":"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.","intents":["Safely execute LLM-generated database queries without risk of injection attacks","Allow Claude to construct WHERE clauses and filter conditions without exposing raw SQL","Prevent 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"],"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"],"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"],"input_types":["parameter values (strings, numbers, dates, booleans)","column names from pre-defined schema","WHERE clause operators (=, <, >, IN, LIKE, etc.)"],"output_types":["safely executed query results","parameter binding errors if types mismatch"],"categories":["safety-moderation","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-benborla29mcp-server-mysql__cap_4","uri":"capability://tool.use.integration.cursor.ide.and.smithery.ecosystem.integration","name":"cursor ide and smithery ecosystem integration","description":"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.","intents":["Install and configure MySQL database access in Cursor IDE with minimal setup","Discover and use MySQL tools through Smithery registry without manual server deployment","Access 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"],"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"],"requires":["Cursor IDE 0.42+","npm or yarn for package installation","MySQL connection details (host, port, user, password, database)","Smithery account for registry access (optional, for discovery)"],"input_types":["MCP server configuration (connection parameters)","tool invocation requests from Cursor UI"],"output_types":["database query results displayed in Cursor","mutation confirmations","error messages with context"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-benborla29mcp-server-mysql__cap_5","uri":"capability://automation.workflow.connection.pooling.and.lifecycle.management","name":"connection pooling and lifecycle management","description":"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.","intents":["Improve performance of repeated database queries by reusing connections","Handle connection failures gracefully without crashing the MCP server","Manage 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"],"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","No metrics or monitoring of pool utilization — requires external APM tools"],"requires":["MySQL driver with connection pooling support (mysql2/promise)","Sufficient database user connections available (pool size + buffer)","Network stability to maintain persistent connections"],"input_types":["connection configuration (host, port, user, password, database, pool size)"],"output_types":["connection status","pool utilization metrics (if exposed)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+","MySQL 5.7+ or MariaDB 10.2+","Active MySQL connection with network accessibility","MCP-compatible client (Claude, Cursor, or custom MCP host)","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","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"],"failure_modes":["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","No constraint validation before execution — database constraints may reject mutations after LLM constructs them","No transaction grouping — multiple related mutations execute independently","MCP protocol overhead adds ~50-100ms per request compared to direct HTTP calls","Tool schema must be pre-defined — dynamic schema discovery not supported","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.5000000000000001,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:35.733Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-benborla29mcp-server-mysql","compare_url":"https://unfragile.ai/compare?artifact=npm-benborla29mcp-server-mysql"}},"signature":"zt7c1h6dd3coRuxviqugh9D62c9atF9PPVaXFMZu63vmzU9mC/HKQBkegAkA2UtXHTJpAlxLD5yiyK7DnJXHDw==","signedAt":"2026-06-20T13:40:30.421Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-benborla29mcp-server-mysql","artifact":"https://unfragile.ai/npm-benborla29mcp-server-mysql","verify":"https://unfragile.ai/api/v1/verify?slug=npm-benborla29mcp-server-mysql","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}