Skip to main content
Glama
Darkstar326

MCP MySQL Server

by Darkstar326

mysql_connect

Establish a connection to MySQL databases by providing host, user, and password parameters. Use this tool to initiate secure database interactions for query execution and management operations.

Instructions

Connect to a MySQL database with provided connection parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesMySQL server hostname or IP address
portNoMySQL server port (default: 3306)
userYesDatabase username
passwordYesDatabase password
databaseNoDatabase name (optional)
sslNoUse SSL connection (default: false)

Implementation Reference

  • The main handler function for the mysql_connect tool. It validates input using ConfigSchema, closes any existing connection pool, creates a new MySQL pool using createConnection, tests it, and returns a success message.
    private async handleConnect(args: any) {
      try {
        const config = ConfigSchema.parse(args);
        this.config = config;
        
        // Close existing connection if any
        if (this.pool) {
          await this.pool.end();
        }
    
        this.pool = await this.createConnection(config);
        
        return {
          content: [
            {
              type: "text",
              text: `Successfully connected to MySQL server at ${config.host}:${config.port}${config.database ? ` (database: ${config.database})` : ""}`,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Connection failed: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Zod schema used to validate the input parameters for mysql_connect tool.
    const ConfigSchema = z.object({
      host: z.string(),
      port: z.number().optional().default(3306),
      user: z.string(),
      password: z.string(),
      database: z.string().optional(),
      ssl: z.boolean().optional().default(false),
      connectionLimit: z.number().optional().default(10),
    });
  • src/index.ts:101-135 (registration)
    Registers the mysql_connect tool in the ListTools response, providing name, description, and JSON inputSchema matching the ConfigSchema.
      name: "mysql_connect",
      description: "Connect to a MySQL database with provided connection parameters",
      inputSchema: {
        type: "object",
        properties: {
          host: {
            type: "string",
            description: "MySQL server hostname or IP address",
          },
          port: {
            type: "number",
            description: "MySQL server port (default: 3306)",
            default: 3306,
          },
          user: {
            type: "string",
            description: "Database username",
          },
          password: {
            type: "string",
            description: "Database password",
          },
          database: {
            type: "string",
            description: "Database name (optional)",
          },
          ssl: {
            type: "boolean",
            description: "Use SSL connection (default: false)",
            default: false,
          },
        },
        required: ["host", "user", "password"],
      },
    },
  • Helper method called by handleConnect to create the mysql2/promise Pool with config options, optionally enable SSL, and test the connection with ping.
    private async createConnection(config: Config): Promise<mysql.Pool> {
      try {
        const poolConfig: mysql.PoolOptions = {
          host: config.host,
          port: config.port,
          user: config.user,
          password: config.password,
          database: config.database,
          connectionLimit: config.connectionLimit,
          multipleStatements: false,
        };
    
        if (config.ssl) {
          poolConfig.ssl = {};
        }
    
        this.pool = mysql.createPool(poolConfig);
    
        // Test the connection
        const connection = await this.pool.getConnection();
        await connection.ping();
        connection.release();
    
        return this.pool;
      } catch (error) {
        throw new Error(`Failed to connect to MySQL: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action ('connect') but doesn't disclose what happens on success/failure, whether it establishes a persistent session, authentication requirements beyond parameters, rate limits, or side effects. This is inadequate for a connection tool that likely manages state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a straightforward connection tool, earning its place by stating the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a database connection tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., connection handle, success status), error handling, or how the connection integrates with sibling tools, leaving significant gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond implying these are 'connection parameters,' which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('connect') and resource ('MySQL database'), making the purpose evident. It distinguishes this as an initialization/connection tool rather than a query or metadata tool, though it doesn't explicitly differentiate from siblings like 'mysql_disconnect' beyond the obvious opposite action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., must be called before other MySQL tools), when not to use it (e.g., if already connected), or how it relates to sibling tools like 'mysql_disconnect' for cleanup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Darkstar326/mcp-mysql'

If you have feedback or need assistance with the MCP directory API, please join our Discord server