Skip to main content
Glama
enesjakozh
elber-code

Database Tools for Claude AI

by elber-code
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Claude AI를 위한 데이터베이스 도구

대장간 배지

이는 Claude AI가 MySQL 데이터베이스와 직접 상호 작용할 수 있게 해주는 MCP(Model Context Protocol) 서버입니다.

특징

  • Claude를 통해 MySQL 데이터베이스 쿼리

  • 유효한 SQL 쿼리를 실행합니다.

  • 크기와 구조를 포함한 테이블에 대한 정보를 얻으세요

  • Claude에서 쉽게 읽을 수 있도록 형식화된 결과

Related MCP server: MariaDB MCP Server

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 데이터베이스 도구를 자동으로 설치하려면:

지엑스피1

이 도구를 설치하고 사용하려면 다음 단계를 따르세요.

  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에 있는 모든 데이터베이스를 보여주세요" 또는 "users 테이블의 크기는 얼마인가요?"와 같이 질문하면 됩니다.

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