Skip to main content
Glama
enesjakozh
elber-code

Database Tools for Claude AI

by elber-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Claude AI 的数据库工具

铁匠徽章

这是一个 MCP（模型上下文协议）服务器，允许 Claude AI 直接与 MySQL 数据库交互。

特征

  • 通过 Claude 查询 MySQL 数据库

  • 执行任何有效的 SQL 查询

  • 获取有关表的信息，包括大小和结构

  • 格式化结果以便于在 Claude 中阅读

Related MCP server: MariaDB MCP Server

安装

通过 Smithery 安装

要通过Smithery自动安装 Claude Desktop 的数据库工具：

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

要安装和使用此工具，请按照以下步骤操作：

  1. 克隆或下载存储库

    git clone [repository-url]

    或下载并解压 ZIP 文件。

  2. 安装依赖项导航到项目目录并运行：

    npm install

配置

为了让 Claude 使用此工具，您需要将配置添加到您的claude_desktop_config.json文件中，该文件通常位于：

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

具有以下结构：

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

用法

配置完成后，您可以使用以下命令从 Claude 与 MySQL 数据库进行交互：

  1. 列出所有数据库
    “在 MySQL 中执行查询以显示数据库。”

  2. 查看数据库中的表
    “在 MySQL 中执行查询以显示表name_table 。”

  3. 查询表的大小
    “在 MySQL 中执行查询以显示表name_table的大小。”

  4. 执行自定义查询
    “在 MySQL 中执行查询：‘您希望查询执行的操作的描述。’”

安全

此工具使用mysql.js文件中配置的权限运行。请确保提供的凭据仅具有您要允许的操作所需的必要权限。

故障排除

如果您遇到连接问题，请检查：

  • MySQL 正在运行

  • mysql.js中的凭据正确

  • Claude配置文件中的路径是正确的

执行

要查询数据库，只需向 Claude 询问类似“显示我的 MySQL 中的所有数据库”或“用户表的大小是多少？”

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.

  1. 1 tool updatev1.0.0
    • First observedmysql
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

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

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
    C
    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
    D
    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