DialectOS
DialectOS is an MCP server that translates and QA-checks content into regional Spanish dialects while preserving markdown and locale-file structure.
Translate text and documents:
translate_text,translate_readme,translate_markdown, andtranslate_api_docsconvert content into a chosen Spanish dialect (e.g., es-ES, es-MX, es-AR), with optional formal/informal tone and provider selection (deepl, libre, mymemory).Preserve structure: markdown translation keeps code blocks, tables, and links intact;
extract_translatableisolates only the translatable prose for review or manual workflows.Create bilingual docs:
create_bilingual_docproduces side-by-side original and translated sections.Handle code comments:
translate_code_commentextracts and translates comments while leaving source code untouched.Manage i18n locale files:
detect_missing_keyscompares locale files,translate_missing_keysfills gaps,batch_translate_localesfans out to multiple dialects, andmanage_dialect_variantsgenerates dialect-specific locale variants.Enforce style conventions:
check_formalityverifies tΓΊ/usted (register) consistency, andapply_gender_neutralapplies latine, elles, -x, or descriptive strategies.Detect and research dialects:
detect_dialectguesses a dialect from sample text via keyword heuristics, andlist_dialectsenumerates supported dialects with metadata.Look up terminology:
search_glossaryqueries the built-in glossary of technical and business terms.
Caveats: the schema exposes 16 tools (the README advertises 18), and list_dialects describes 20 dialects while the README claims 25 β treat tool metadata as authoritative, and note dialect detection is heuristic-only.
π 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.
A 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.
Related MCP server: nativ-mcp
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.mdOffer details:
docs/spanish-launch-certification.md
β¨ What makes DialectOS different?
Feature | Google Translate | DeepL API | DialectOS |
Spanish dialect awareness | β Generic "Spanish" | β οΈ Limited variants | β 25 regional variants (5 experimental, see below) |
MCP native integration | β | β οΈ Official DeepL MCP server, generic Spanish | β 18 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) | β | β | β
|
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 |
Coverage is not equal across the 25 variants. es-AD, es-BZ, es-PH, es-GQ and es-US are experimental: their profiles lean on contact-language markers (Catalan, Kriol, Tagalog, English) and have thinner vocabulary and test data than the major variants.
Dialect detection is a keyword heuristic. Its last recorded top-1 accuracy was 54.8% on the bundled detection corpus, and that corpus was written from the detector's own keyword lists, so the figure is not an independent measure. Treat
detect_dialectoutput as a hint, not a verdict.
π― 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.2 is distributed as GitHub Release tarballs.
GET https://registry.npmjs.org/@kyanitelabs/dialectosandGET https://registry.npmjs.org/dialectosboth return 404 β there is no npm package. The CLI and MCP tarballs bundle the unpublished@dialectos/*workspace packages, so a singlepnpm add -g/pnpm dlxof the tarball URL works. 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.2/dialectos-mcp-0.3.2.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"
}
}
}
}ALLOWED_LOCALE_DIRS is a comma-separated list of the only directories the
server may read or write; when set, it replaces the working directory. Without
it the server falls back to its working directory, but never to / or your
home directory, so set it when your client starts servers from either.
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 demoOpen 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-evalIncremental 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-certifyAdversarial 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-adversarialLong-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-certCustomer-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
# Install the v0.3.2 CLI tarball from the GitHub Release
pnpm add -g https://github.com/KyaniteLabs/DialectOS/releases/download/v0.3.2/dialectos-cli-0.3.2.tgz
# Or use a local source checkout
pnpm install --frozen-lockfile
pnpm build
# Translate to Mexican Spanish
dialectos translate "Hello world" --dialect es-MX
# Translate a README preserving structure
dialectos translate-readme README.md --dialect es-AR --output README.ar.md
# Validate an existing translation
dialectos validate --source "Click the button" --translated "Haz clic en el botΓ³n" --dialect es-MX
# Validate translation files
dialectos validate --source-file en.json --translated-file es-MX.json --dialect es-MX --format json
# View translation corpus statistics
dialectos corpus stats
# Run dialect quality benchmark
dialectos benchmark run --dialects es-MX,es-AR,es-ES
# Generate glossary suggestions from corrections
dialectos glossary suggest --min-occurrences 3
# Compare two glossary versions
dialectos glossary diff glossary-v1.json glossary-v2.json
# Detect missing i18n keys
dialectos i18n detect-missing ./locales/en.json ./locales/es.json
# List all supported dialects
dialectos dialects listFrom source
git clone https://github.com/KyaniteLabs/DialectOS.git
cd DialectOS
pnpm install
pnpm build
pnpm test # 1,500+ tests passingπ οΈ MCP Tools
Markdown Translation (4 tools)
Tool | Description |
| Translate while preserving tables, code blocks, links |
| Extract only translatable text from markdown |
| Translate API docs with table cell-level translation |
| Side-by-side bilingual documents |
i18n Operations (6 tools)
Tool | Description |
| Compare locale files for missing keys |
| Auto-translate missing keys |
| Batch translate to multiple dialects |
| Create dialect-specific variants |
| Check tΓΊ vs usted consistency |
| Apply gender-neutral language |
Translation (7 tools)
Tool | Description |
| Translate with semantic context, grammar profiles, and quality contracts |
| Detect dialect from sample text (heuristic; see accuracy note below) |
| Translate comments, preserve code |
| Full README translation pipeline |
| Search 300+ source-attributed glossary terms |
| List all 25 supported dialects |
| Research source-backed regional lexeme proposals without mutating runtime data |
| Check an existing translation with the same validator as the CLI and GitHub Action |
π¦ Packages
Package | Version (source) | Description | Tests |
| 18 MCP tools (stdio server) | 93 | |
| CLI: translate, validate, corpus, benchmark, glossary | 569 | |
| LLM, DeepL, LibreTranslate, MyMemory with circuit breaker + corpus | 152 | |
| Rate limiting, SSRF protection, sanitization | 68 | |
| Shared TypeScript types + glossary, profile, certification, and quality data | 54 | |
| Locale file diff/merge utilities | 55 | |
| Structure-preserving markdown parser | 74 |
1,500+ tests across 7 packages plus docs contracts, demo-server contracts, and static-hardening checks
Package versions above match the latest GitHub release, v0.3.2.
π‘οΈ Security & Quality
DialectOS has undergone adversarial security hardening:
Known dependency advisories patched with pinned overrides (see CHANGELOG)
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
Code | Region | Example Difference |
| Spain | "Coche" (car), "Ordenador" (computer) |
| Mexico | "Carro", "Computadora" |
| Argentina | "Auto", "Computadora", "Che" |
| Colombia | "Carro", "Computador", "ChΓ©vere" |
| Chile | "Auto", "Computadora", "Caleta" |
| Peru | "Carro", "Computadora", "Pe" |
| Venezuela | "Carro", "Computadora", "Chamo" |
| Uruguay | "Auto", "Computadora", "Bo" |
| Equatorial Guinea | "Carro", "Camisola", "Bacalao" |
| United States | "Carro", "Computadora", "Pocha" |
| Philippines (Chavacano) | "Carro", "Jendeh", "Kame" |
| Belize | "Carro", "Breki", "Kriol" |
| Andorra | "Carro", "Madriu", "Caldea" |
...and 12 more. Full list via dialectos dialects list.
ποΈ Architecture
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β MCP Client β
β (Claude Desktop / Cursor / etc.) β
ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β stdio
ββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββ
β @dialectos/mcp β
β 18 tools β’ JSON-RPC over stdio β
ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β
ββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββ
β @dialectos/cli β
β translate β’ validate β’ corpus β’ benchmark β’ glossary β
β ββ Policy profiles (strict/balanced/permissive) β
β ββ Quality gates (token/glossary/structure/semantic) β
β ββ Translation corpus + auto-glossary β
β ββ Checkpoint resumption + telemetry β
ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β
ββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββ
β @dialectos/providers β
β βββββββββββ βββββββββββββββββββ βββββββββββββββββββ β
β β LLM β β DeepL β β Libre/MyMemory β β
β β Primary β β Paid fallback β β Generic fallbackβ β
β βββββββββββ βββββββββββββββββββ βββββββββββββββββββ β
β β β β β
β ββββββββββββββββββ΄βββββββββββββββββββββ β
β Circuit Breaker + Rate Limiter β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββπ Quality Gates
Every translation passes through 4 quality dimensions:
Quality Score = tokenIntegrityΓ25% + glossaryFidelityΓ30% + structureIntegrityΓ20% + semanticSimilarityΓ25%Gate | What it checks | Example failure |
Token Integrity | Protected terms preserved | "Kyanite Labs" β "Cianita Labs" |
Glossary Fidelity | Enforced terminology used | "API" β "Interfaz" (when glossary says "API") |
Structure Integrity | Markdown structure intact | Missing code fence, broken table |
Semantic Similarity | Meaning not drifted | "API is down" β "Hello world" |
β 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.2 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:
[](https://github.com/KyaniteLabs/DialectOS)β‘ GitHub Action
Validate Spanish translations in CI on every pull request:
- uses: KyaniteLabs/DialectOS@v0.3.2
with:
dialect: es-MX
source-dir: locales/en
target-patterns: 'locales/es-MX/*.json'
fail-on-blocking: trueMulti-dialect matrix:
strategy:
matrix:
dialect: [es-ES, es-MX, es-AR, es-CO]
steps:
- uses: KyaniteLabs/DialectOS@v0.3.2
with:
dialect: ${{ matrix.dialect }}
fail-on-blocking: trueSee 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_FORMATVS 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.
Product | DialectOS |
Category | Spanish dialect translation and localization-QA MCP server and CLI |
Best for | AI agents, documentation teams, app developers, and support teams localizing into regional Spanish |
Not | a general-purpose machine-translation API for many languages |
Source | |
Keywords | Spanish dialect translation MCP server, Spanish localization QA, regional Spanish translator, glossary enforcement, i18n validation CLI |
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 presentPrefer machine-readable briefs (
llms.txt) when the repo ships oneMCP 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).
Available Tools
16 toolsapply_gender_neutralB
Apply gender-neutral language strategies to a locale file
Inputs: localePath (required), strategy.
batch_translate_localesC
Translate base locale to multiple target dialects
Inputs: targets (required), directory (required), provider, baseLocale.
check_formalityC
Check locale file for formality consistency
Inputs: localePath (required), register.
create_bilingual_docB
Create a side-by-side bilingual document with original and translated sections
Inputs: filePath (required), dialect, provider.
detect_dialectB
Detect Spanish dialect from text using keyword matching
Inputs: text (required).
detect_missing_keysB
Compare two locale files and report missing keys
Inputs: basePath (required), targetPath (required).
extract_translatableA
Extract translatable text from a markdown file (excludes code blocks, HTML)
Inputs: filePath (required).
list_dialectsA
List all 20 Spanish dialects with metadata
Inputs: no named parameters.
manage_dialect_variantsB
Create dialect-specific variants of a locale file
Inputs: variant (required), sourcePath (required), outputPath.
search_glossaryB
Search the built-in glossary for technical and business terms
Inputs: query (required).
translate_api_docsB
Translate API documentation markdown with optimized handling for tables and lists
Inputs: filePath (required), dialect, provider.
translate_code_commentC
Extract and translate code comments (basic text extraction)
Inputs: code (required), dialect, provider.
translate_markdownB
Translate a markdown file while preserving structure (code blocks, links, etc.)
Inputs: filePath (required), formal, dialect, informal, +1 more.
translate_missing_keysB
Translate missing keys from base locale to target locale
Inputs: basePath (required), targetPath (required), dialect, provider.
translate_readmeB
Translate a README markdown file preserving structure
Inputs: filePath (required), formal, dialect, informal, +1 more.
translate_textB
Translate text to a Spanish dialect
Inputs: text (required), formal, dialect, informal, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 16 tools
Most tools have clearly distinct purposes, but there is some potential overlap among translate_markdown, translate_readme, and translate_api_docs; descriptions alleviate confusion slightly.
All tools follow the verb_noun pattern in snake_case, making naming fully consistent and predictable.
16 tools is well-scoped for a dialect translation server, covering translation, detection, management, and glossary without being excessive.
The tool set covers core translation, detection, and locale management needs, but could include a direct validation or export tool for full completeness.
Maintenance
Related MCP Connectors
MCP server for Translation Services
Phrase MCP server: language intelligence platform for translation, terminology, and quality.
Translate MCP β LibreTranslate-compatible machine translation.
Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides standardized translation services across six languages (Arabic, Chinese, English, French, Russian, Spanish) using Claude Sonnet 3.5, with support for different domains and formality levels.3MIT

nativ-mcpofficial
AlicenseAqualityBmaintenanceAI-powered localization platform. Translate text, search translation memory, and access style guides from any MCP-compatible AI tool.21298 PyPI1MIT- AlicenseNot gradedqualityCmaintenanceAI-powered translation MCP server with EU AI Act compliance, enabling automated translation workflows via the MCP protocol.7 npm44 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive localization data for 174 locales, enabling AI agents to generate culturally-adapted multilingual content.MIT