DialectsLABSCO SUMMARY
Checking the dialect list first is the whole discipline.
Two tools, and the order matters: ask what sqlglot supports, then transpile in those terms. That is what keeps an assistant from confidently naming a dialect that does not exist and getting a plausible-looking result. Errors surface as errors — an unsupported dialect or a syntax problem is reported rather than silently smoothed over, which for query translation is the only acceptable behaviour.
What it is
An MCP tool built on the sqlglot library for translating SQL between dialects — MySQL to PostgreSQL, and every other pair sqlglot knows. It reports unsupported dialects and syntax errors rather than returning quietly broken SQL.
What you get
- The full list of SQL dialects sqlglot supports, so the conversion is asked for in terms it recognises —
Dialects - Query conversion from a source dialect to a target dialect —
Transpiler - Explicit error reporting when a dialect is unsupported or the input does not parse
Requirements
No account and no key. Two paths: locally with Python 3.13 or newer and uv sync --frozen then uv run server.py, or build the Docker image and run it with docker, passing -i, --rm and --init. Client configuration is a plain command entry either way. The package is sqltranspiler (version 0.1.0).
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Porting a query to a different database
Confirm both dialects are supported, then transpile the query rather than rewriting the syntax by hand.
02
Migrating a set of reports between engines
Run each query through the transpiler and let syntax errors surface as errors instead of finding them in production.
03
Checking whether a migration is even feasible
List the supported dialects first to see whether the source and the target are both covered.
2 tools
Listed in project docs. Your client may show a different list.
TranspilerBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- docker on PATH
- Python 3.13+
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
TERMINAL
git clone https://github.com/Baronco/SQL-Transpiler-MCP-Tool.git
cd SQL-Transpiler-MCP-Tool
docker build -t sql-transpiler .MCP Clients
Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"sql-transpiler": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e",
"DOCKER_CONTAINER=true",
"sql-transpiler"
]
}
}
}Claude Desktop — uv
CLAUDE DESKTOP — UV · JSON
{
"mcpServers": {
"sql-transpiler": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_SQL_TRANSPILER_MCP_TOOL>",
"run",
"server.py"
]
}
}
}<YOUR_PATH_TO_SQL_TRANSPILER_MCP_TOOL> is the absolute path of your clone, and run uv sync --frozen in it once first.
