
DialectOS
io.github.KyaniteLabsPublished by GitHub account KyaniteLabsv0.1.0Updated Oct 24, 2026
Spanish dialect localization MCP server: 25 regional variants, glossary, adversarial QA gates.
Overview
Local MCP server and CLI that translates and QA-checks content across 25 regional Spanish variants, preserving markdown and locale-file structure.
- What you can do
- Translate text, code comments, READMEs and API docs into a chosen Spanish dialect, with dialect detection and glossary search
- Translate markdown while keeping tables, code blocks and links intact, extract translatable text, and build side-by-side bilingual documents
- Work on i18n locale files: detect missing keys, translate them, batch-translate to several dialects, create dialect variants, check tú/usted formality and apply gender-neutral language
- Research regional terms and list the supported dialects
- When to use it
- Useful when localizing documentation, app strings or support content into specific Spanish regions rather than generic Spanish, and when you want glossary enforcement and structure-preserving output checked by quality gates before publishing.
- Requirements
- Runs as a local stdio process installed from a GitHub release tarball via pnpm (Node.js toolchain). Needs an LLM endpoint configured through environment variables such as LLM_API_URL, LLM_MODEL, LLM_API_FORMAT and LLM_API_KEY, plus ALLOWED_LOCALE_DIRS for locale-file work; a local LM Studio server is an alternative.
Installation
In SourceWeft
- Open DialectOS in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[DialectOS — Spanish dialect localization MCP server: translate and QA across 25 regional variants]
🌎 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.
[CI] [Tests] [License] [Node] [pnpm] [MCP] [Security]
📖 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.
- Beta pilot: $500
- Scope: up to 10,000 source words and 5 target dialects
- Deliverables: certification report, issue list, severity table, recommended fixes, launch decision
- Sample report:
audits/sample-customer-report.md - Offer details:
docs/spanish-launch-certification.md
✨ What makes DialectOS different?
🎯 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 singlepnpm add -g/pnpm dlxcommand 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:
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.
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.
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.
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.
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.
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.
Customer-facing certification report
Use dialect:report to turn certification artifacts into a customer-facing Markdown deliverable for paid launch audits.
CLI install
From source
🛠️ MCP Tools
Markdown Translation (4 tools)
i18n Operations (6 tools)
Translation (7 tools)
📦 Packages
662+ tests across 7 packages plus docs contracts, demo-server contracts, and static-hardening checks
🛡️ Security & Quality
DialectOS has undergone adversarial security hardening:
- 18 CVEs resolved via dependency overrides
- SSRF protection on all provider endpoints
- Circuit breaker with half-open probe locks
- Atomic checkpoint writes with schema versioning
- HTML injection detection in translated output
- Semantic drift scoring — catches "looks valid but meaning changed"
- Provider capability negotiation — validates language support before API calls
- Chaos harness for deterministic resilience testing
See SECURITY.md for details.
🎨 Supported Dialects
...and 12 more. Full list via dialectos dialects list.
🏗️ Architecture
📊 Quality Gates
Every translation passes through 4 quality dimensions:
❓ FAQ
What is DialectOS? DialectOS is an open-source translation engine for Spanish regional dialects. It runs as an MCP server (for AI assistants like Claude) and a CLI tool for developers.
How is DialectOS different from Google Translate? Google Translate treats Spanish as one language. DialectOS understands 25 regional variants, preserves markdown structure, enforces glossaries, and applies quality gates that catch errors before they reach users.
What are Spanish dialects? Spanish varies significantly by country. Mexican Spanish uses "carro" for car; Spain uses "coche"; Argentina uses "auto". DialectOS handles these differences automatically.
Does DialectOS work with ChatGPT / Claude? Yes. DialectOS is an MCP server, so Claude Desktop, Cursor, Windsurf, and other MCP clients can use its 17 translation tools natively.
Is DialectOS free? Yes. DialectOS v0.3.1 is released under Apache-2.0. See LICENSE for details.
What is MCP? Model Context Protocol is an open standard that lets AI assistants use external tools. DialectOS exposes 17 translation tools through MCP so AI agents can translate natively.
Can I use DialectOS for commercial projects? Yes. Apache-2.0 allows commercial use, modification, and redistribution subject to the license terms. See LICENSE for details.
How accurate is the translation? DialectOS applies 4 quality gates (token integrity, glossary fidelity, structure integrity, semantic similarity) and adversarial tests. Automated tests verify correctness across dialects.
🏷️ Badges
Add this badge to your project if you use DialectOS for translation:
⚡ GitHub Action
Validate Spanish translations in CI on every pull request:
Multi-dialect matrix:
See docs/github-action.md for full configuration options.
🤝 Contributing
We welcome contributors! See CONTRIBUTING.md for:
- Setting up your development environment
- Running the test suite
- Submitting pull requests
- Code style guidelines
Good first issues are tagged with good first issue — perfect for newcomers.
📋 Roadmap
See ROADMAP.md for upcoming features including:
- Portuguese dialect support (pt-BR, pt-PT)
- Real-time collaborative translation
- Custom provider plugins
- OpenAI-compatible, Anthropic-compatible, and LM Studio local gateways via
LLM_API_URL/LM_STUDIO_URL+LLM_MODEL+LLM_API_FORMAT - VS Code extension
📄 License
Apache-2.0 — see LICENSE for details. Dated relicensing history of published releases: LICENSING.md.
Made with ❤️ by KyaniteLabs and contributors.
Star ⭐ this repo if it helps your project!
Part of KyaniteLabs
More from KyaniteLabs. Related projects:
- kinocut — guardrailed video-editing MCP server for AI agents (formerly mcp-video)
- Epoch — time-estimation MCP server (PERT) for AI agents
- checkyourself — local-first production-readiness checks for AI-built code
→ More at kyanitelabs.tech
What is DialectOS?
DialectOS is an open-source Spanish dialect translation server that runs as an MCP tool and CLI. It translates into 25 regional Spanish variants while preserving markdown structure, enforcing glossary terms, and applying adversarial quality gates that catch semantic drift.
Who it's for
- Primary: AI agents, documentation teams, app developers, and support teams localizing into regional Spanish
- Use when you need to translate or validate content for specific Spanish dialects while preserving markdown and locale-file structure and enforcing glossaries
- Skip if you need a general-purpose machine-translation API for many languages
FAQ
What is DialectOS?
DialectOS is an open-source Spanish dialect translation server that runs as an MCP tool and CLI. It translates into 25 regional Spanish variants while preserving markdown structure, enforcing glossary terms, and applying adversarial quality gates that catch semantic drift.
Who should use DialectOS?
AI agents, documentation teams, app developers, and support teams localizing into regional Spanish.
How is DialectOS different?
Unlike generic machine translation, DialectOS treats Spanish as 25 regional variants and gates output on token, glossary, structure, and semantic checks.
Is DialectOS production software?
Treat the README status and release tags as source of truth for maturity. Validate against your own requirements before production use.
Status
- Maintained as of 2026 on the default branch
- Prefer release tags when pinning dependencies
- Report issues on GitHub
Agent surface
- Coding agents: read this README first, then repo docs/
AGENTS.mdif present - Prefer machine-readable briefs (
llms.txt) when the repo ships one - MCP or skill entrypoints are documented in-repo when applicable
Contributing
Issues and PRs welcome on GitHub. Keep public docs free of secrets and machine-local paths.
License
See LICENSE in this repository (or package metadata if license is package-only).
Source: README.md at commit 1b232f1
Tools
0Version history
1- v0.1.0LatestOct 12, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts