Skip to main content
Glama
enesjakozh
elber-code

Database Tools for Claude AI

by elber-code
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Database Tools for Claude AI

This is an MCP (Model Context Protocol) server that allows Claude AI to interact directly with MySQL databases.

Features

  • Query MySQL databases through Claude

  • Execute any valid SQL query

  • Get information about tables, including size and structure

  • Formatted results for easy reading in Claude

Related MCP server: MariaDB MCP Server

Installation

Installing via Smithery

To install Database Tools for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @elber-code/database-tools --client claude

To install and use this tool, follow these steps:

  1. Clone or download the repository

    git clone [repository-url]

    or download and extract the ZIP file.

  2. Install dependencies Navigate to the project directory and run:

    npm install

Configuration

For Claude to use this tool, you need to add the configuration to your claude_desktop_config.json file, which is typically located at:

C:\Users\YOUR_USER\AppData\Roaming\Claude\claude_desktop_config.json

With the following structure:

{
  "mcpServers": {
    // Other existing configurations...
    "database-tools": {
      "command": "node",
      "args": [
        "C:\\path\\to\\index.js"
      ]
    }
  }
}

Usage

Once configured, you can interact with your MySQL databases from Claude with commands like:

  1. List all databases
    "Execute query in MySQL to show me the databases."

  2. View tables in a database
    "Execute query in MySQL to show me the table name_table."

  3. Query the size of a table
    "Execute query in MySQL to show me the size of the table name_table."

  4. Execute custom queries
    "Execute query in MySQL: 'The description of what you want your query to do.'"

Security

This tool runs with the permissions configured in the mysql.js file. Make sure the credentials provided have only the necessary permissions for the operations you want to allow.

Troubleshooting

If you have connection problems, check:

  • That MySQL is running

  • That the credentials in mysql.js are correct

  • That the path in the Claude configuration file is correct

Implementation

To query databases, simply ask Claude something like: "Show me all databases in my MySQL" or "What is the size of the users table?"

Available Tools

1 tool
mysqlC

Execute a query in MySQL

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesSQL query to execute

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions execution but doesn't disclose behavioral traits like whether it's read-only or destructive, authentication needs, error handling, or rate limits, leaving significant gaps.

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 no wasted words, making it front-loaded and appropriately sized for its purpose.

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 executing SQL queries, no annotations, and no output schema, the description is incomplete. It lacks details on return values, error cases, or operational constraints, which are crucial for effective use.

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 already documents the 'query' parameter. The description adds no additional meaning beyond what the schema provides, such as query syntax or examples, meeting the baseline for high coverage.

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 action ('Execute') and resource ('a query in MySQL'), making the purpose understandable. However, it doesn't distinguish from siblings since there are none, so it's not fully specific to a unique context.

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, such as for read vs. write operations or specific query types. The description only states what it does without context or exclusions.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedmysql
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as executing MySQL queries, leaving no ambiguity for an agent to misselect among alternatives.

Naming Consistency5/5

Since there is only one tool named 'mysql', it inherently follows a consistent pattern with itself. There are no other tools to compare against, so no inconsistencies in naming conventions can arise.

Tool Count2/5

A single tool for a server named 'Database Tools for Claude AI' is too few for the apparent scope, which suggests broader database operations. This minimal set limits functionality and does not provide a comprehensive tool surface for database management tasks.

Completeness2/5

The tool surface is severely incomplete for a database tools server, as it only offers query execution without supporting essential operations like connection management, schema inspection, data manipulation beyond queries, or CRUD lifecycle coverage. This will likely cause agent failures in handling typical database workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MariaDB MCP Server

    abel9851
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server implementation that enables Claude to execute read-only queries against MariaDB databases and explore database schemas through natural language.
    20
    MIT

  • mcp-sequel

    eukos
    A
    license
    A
    quality
    B
    maintenance
    MCP server for Claude that connects to MySQL, MariaDB, and SQLite databases. Query your databases using natural language.
    3
    MIT

  • mcp-mysql-explorer

    xsg22
    A
    license
    Not graded
    quality
    C
    maintenance
    MCP server that connects AI agents to MySQL databases for schema exploration, data querying, and SQL execution via natural language.
    2
    MIT

Appeared in Searches

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/elber-code/database-tools'

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