Skip to main content

Integrations

Pick the one that fits your workflow — they all share the same open-source translation engine and use your own LLM key.

CLI

Check locale files from your terminal or CI — and retranslate just the keys that fail. The fastest way to start.

  • One command, no config file
  • Any language your model speaks
  • Placeholder preservation and validation
  • Incremental mode
  • Anthropic, OpenAI or a custom adapter

MCP Server

Check and review your locale files from Claude Desktop, Cursor or any MCP client — validation needs no API key.

  • Validation tools need no API key and make no model call
  • check_locales, check_glossary, diff_locales, review_locales
  • Your agent reviews meaning using its own model
  • Translation available too, with your own provider key

Vite Plugin

Keep translations current at build time — incremental, cached, placeholder-safe.

  • Runs during build — no key in the browser
  • Caches unchanged strings
  • Regional fallback (pt-BR to pt)
  • Falls back to the source language on failure

GitHub Action

Retranslate changed keys automatically on every push or pull request.

  • Commits directly or opens a pull request
  • Incremental translation
  • Local placeholder verification
  • Skip keys or paths with globs

Node.js

Call the translation engine directly from your own scripts with @shipi18n/core.

  • The engine every package is built on
  • Structure-preserving JSON translation
  • Placeholder extraction and validation
  • Any provider through a custom adapter

React

Translate your locale files at build time, then read them with react-i18next as usual.

  • No API key in the browser
  • Works with react-i18next
  • Placeholders and Trans markup survive
  • Zero runtime dependency

Next.js

Generate translated message files during the build and serve them from Server Components.

  • App Router and Pages Router
  • Translation runs in the build step
  • No key reaches the client bundle
  • Pairs with next-intl or i18next

Vue

Translate locale files at build time and load them with vue-i18n.

  • Works with Vue 3 and vue-i18n
  • Use the CLI or the Vite plugin
  • Named interpolation is preserved
  • No runtime dependency

Quick Start

1. Get an LLM key

Shipi18n has no account. Bring your own key from Anthropic or OpenAI — you pay your provider directly.

Read the docs

2. Install the package

npm install -D @shipi18n/cli @anthropic-ai/sdk

3. Set the key in your environment

export ANTHROPIC_API_KEY=your-key-here
# or OPENAI_API_KEY, with --provider openai

4. Start translating

npx @shipi18n/cli translate locales/en.json -t es,fr,de

Need more details?

The full documentation covers every option for the CLI, the MCP server, the core library and the build integrations.

Browse the repositories