Which integrations are available for this server?

Provides tools for exploring and querying MySQL databases, including listing tables, describing table structures, and executing arbitrary SQL statements.

How do I use keevor-mysql-mcp-server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@keevor-mysql-mcp-server list all tables in the database" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

keevor-mysql-mcp-server

by KeeVor

Overview Schema Related Servers Score Discussions

Python

Local

keevor-mysql-mcp-server

一个 MCP (Model Context Protocol) 服务器，用于连接 MySQL 数据库并执行常用操作。

功能

list_tables - 查询数据库中的所有表
describe_table - 查询指定表的结构
execute_sql - 执行 SQL 语句

Related MCP server: MySQL Custom MCP Server

使用方法

1. 安装 uv

# Windows (PowerShell)
irm https://astral.sh/uv/install.ps1 | iex

# macOS / Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

2. 配置 MCP

在 AI 工具的 MCP 配置文件中添加：

{
  "mcpServers": {
    "keevor-mysql-mcp-server": {
      "command": "uvx",
      "args": ["keevor-mysql-mcp-server"],
      "env": {
        "DB_HOST": "localhost",
        "DB_PORT": "3306",
        "DB_USER": "root",
        "DB_PASSWORD": "your_password",
        "DB_NAME": "your_database"
      }
    }
  }
}

3. 开始使用

配置完成后，AI 助手即可使用以下工具：

查询所有表：调用 list_tables
查询表结构：调用 describe_table，传入表名
执行 SQL：调用 execute_sql，传入 SQL 语句

环境变量

变量	说明	默认值
DB_HOST	数据库主机地址	localhost
DB_PORT	数据库端口	3306
DB_USER	数据库用户名	root
DB_PASSWORD	数据库密码	-
DB_NAME	数据库名称	-

License

MIT

Available Tools

3 tools

describe_tableA

查询指定表的详细结构，包含字段注释、索引、外键等信息

Args:
    table_name: 要查询结构的表名

ParametersJSON Schema

Name	Required	Description	Default
`table_name`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

Despite no annotations, the description discloses that the output includes field comments, indexes, and foreign keys, adding behavioral context beyond basic table schema. It implies a read-only operation.

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 very concise: two lines for purpose and one line for parameter explanation, with no superfluous text. Front-loaded with the main action.

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

Completeness4/5

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

Given the simple single-parameter input and existing output schema, the description adds value by specifying that details include comments, indexes, and foreign keys. Could mention if it is safe/read-only but not essential.

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

Parameters4/5

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

Schema description coverage is 0% but the description compensates with an in-line 'Args' explanation for table_name, clearly stating it is the table name to query. Adequate for a single parameter.

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

Purpose5/5

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

The description clearly states the tool queries detailed table structure including field comments, indexes, and foreign keys. It distinguishes from siblings: list_tables lists tables, execute_sql runs arbitrary SQL, while describe_table provides schema details for a specific table.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance. Usage is implied from context: use when needing table structure details, but no alternatives or exclusions are mentioned.

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

execute_sqlC

执行SQL语句

Args:
    sql: 要执行的SQL语句

ParametersJSON Schema

Name	Required	Description	Default
`sql`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.3/5.0

Behavior1/5

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

No annotations provided. The description fails to disclose critical behavioral traits such as whether SQL statements are read-only or can modify data, what happens on error, or whether results are returned. For a tool executing arbitrary SQL, this is a significant omission.

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

Conciseness2/5

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

The description is very brief, but it sacrifices necessary information for brevity. It front-loads the purpose but lacks structure for parameter details or usage notes. It is under-specified rather than concise.

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

Completeness1/5

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

Despite having only one parameter and an output schema, the description fails to provide essential context about SQL execution behavior, return format, or safety considerations. It is incomplete for an operation with significant potential impact.

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

Parameters1/5

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

Schema description coverage is 0%, and the description merely restates the parameter name 'sql: 要执行的SQL语句' without adding any semantics about syntax, limitations, or allowed statements. The agent gains no additional meaning beyond the raw schema.

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

Purpose5/5

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

The description 'Execute SQL statement' clearly states the tool's verb and resource. It distinguishes from sibling tools 'describe_table' and 'list_tables' which are for schema inspection rather than execution.

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 on when to use this tool versus alternatives, nor any mention of prerequisites or when not to use it. The description is minimal and leaves usage decisions entirely to the agent.

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

list_tablesA

查询数据库中的所有表，包含表注释、引擎、行数等信息

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, but description explicitly states it returns table comments, engine, row count, etc. Safe read operation implicitly clear. Lacks mention of any pagination or limits, but acceptable for this simple tool.

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?

Single sentence front-loads action and key details. No wasted words.

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

Completeness5/5

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

With no parameters and output schema present, description sufficiently explains what is returned (table metadata). No missing aspects for this straightforward tool.

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

Parameters4/5

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

No parameters exist; schema coverage 100%. Baseline is 4 per rules. Description adds no redundant info.

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

Purpose5/5

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

Description clearly states verb 'list' and resource 'all tables in database' with details. Distinguishes from siblings: describe_table focuses on single table, execute_sql runs arbitrary SQL.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance. Usage is implied as 'when you need an overview of all tables', but no comparison with siblings.

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.

3 tool updatesv1.0.0Jul 4, 2026
- First observeddescribe_table
- First observedexecute_sql
- First observedlist_tables

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: list_tables retrieves metadata about all tables, describe_table zooms into a single table's structure, and execute_sql runs arbitrary queries. No overlaps.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (list_tables, describe_table, execute_sql), making them predictable and easy to understand.

Tool Count4/5

With only 3 tools, the server covers the minimum needed for MySQL interaction. While a bit sparse, the tools are well-chosen and each one serves a necessary role, making the count appropriate for a focused utility server.

Completeness3/5

The tool set covers basic discovery (list, describe) and execution (execute_sql), but lacks specialized tools for common operations like SELECT, INSERT, or database management. The generic execute_sql fills many gaps, so the surface is functional but not comprehensive.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

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

Related MCP Connectors

smithery-ai-cookbook-python-quickstart
ai.smithery
A simple MCP server built with FastMCP and python
Developer Tools
213
mcp-aichatOAuth
io.github.AceDataCloud
MCP server for AI dialogue using various LLM models via AceDataCloud
AI & Machine Learning
2
Second server!
com.fenetresurciel.verylongmcp
A non functional MCP server (yet)
Developer Tools
2
thoughtsOAuth
ai.thoughtbox.api
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Cloud Storage Finance
2

Related MCP Servers

MySQL Database Access
Databases RAG Systems
dpflucas
A
license
A
quality
D
maintenance
An MCP server that provides read-only access to MySQL databases.
Updated a year ago (2025-04-22 10:22 UTC)
4
454
72
MIT
MySQL Custom MCP Server
tonguyenducmanh
F
license
Not graded
quality
Not graded
maintenance
An MCP server that enables interaction with MySQL databases through the Model Context Protocol, allowing execution of SQL queries and database table listing operations from Cline AI.
Updated a year ago (2025-07-13 00:38 UTC)
-
mysql-mcp-server
Databases Developer Tools
wenit
A
license
Not graded
quality
D
maintenance
基于Node.js的MySQL MCP服务器，支持通过MCP协议安全操作MySQL数据库。
Updated 6 months ago (2026-03-12 12:18 UTC)
45
3
MIT
OpenCode MySQL Connector
Databases Developer Tools
siimleetberg
F
license
C
quality
C
maintenance
A MySQL MCP server providing tools to query and explore MySQL databases via stdio transport.
Updated 2 months ago (2026-07-17 07:57 UTC)
7
-

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/KeeVor/keevor-mysql-mcp-server'

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