π DialectOS
TL;DR: DialectOS β open-source MCP server and CLI for translating and QA-checking content across 25 regional Spanish variants. Best for AI agents, documentation teams, and app developers localizing into Spanish.
The first Model Context Protocol server built specifically for Spanish dialects.
DialectOS is an open-source Spanish dialect translation server that runs as an MCP
(Model Context Protocol) tool and CLI. It translates English and other languages into
25 regional Spanish variants β Mexican, Argentinian, Colombian, Puerto Rican, and more β
while preserving markdown structure, enforcing glossary terms, and applying adversarial
quality gates that catch semantic drift before it reaches users.
Translate, detect, and adapt content across 25 regional Spanish variants while preserving markdown structure, code comments, and locale file formatting.

π Documentation Β·
π Quick Start Β·
π οΈ MCP Tools Β·
Agent Skill Β·
π¦ Packages Β·
π€ Contributing Β·
π Roadmap
Public Discovery
DialectOS is a Spanish localization and dialect QA system for AI agents, documentation teams, app developers, and support organizations. It provides MCP tools, CLI workflows, glossary enforcement, locale-file validation, and adversarial quality gates for regional Spanish variants.
AI discovery: llms.txt provides a compact project summary for AI assistants and search crawlers.
Best-fit searches: Spanish dialect translation MCP server, Spanish localization QA, Model Context Protocol translation tool, i18n validation CLI, regional Spanish translator, glossary enforcement, AI localization audit, Spanish launch certification.
Agent Skill
DialectOS includes a public agent skill at skills/dialectos/SKILL.md. Use $dialectos in compatible agent hosts when you want an agent to choose the right MCP or CLI workflow for regional Spanish translation, markdown preservation, locale-file validation, glossary enforcement, register checks, and launch-readiness QA.
Spanish Launch Certification
DialectOS is available as a paid Spanish localization launch audit. We certify your Spanish docs, app strings, support macros, or locale files across target dialects and deliver an MQM-aligned launch-readiness report.
β¨ What makes DialectOS different?
| Feature | Google Translate | DeepL API | DialectOS |
|---|
| Spanish dialect awareness | β Generic "Spanish" | β οΈ Limited variants | β
25 regional variants |
| MCP native integration | β | β | β
17 MCP tools |
| Markdown structure preservation | β | β | β
Tables, code blocks, links intact |
| i18n locale file support | β | β | β
JSON locale diff & merge |
| Gender-neutral language | β | β | β
elles / latine / -x |
| Formality checking (tΓΊ vs usted) | β | β | β
Cross-dialect consistency |
| Adversarial quality gates | β | β | β
Semantic drift + structure validation |
| LLM-first dialect adaptation | β Generic MT | β οΈ Limited dialect control | β
Any OpenAI/Anthropic/LM Studio local LLM + dialect contracts |
| Translation validation (any provider) | β | β | β
dialectos validate β standalone correctness check |
| GitHub CI integration | β | β | β
Composite action for PR validation |
| Auto-glossary from corrections | β | β | β
Learns from user feedback |
| Public benchmark suite | β | β | β
205 adversarial samples across 25 dialects |
π― Why this exists
"We shipped a product to Mexico using our Spain Spanish translations. Users thought we were being intentionally rude."
Spanish is not one language β it's 25 regional variants with different vocabulary, formality levels, slang, and grammatical preferences. Existing translation tools treat Spanish as a monolith.
DialectOS solves this by:
- Understanding regional differences (es-MX vs es-ES vs es-AR vs es-CO...)
- Preserving technical document structure during translation
- Providing glossary enforcement for consistent terminology
- Adding semantic context, dialect grammar profiles, quality contracts, and quality gates that catch drift before it reaches users
- Running as an MCP server so AI assistants can translate natively
π Quick Start
Install note: DialectOS v0.3.1 is distributed through GitHub Release tarballs, not the npm registry. The CLI and MCP tarballs bundle the unpublished @dialectos/* workspace packages, so a single pnpm add -g / pnpm dlx command works without a registry publish. Clone the repo only for local development or the browser demo.
MCP setup
Add the released MCP server to Claude Desktop, Cursor, or any MCP client:
{
"mcpServers": {
"dialectos": {
"command": "pnpm",
"args": [
"dlx",
"https://github.com/KyaniteLabs/DialectOS/releases/download/v0.3.1/dialectos-mcp-0.3.1.tgz"
],
"env": {
"LLM_API_URL": "https://your-llm-gateway/v1/chat/completions",
"LLM_MODEL": "your-dialect-capable-model",
"LLM_API_KEY": "your-key-if-required",
"LLM_API_FORMAT": "openai",
"ALLOWED_LOCALE_DIRS": "/path/to/locales"
}
}
}
}
For local development from a source checkout, run pnpm build and point your MCP client at packages/mcp/dist/index.js.
Full-app browser demo
The browser demo requires a source checkout.
The browser demo is no longer a fake/static rule replacer. It calls a local
DialectOS backend, and that backend calls the configured provider stack.
LLM_API_URL="http://127.0.0.1:1234/v1/chat/completions" \
LLM_API_FORMAT="openai" \
LLM_MODEL="your-local-model-name" \
LLM_ALLOW_LOCAL=1 \
pnpm demo
Open http://127.0.0.1:8080.
For the beginner container walkthrough, see
docs/full-app-demo.md.
Recommended certified models
For v0.3.0, the recommended default cloud model is glm-4.5-air through the Z.ai international Anthropic-compatible endpoint. It passed basic, expanded adversarial, and long-document certification. Use glm-5.1 when you want the higher-confidence/premium option, and qwen3.5-9b via LM Studio for local/offline certification.
export LLM_API_URL="https://api.z.ai/api/anthropic/v1/messages"
export LLM_MODEL="glm-4.5-air"
export LLM_API_FORMAT="anthropic"
export LLM_API_KEY="..."
LM Studio local model testing
Start LM Studio's local server, then point DialectOS at any downloaded local model. LLM_API_FORMAT=lmstudio uses LM Studio's native REST API and loads the model just-in-time when needed.
LM_STUDIO_URL="http://127.0.0.1:1234" \
LLM_MODEL="publisher/model-key-or-api-identifier" \
LLM_API_FORMAT="lmstudio" \
pnpm dialect:eval -- --live --provider=llm --out=/tmp/dialectos-lmstudio-eval
Incremental provider certification
Use dialect:certify for long local-model or cloud-provider runs. It writes events.jsonl, progress.json, and an incrementally updated results.json after every sample, with per-sample timeout protection.
LM_STUDIO_URL="http://127.0.0.1:1234" \
LLM_MODEL="qwen3.5-9b" \
LLM_API_FORMAT="lmstudio" \
pnpm dialect:certify -- --live --provider=llm --sample-timeout-ms=300000 --out=/tmp/dialectos-certify
Adversarial dialect certification
Use dialect:certify:adversarial to run paraphrase, dialect-collision, taboo-copy, placeholder, register, and repeatability traps. It wraps dialect:certify and writes a failure-matrix.md plus aggregate repeatability results.
pnpm dialect:certify:adversarial -- --live --provider=llm --repeat=2 --sample-timeout-ms=300000 --out=/tmp/dialectos-adversarial
Long-document certification
Use dialect:certify:documents to certify README/API-doc/locale JSON flows, not just sentence fixtures. It checks markdown structure, placeholders, URLs, code fences, API tables, and locale JSON outputs.
pnpm dialect:certify:documents -- --live --provider=llm --dialects=es-MX,es-PA,es-PR --out=/tmp/dialectos-doc-cert
Customer-facing certification report
Use dialect:report to turn certification artifacts into a customer-facing Markdown deliverable for paid launch audits.
pnpm dialect:report -- --input=audits/release-candidate-2026-04-22/model-matrix.json --out=customer-report.md --customer="Acme SaaS" --product="Spanish launch"
CLI install