MCP MySQL tool parser rejects cross-schema dot notation (schema.table)

Resolved 💬 7 comments Opened Mar 9, 2026 by VoxCore84 Closed Apr 27, 2026

Bug Description

The MCP MySQL tool's SQL parser fails when queries use cross-schema dot notation (schema.table). This is standard MySQL syntax required for any multi-database workflow.

Reproduction

DESCRIBE world.gameobject_template

Expected

Returns column definitions for the table.

Actual

Error: Parsing failed: Expected "#", "--", "/*", ";", "GO", [ \t\n\r], [A-Za-z0-9_$\x80-￿], or end of input but "." found.

Workaround

Fall back to the Bash tool with the mysql CLI:

mysql -u root -padmin -e "DESCRIBE gameobject_template" world

This works but defeats the purpose of having an MCP tool for database access.

Impact

Any project with multiple databases (common in game servers, microservices, data pipelines) needs cross-schema queries. The parser appears to use a grammar that doesn't recognize the database.table syntax, which is fundamental MySQL.

Environment

  • Claude Code 2.1.71
  • MySQL 8.0
  • Windows 11
  • MCP MySQL server (bundled)

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗