About sonenta
MCP server for Sonenta translation management: keys, translations, a11y, and source-health tools
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @sonenta/mcpSONENTA_API_KEYSecretSonenta API key (mcp:* scope). If omitted, the server reads it from ~/.sonenta/credentials (run `sonenta login`). Legacy SONENTA_TOKEN / VERBUMIA_API_KEY / VERBUMIA_TOKEN are also accepted.SONENTA_API_BASEAPI host. Defaults to https://api.sonenta.dev.SONENTA_PROJECTSComma-separated project UUIDs to scope the server to. Optional; use SONENTA_PROJECT for a single project.SONENTA_AGENT_NAMEOptional agent identity — a short run name that groups this session's work in the Sonenta dashboard.SONENTA_AGENT_TYPEOptional agent identity — the agent kind (e.g. sonenta-i18n, sonenta-a11y).SONENTA_AGENT_VERSIONOptional agent identity — the agent version. Defaults to the server's own version when unset.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.