Sonenta

com.sonentaPublished by sonenta.comv0.57.0Updated Oct 28, 2026

MCP server for Sonenta translation management: keys, translations, a11y, and source-health tools.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server for Sonenta translation management, giving an assistant tools for keys, translations, accessibility and source-health work.

What you can do
  • Manage translation keys and translations in Sonenta projects
  • Work on accessibility (a11y) items
  • Check source health for translation sources
  • Scope work to specific projects by UUID
  • Tag sessions with an agent name, type and version for the Sonenta dashboard
When to use it
Useful when a team keeps its localization in Sonenta and wants an assistant to inspect or maintain keys, translations, accessibility and source health from the editor or terminal instead of the web dashboard.
Requirements
Runs locally over stdio from the npm package @sonenta/mcp, so Node.js is needed. Requires a Sonenta API key with mcp scope, supplied as SONENTA_API_KEY or read from the local credentials file after running the Sonenta login command. Optional variables set the API host, project scope and agent identity.
Before you install
The API key is a credential; keep it out of shared configs and logs. Project scoping is optional, so without SONENTA_PROJECTS or SONENTA_PROJECT the server may reach more projects than intended. Translation and key tools likely change project data, so review writes before approving them. Requests go to the Sonenta API host, which can be overridden.

Installation

In SourceWeft

  1. Open Sonenta in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.57.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.