Skip to main content
Glama

Turjuman

Open-source, self-hosted translation management — managed by your AI agent.

Turjuman is a lightweight, open-source alternative to commercial translation-management SaaS. Instead of a heavy web dashboard, you manage projects, keys, locales and translations through an MCP server connected to Claude Code (or any MCP client/agent). A thin developer CLI handles the deterministic file work — pulling/pushing locale files in your repo and CI.

It runs on a serverless AWS stack (Lambda + DynamoDB) that costs ~nothing to host and fits comfortably in the free tier. No always-on servers, no Cognito.

Claude Code / agent ──Streamable HTTP + API key──┐
Developer CLI / CI ──REST + API key──────────────┤
                                                 ▼
                          Lambda Function URLs ──► DynamoDB (single table)

Why MCP-first?

Translation management is mostly conversation + judgement: "add a French locale", "translate the untranslated checkout strings", "what does cart.empty say in German?". An agent with the right tools does this naturally. The connected LLM does the translating itself — there's no separate machine-translation engine to pay for or configure.

The CLI exists for the things you should not hand to an LLM: deterministically exporting a JSON/YAML file, downloading translations, and syncing them in CI.

Related MCP server: i18n Agent

Features (v1)

  • MCP server with 36 tools: projects, locales, keys (with descriptions/context), translations, bulk fill, review workflow, and full user/member/API-key administration (incl. key revocation).

  • First-class RBAC. Global roles (OWNER/ADMIN/MEMBER) + per-project roles (MANAGER/EDITOR/DEVELOPER/VIEWER). High-privilege users manage everyone else's access.

  • Glossary + translation memory, and webhooks (HMAC-signed, via DynamoDB Streams) for change events.

  • API-key auth — simple bearer tokens, stored hashed. (OAuth/Cognito is a future option.)

  • Developer CLIlogin, init, pull, push, build with multi-target config and adapters for JSON (nested/flat), YAML, Flutter ARB, Java .properties, CSV, Android strings.xml, and iOS .strings/.stringsdict (ICU-canonical plurals converted to each format's native form).

  • DynamoDB single-table design, on-demand billing. Multi-tenant-ready (orgId on every record).

Repository layout

Package

What it is

packages/core

Domain model, DynamoDB repository, RBAC, services, format adapters (the shared brain)

packages/mcp-server

Stateless Streamable HTTP MCP server → Lambda

packages/api

REST API for the CLI/CI → Lambda, plus the webhook dispatcher

packages/cli

The turjuman developer CLI (incl. the AWS CDK deployer in src/deploy/)

Try it locally (no AWS)

The fastest way to see Turjuman work — everything runs against DynamoDB Local, no cloud account needed:

npm install && npm run build
docker run -d --rm -p 8000:8000 amazon/dynamodb-local

# create the table + first owner, and print your API key
node scripts/dev-setup.mjs you@example.com "You"

# start the servers (each in its own shell), pointed at DynamoDB Local
export AWS_ENDPOINT_URL_DYNAMODB=http://localhost:8000 TURJUMAN_TABLE=Turjuman
export AWS_ACCESS_KEY_ID=local AWS_SECRET_ACCESS_KEY=local AWS_REGION=us-east-1
node packages/mcp-server/dist/local.js   # MCP  on http://localhost:3000
node packages/api/dist/local.js          # REST on http://localhost:4000

Point your MCP client at http://localhost:3000/ with the printed API key (see below) and start talking to it.

Self-host on AWS

Status: the SAM stack is conventional but has not yet been verified end-to-end against a live AWS account (see ROADMAP). Use the local path above to evaluate; treat the cloud deploy as beta and please report issues.

1. Deploy to your AWS account

One command self-bootstraps the CDK environment, deploys the CloudFormation stack from pre-bundled Lambda assets, and creates your first owner — no SAM CLI, no clone needed (see Self-hosting for options):

npx @turjuman/aws-deploy deploy   # interactive; prints McpUrl/ApiUrl and your API key

Self-hosting ships as a separate @turjuman/aws-deploy package (binary turjuman-aws-deploy) so the day-to-day turjuman developer CLI stays a lean, AWS-free install.

2. Your first owner + API key

turjuman-aws-deploy deploy creates the first owner at the end and prints the API key once (also saved to ~/.turjuman/auth.json, so you're logged in). It refuses to create a second owner once the org has users, so re-running deploy to update the stack is safe.

3. Connect Claude Code (MCP)

Add to your .mcp.json (see .mcp.json.example):

{
  "mcpServers": {
    "turjuman": {
      "type": "http",
      "url": "<McpUrl>",
      "headers": { "Authorization": "Bearer <your-api-key>" }
    }
  }
}

Keep your key out of version control. .mcp.json is often committed — prefer referencing the token via an environment variable / secret manager rather than pasting the literal key. If a key ever leaks, revoke it immediately with the revoke_api_key tool.

Then just ask: "Create a project called Web App with base locale en, add fr and es, and translate everything into French."

4. Sync files in your repo (CLI)

npx turjuman login --url <ApiUrl> --key <your-api-key>
npx turjuman init --project <proj_id> --format json-nested --path "locales/{locale}.json"
npx turjuman pull     # write locale files from Turjuman
npx turjuman push     # upload source keys / translations

Documentation

The full documentation lives in docs/ and is published as a documentation site with Mintlify — one source that serves human readers, external agents (Mintlify auto-generates llms.txt / llms-full.txt and an "open in Claude/ChatGPT" menu per page), and the agents working in this repo. Start here:

Development

npm install
npm run build
npm test            # unit tests (hermetic)

# integration tests against an emulated AWS (LocalStack DynamoDB):
npm run e2e:up && npm run test:integration && npm run e2e:down

# full deployed end-to-end (SAM stack on LocalStack: Lambda Function URLs +
# the real DynamoDB Streams -> webhook flow). Just needs Docker:
npm run test:e2e

See Contributing for the full testing guide (unit, LocalStack integration, and deployed end-to-end), which also runs in CI.

License

MIT

A
license - permissive license
-
quality - not tested
A
maintenance

Maintenance

Maintainers
Response time
0dRelease cycle
8Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mogharsallah/turjuman'

If you have feedback or need assistance with the MCP directory API, please join our Discord server