تخطَّ إلى المحتوى
Sonenta
← All documentation

Quickstart · for developers

Run your i18n from your editor

Sonenta is MCP-first: it plugs into the AI dev environment you already use — Claude Code, Cursor, Claude Desktop — so you create keys, translate and publish by asking your agent, right where you code. No copy-pasting strings into a dashboard.

1 · Get your API key

Grab a project API key once — from the dashboard, or straight from your terminal:

npx @sonenta/cli login
Get a key in the dashboard →

2 · Add the Sonenta MCP to your AI environment

Drop this into your MCP config (Claude Desktop, Claude Code, or .cursor/mcp.json). Your agent now has tools to create keys, translate with AI, and publish to the CDN — e.g. create_keys_bulk, propose_translations_bulk, publish_cdn.

{
  "mcpServers": {
    "sonenta": {
      "command": "npx",
      "args": ["-y", "@sonenta/mcp"],
      "env": {
        "SONENTA_API_KEY": "snt_live_<prefix>.<secret>",
        "SONENTA_PROJECTS": "<project_uuid>"
      }
    }
  }
}

See the full MCP setup for Cursor / Claude Code / Claude Desktop specifics and the complete tool list.

3 · Install the runtime SDK in your app

Add the SDK so your app loads translations live from the CDN. @sonenta/react-i18next is a drop-in for react-i18next — keep your t() calls.

npm i @sonenta/react-i18next
import { SonentaProvider } from "@sonenta/react-i18next";

<SonentaProvider token={import.meta.env.VITE_SONENTA_TOKEN} projectUuid="proj_xxx" defaultLocale="en">
  <App />
</SonentaProvider>

4 · Work from your editor

Now just ask your agent, in plain language:

“Extract the new strings in the checkout flow, create the keys under the checkout namespace, translate them to FR and ES, then publish.”

It calls the Sonenta MCP tools and the keys are live. Prefer scripts/CI? The sonenta CLI (@sonenta/cli) does the same — sonenta push, sonenta pull, sonenta import. Either way: no manual key entry.

Next