From prompt to release, without leaving your editor.

1. Install the SDK

One package per framework. Keys called without a translation show up in the dashboard during development, with nothing for you to instrument.

# React (web)
npm i @sonenta/react-i18next

# Next.js · Vue · Svelte · Astro
npm i @sonenta/next
npm i @sonenta/vue-i18n
npm i @sonenta/svelte-i18n
npm i @sonenta/astro

2. Wire up the agent

sonenta init writes the project configuration and a block into CLAUDE.md or AGENTS.md. The MCP server is then declared in your client, in five lines of JSON. The same block works for Claude Code, Cursor and Claude Desktop.

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

3. Let the agent translate

You describe the intent. The agent picks its tools, reads the glossary and the context, handles only untranslated keys, and proposes. It runs on your machine: the everyday flow spends no credits.

Tool trace, an example

list_untranslated_keys  namespace=checkout  language_code=es
glossary_list · project_context_get
propose_translations_bulk
publish_cdn

4. Publish

A release builds one JSON per language and namespace, and the CDN serves it. Your apps load the new bundle with no redeploy, and with no trip through the stores on mobile.

# depuis la CLI
sonenta releases

# ou depuis l'agent, via MCP
publish_cdn