Mysql MCP 26e5c8ac

MCP数据服务

提供方 berthojoris · 包名 @berthojoris/mcp-mysql-server

数据服务 stdio · 本地进程 无需鉴权 社区 / 第三方 ClaudeCursorWindsurfCline
查看接入方式

一个用于MySQL数据库与AI代理集成的生产就绪模型上下文协议(MCP)服务器。

一句话选型结论

按资料字段整理

Mysql MCP 26e5c8ac 属于数据服务类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude、Cursor、Windsurf 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 4 仓库热度,无公开仓库时显示未标注
工具数 78 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量78暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

数据库集成TypeScript本地部署AI代理MySQL模型上下文协议生产就绪

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx @berthojoris/mcp-mysql-server mysql://user:pass@localhost:3306/mydb "list,read,utility"

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 78 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 78 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Windsurf,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mysql MCP 26e5c8ac当前 78 stdio · 本地进程 本地部署 有 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方berthojoris上游标注的维护方 berthojoris
分类数据服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@berthojoris/mcp-mysql-server · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

19.6 KB
来自项目仓库与上游目录的原文,未做删改

MySQL MCP Server

A production-ready Model Context Protocol (MCP) server for MySQL database integration with AI agents

Last Updated: 2026-10-26 16:39:47


TL;DR - Quick Setup

Run directly with npx:```bash
npx @berthojoris/mcp-mysql-server mysql://user:pass@localhost:3306/mydb "list,read,utility"


Add to your AI agent config (`.mcp.json`, `.cursor/mcp.json`, etc.):```json
{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "type": "stdio",
      "args": [
        "-y",
        "@berthojoris/mcp-mysql-server",
        "mysql://user:pass@localhost:3306/mydb",
        "list,read,utility"
      ]
    }
  }
}

For dual-layer and environment-variable configuration, see DOCUMENTATIONS.md → Configuration. To connect remote clients such as ChatGPT over HTTP, see Remote Access.


Installation

Option 1: Quick Start with npx (Recommended)

No installation required - run directly:```bash
npx @berthojoris/mcp-mysql-server mysql://user:pass@localhost:3306/db "list,read,utility"


### Option 2: Global Installation```bash
npm install -g @berthojoris/mcp-mysql-server
mcp-mysql mysql://user:pass@localhost:3306/db "list,read,utility"

> Credentials with special characters: if your username or password contains characters that have a special meaning in URLs (@, :, /, ?, #, %, &, etc.), URL-encode them before putting them in the connection string. For example, the password p@ss:w0rd becomes p%40ss%3Aw0rd, giving mysql://user:p%40ss%3Aw0rd@host:3306/db. The server decodes both the username and password before connecting.


Quick Start

1. Set Up Environment (Optional)

Create .env file for local development:```env
DB_HOST=localhost
DB_PORT=3306
DB_USER=root
DB_PASSWORD=yourpassword
DB_NAME=yourdatabase
MCP_CONFIG=list,read,utility


### 2. Build Project (If Cloned Locally)```bash
npm install
npm run build

3. Configure Your AI Agent

See AI Agent Configuration section below.

4. Restart Your AI Agent

Completely restart your AI agent application to load the MCP server.

5. Test It!

Try asking your AI:

> "What databases are available?"
> "Show me all tables in my database"
> "What's the structure of the users table?"
> "Show me the first 5 records from users"


AI Agent Configuration

Standard JSON Configuration

Most AI agents use a similar JSON configuration format (the file location varies by tool).

The examples below use the default stdio transport, where the AI agent starts the server itself. Remote clients connect over HTTP instead; see Remote Access.

Universal Configuration Template:

Option 1: Single-Layer (Permissions Only) - Simple Setup```json
{
"mcpServers": {
"mysql": {
"command": "npx",
"type": "stdio",
"args": [
"-y",
"@berthojoris/mcp-mysql-server",
"mysql://user:password@localhost:3306/database",
"list,read,utility,create,update,ddl"
]
}
}
}


**Option 2: Dual-Layer (Permissions + Categories) - Recommended for Fine Control**```json
{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "type": "stdio",
      "args": [
        "-y",
        "@berthojoris/mcp-mysql-server",
        "mysql://user:password@localhost:3306/database_name_here",
        "list,read,utility,create,update,ddl,transaction",
        "database_discovery,crud_operations,custom_queries,schema_management,index_management,constraint_management,table_maintenance,query_optimization,analysis,seed_operations"
      ]
    }
  }
}

> 💡 Tip: The dual-layer approach provides granular control. The 4th argument (permissions) controls broad access levels, while the 5th argument (categories) fine-tunes which specific tools are available.

Environment Variables Configuration

Alternative approach using environment variables instead of connection string:

Option 1: Permissions Only (Simple)```json
{
"mcpServers": {
"mysql": {
"command": "npx",
"type": "stdio",
"args": ["-y", "@berthojoris/mcp-mysql-server"],
"env": {
"DB_HOST": "localhost",
"DB_PORT": "3306",
"DB_USER": "root",
"DB_PASSWORD": "your_password",
"DB_NAME": "your_database",
"MCP_PERMISSIONS": "list,read,utility,create,update,delete"
}
}
}
}


**Option 2: Permissions + Categories (Recommended)**```json
{
  "mcpServers": {
    "mysql": {
      "command": "npx",
      "type": "stdio",
      "args": ["-y", "@berthojoris/mcp-mysql-server"],
      "env": {
        "DB_HOST": "localhost",
        "DB_PORT": "3306",
        "DB_USER": "root",
        "DB_PASSWORD": "your_password",
        "DB_NAME": "your_database",
        "MCP_PERMISSIONS": "list,read,utility,create,update,delete",
        "MCP_CATEGORIES": "database_discovery,custom_queries,analysis"
      }
    }
  }
}

More configuration details are in DOCUMENTATIONS.md → Configuration.


Cursor Compatibility Bridge

If a Cursor MCP wrapper can call tools but cannot send arguments, use the no-argument cursor_execute_request bridge. Create .cursor/mysql-mcp-request.json in the workspace, then call cursor_execute_request:```json
{
"tool": "execute_ddl",
"arguments": {
"query": "DROP TABLE IF EXISTS spark_processes;"
}
}


For direct SQL, the bridge can infer the right SQL tool:```json
{
  "query": "DROP TABLE IF EXISTS spark_processes;",
  "mode": "auto"
}

Set MYSQL_MCP_CURSOR_REQUEST_FILE to override the request file path.


AI Agent Tool Discovery

For Codex, Claude Code CLI, Cursor, Droid CLI, and other MCP agents, call list_all_tools first. It returns the live runtime catalog, enabled/disabled status, active permission/category profile, and recommended workflows for schema exploration, safe SELECT queries, CSV exports, transactions, and data changes.

Use export_table_to_csv for table-based exports and export_query_to_csv for SELECT query exports.


Remote Access (ChatGPT & other remote MCP clients)

stdio stays the default. For remote clients such as ChatGPT connectors / developer mode, you can enable the Streamable HTTP transport with a flag or an environment variable, the same way you set permissions. Remove the flag, or set MCP_TRANSPORT=stdio, to turn it off again.```bash

Read-only MySQL account + bearer token, bound to localhost

export MCP_HTTP_AUTH=token
export MCP_HTTP_AUTH_TOKENS=$(openssl rand -hex 32) # give this token to your clients
npx -y @berthojoris/mcp-mysql-server mysql://mcp_reader:pass@localhost:3306/app "list,read,utility" --transport=http --port=3000


- **Endpoint**: `http://127.0.0.1:3000/mcp`, plus `GET /health`. Publish it over HTTPS with a reverse proxy or tunnel, and set `MCP_HTTP_PUBLIC_URL`.
- **Auth**: `MCP_HTTP_AUTH=token` (bearer tokens) or `oauth` (OAuth 2.1 JWT validation against your authorization server, with RFC 9728 metadata, as needed by ChatGPT). `none` only works on loopback.
- **Isolation**: `Host`/`Origin` checks (DNS-rebinding protection). Each session is bound to its identity, and each transaction to its session. A session's open transactions are rolled back when it closes or expires.
- **Startup checks**: invalid or unsafe HTTP settings stop the server with an error. `MCP_HTTP_*` settings are ignored over stdio.
- **Tool annotations**: every tool reports `readOnlyHint` and `destructiveHint`.

#### Protection defaults

Protections are **on by default in HTTP mode and off by default over stdio**, so existing stdio setups behave as before. Every value can be overridden with an environment variable on either transport.

| Variable | stdio default | HTTP default | What it does |
|----------|---------------|--------------|--------------|
| `MCP_QUERY_TIMEOUT_MS` | `0` (off) | `30000` | Cancels longer statements on the MySQL server with `KILL QUERY`. A timed-out statement inside a transaction rolls that transaction back |
| `MCP_RATE_LIMIT_PER_MINUTE` | `0` (off) | `60` | Tool calls per client per minute. The client is the auth identity, or the IP when there is none |
| `MCP_MAX_RESULT_BYTES` | `0` (off) | `524288` | Maximum result size. Row arrays are truncated to fit; other oversized results return an error |
| `MCP_AUDIT_LOG` | `off` | `stderr` | `off`, `stderr`, or a file path. One JSON line per tool call, authentication failure, and session open/close. SQL text is logged; other argument values are not |
| `MCP_REQUIRE_READONLY_DB_USER` | `false` | `false` | `true` makes startup fail if the MySQL user can write. In HTTP mode a warning is always logged |

#### HTTP settings

Variable / flag · Default · What it does
`MCP_TRANSPORT` / `--transport=stdio\ · http`, `--http` · `stdio` · Turns the HTTP transport on or off
`MCP_HTTP_HOST` / `--host=` · `127.0.0.1` · Bind address
`MCP_HTTP_PORT` / `--port=` · `3000` · Port
`MCP_HTTP_PATH` · `/mcp` · Endpoint path
`MCP_HTTP_PUBLIC_URL` · – · Public HTTPS base URL. Required for `oauth`
`MCP_HTTP_AUTH` · `none` · `none` (loopback only), `token`, or `oauth`
`MCP_HTTP_AUTH_TOKENS` · – · Comma-separated bearer tokens, at least 32 characters each
`MCP_OAUTH_ISSUER` / `MCP_OAUTH_AUDIENCE` / `MCP_OAUTH_JWKS_URI` / `MCP_OAUTH_REQUIRED_SCOPES` · – / resource URL / discovered / – · OAuth 2.1 token validation
`MCP_HTTP_ALLOWED_HOSTS` · loopback names when bound to loopback · `Host` allowlist. Off (with a warning) when bound to a non-loopback address and neither this nor `MCP_HTTP_PUBLIC_URL` is set
`MCP_HTTP_ALLOWED_ORIGINS` · loopback origins when bound to loopback · Browser `Origin` allowlist. Requests without `Origin` are always allowed
`MCP_HTTP_TRUST_PROXY` · `false` · Take the client IP from `X-Forwarded-For`
`MCP_HTTP_ALLOW_UNAUTHENTICATED` · `false` · Allow `none` outside loopback (not recommended)
`MCP_HTTP_MAX_SESSIONS` · `100` · Maximum concurrent sessions (`0` = no limit)
`MCP_HTTP_SESSION_IDLE_TIMEOUT_MS` · `1800000` · Idle sessions close after this time, and their transactions roll back (`0` = never)
`MCP_HTTP_MAX_BODY_BYTES` · `1048576` · Maximum request body size (`0` = no limit)

In HTTP mode the server runs as a standalone service, so put the settings in `.env` (or your process manager) instead of an MCP client's `command` config:```env
DB_HOST=localhost
DB_USER=mcp_reader
DB_PASSWORD=pass
DB_NAME=app
MCP_PERMISSIONS=list,read,utility
MCP_TRANSPORT=http
MCP_HTTP_PORT=3000
MCP_HTTP_AUTH=token
MCP_HTTP_AUTH_TOKENS=<64-hex-token>
MCP_QUERY_TIMEOUT_MS=15000
MCP_AUDIT_LOG=logs/mcp-audit.log

From the directory that holds .env, start it with node dist/mcp-server.js (from a clone) or the npx command above (a connection string argument overrides the DB_* values). Then point clients that support remote MCP servers at the URL. For example, in Claude Code's .mcp.json:```json
{
"mcpServers": {
"mysql-remote": {
"type": "http",
"url": "http://127.0.0.1:3000/mcp",
"headers": { "Authorization": "Bearer <64-hex-token>" }
}
}
}


Full details (OAuth setup, sessions, read-only user SQL) are in **DOCUMENTATIONS.md → Remote Access**.

---

## Permission System

Control database access with a **dual-layer filtering system** that provides both broad and fine-grained control:

- **Layer 1 (Permissions)**: Broad operation-level control using legacy categories
- **Layer 2 (Categories)**: Optional fine-grained tool-level filtering using documentation categories

**Filtering Logic**: `Tool enabled = (Has Permission) AND (Has Category OR No categories specified)`

### Permissions

| Permission | Operations | Use Case |
|------------|------------|----------|
| `list` | List databases, tables, schemas | Database exploration |
| `read` | SELECT queries, read data | Analytics, reporting |
| `create` | INSERT new records | Data entry |
| `update` | UPDATE existing records | Data maintenance |
| `delete` | DELETE records | Data cleanup |
| `execute` | Execute custom INSERT/UPDATE SQL (DELETE requires `delete` permission too) | Complex write operations |
| `ddl` | CREATE/ALTER/DROP tables; optimize, repair, and flush tables | Schema management |
| `procedure` | Stored procedures (CREATE/DROP/EXECUTE) | Procedure management |
| `transaction` | BEGIN, COMMIT, ROLLBACK | ACID operations |
| `utility` | Connection testing, diagnostics | Troubleshooting |

**Security changes in v1.46.0 (review before upgrading):**
- `optimize_table`, `repair_table`, `flush_table`, and `optimize_fulltext` now require `ddl` instead of `utility`, so the read-only default no longer includes them. `flush_table` is limited to the connected database and no longer accepts `with_read_lock`.
- `run_select_query` drops invalid optimizer hint values and validates the query again after hints are applied.
- System schema names are detected with whitespace around the dot (e.g. `mysql . user`).

**Changes in v1.44.0 (review before upgrading):**
- **Read-only by default**: with no permissions and no categories, the server now enables only `list,read,utility` (previously every tool). To keep full access, pass `list,read,create,update,delete,execute,ddl,utility,transaction,procedure`.
- **No implicit `mysql` schema**: without a database in the connection string or `DB_NAME`, database-scoped tools report &quot;No database specified&quot; instead of using the `mysql` system schema.
- **Query cache off by default**: opt in with `CACHE_ENABLED=true`. Any write and every transaction commit now clears the cache.
- **SQL validation**: `#`, `;`, and `--` inside string values (e.g. `&#x27;#fff&#x27;`) are no longer rejected. `WITH` (CTE) queries are supported and, like derived tables, need `execute` in read queries.

**Security changes in v1.43.4:**
- `EXPLAIN ANALYZE` runs the statement it wraps (MySQL 8.0.18+), so it now requires that statement&#x27;s permission: `delete` for DELETE, `update` or `execute` for UPDATE, `read` for SELECT. Plan-only `EXPLAIN` still needs just `list` or `read`.

**Security changes in v1.43.3:**
- CSV exports require both `utility` and `read`; enable the `utilities` category when filtering categories.
- SQL within a transaction requires the corresponding operation permission. `transaction` alone does not permit reads or writes.
- `execute_write_query` accepts only INSERT/UPDATE/DELETE. DDL requires enabled DDL tools.
- Disabled tools cannot be called directly or through the Cursor bridge. The bridge requires `utility` and an enabled destination tool.
- `execute` does not bypass mandatory SQL safety restrictions, including file access and account/privilege changes.

Report suspected security issues privately via Private Vulnerability Reporting; see SECURITY.md for the policy.

Filtering rules and per-permission details are documented in **DOCUMENTATIONS.md → Permission System**.

---

### Documentation Categories (Recommended)

Use documentation categories to fine-tune which tools are exposed (Layer 2):

| Category List | Use Case | List Tools |
|---------------|----------|-----------|
| `database_discovery` | Explore databases, tables, and schema structure | `get_all_tables_relationships, list_databases, list_tables, read_table_schema` |
| `crud_operations` | Create, read, update, delete operations on data | `create_record, delete_record, read_records, update_record` |
| `bulk_operations` | High-performance batch processing operations | `bulk_delete, bulk_insert, bulk_update` |
| `seed_operations` | FK-aware relational dummy data seeding | `execute_seed_plan, generate_seed_preview, infer_seed_rules, plan_seed_data, seed_from_template, validate_seed_integrity` |
| `custom_queries` | Execute custom SQL queries and advanced operations | `execute_write_query, run_select_query` |
| `schema_management` | Manage database schema, tables, and structure | `alter_table, create_table, drop_table, execute_ddl` |
| `utilities` | Database utilities, diagnostics, and helper functions | `cursor_execute_request, describe_connection, export_query_to_csv, export_table_to_csv, list_all_tools, read_changelog, test_connection` |
| `transaction_management` | Handle ACID transactions and rollback operations | `begin_transaction, commit_transaction, execute_in_transaction, get_transaction_status, rollback_transaction` |
| `stored_procedures` | Create, execute, and manage stored procedures | `create_stored_procedure, drop_stored_procedure, execute_stored_procedure, get_stored_procedure_info, list_stored_procedures, show_create_procedure` |
| `views_management` | Create and manage database views | `alter_view, create_view, drop_view, get_view_info, list_views, show_create_view` |
| `triggers_management` | Create and manage database triggers | `create_trigger, drop_trigger, get_trigger_info, list_triggers, show_create_trigger` |
| `index_management` | Optimize performance with index and fulltext management | `analyze_index, create_fulltext_index, create_index, drop_fulltext_index, drop_index, fulltext_search, get_fulltext_info, get_fulltext_stats, get_index_info, list_indexes, optimize_fulltext` |
| `constraint_management` | Manage data integrity constraints | `add_check_constraint, add_foreign_key, add_unique_constraint, drop_constraint, drop_foreign_key, list_constraints, list_foreign_keys` |
| `table_maintenance` | Table optimization, repair, and maintenance | `analyze_table, check_table, flush_table, get_table_size, get_table_status, optimize_table, repair_table, truncate_table` |
| `query_optimization` | Analyze and optimize SQL queries | `analyze_query, get_optimization_hints, repair_query` |
| `analysis` | Data analysis, schema discovery, and reporting tools | `find_tables_by_keyword, get_column_statistics, get_database_summary, get_schema_erd, get_schema_rag_context, search_data_across_tables, search_schema` |

  Copy/paste list (comma-separated, no spaces)```text
database_discovery,crud_operations,bulk_operations,seed_operations,custom_queries,schema_management,utilities,transaction_management,stored_procedures,views_management,triggers_management,index_management,constraint_management,table_maintenance,query_optimization,analysis

Tool descriptions per category are in DOCUMENTATIONS.md → Tool Categories.


Available Tools

The server exposes 88 tools organized into categories (CRUD, seed, schema, discovery, and utilities).

  • Complete list of tools: DOCUMENTATIONS.md → Tool Categories
  • Every tool carries MCP annotations (readOnlyHint, destructiveHint, idempotentHint); see DOCUMENTATIONS.md → Tool annotations

Detailed Documentation

For comprehensive documentation, see DOCUMENTATIONS.md:

  • Remote Access - Streamable HTTP transport, bearer/OAuth authentication, sessions, protection settings, audit log

  • DDL Operations - Create, alter, and drop tables

  • Data Export Tools - Export data to CSV format
  • Relational Data Seeder - Plan, preview, execute, validate, infer rules, and template FK-aware dummy data
  • Full-Text Search - Create and search FULLTEXT indexes with multiple search modes
  • Transaction Management - ACID transactions
  • Stored Procedures - Create and execute with IN/OUT/INOUT parameters
  • Views & Triggers - Manage database views and triggers
  • Index & Constraint Management - Optimize performance and enforce data integrity
  • Table Maintenance - Analyze, optimize, check, and repair tables
  • Query Logging - See all SQL queries executed automatically
  • Security Features - Built-in security and best practices
  • Bulk Operations - High-performance batch processing
  • Troubleshooting - Common issues and solutions

MySQL MCP vs Manual Database Access

This MySQL MCP is a powerful intermediary layer between AI assistants and MySQL databases.

For full feature coverage and usage examples, see DOCUMENTATIONS.md.


License

MIT License - see LICENSE file for details.


Made with care for the AI development community

Enabling AI agents to interact with MySQL databases safely and efficiently

Report Bug · Request Feature · Documentation

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Mysql MCP 26e5c8ac 怎么安装?

在客户端按下面的安装命令接入:npx @berthojoris/mcp-mysql-server mysql://user:pass@localhost:3306/mydb "list,read,utility"。对应的包名是 @berthojoris/mcp-mysql-server。装完在客户端配置里引用同一个包或端点。

Mysql MCP 26e5c8ac 怎么在 Claude、Cursor、Windsurf 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Mysql MCP 26e5c8ac 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Mysql MCP 26e5c8ac 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Mysql MCP 26e5c8ac 支持哪些客户端?

资料标注支持 Claude、Cursor、Windsurf、Cline;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Mysql MCP 26e5c8ac 能提供哪些能力?

资料显示约 78 个工具;能力标签包括 数据库集成、生产就绪、MySQL、Claude、AI代理。具体工具清单以官方文档为准。

Mysql MCP 26e5c8ac 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Mysql MCP 26e5c8ac 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。