Editor tools
Editor and IDE plugins
Bring transglot into your editor through the language server, and into your AI coding assistant through the MCP server.
transglot reaches your editor in two ways. Both are npm packages, both authenticate with a deploy token, and both can do only what the token's abilities allow.
| Tool | Package | Works in | What you get |
|---|---|---|---|
| Language server | @transglot/lsp | Neovim, JetBrains IDEs (through LSP4IJ), Helix, Sublime Text, and any editor with an LSP client | Missing translations flagged as diagnostics, translations on hover and in CodeLens, and a code action that turns a hardcoded string into a key. |
| MCP server | @transglot/mcp | Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, and any other MCP client | An AI agent that reads and edits translations, syncs files, starts translation runs and manages the glossary. |
Which one to use
- You want to see translations while you edit keys: the language server. It reads your
transglot.jsonand works on JSON message files. - You want an assistant to do localization work for you: the MCP server. Ask it to fill missing translations, check a key in every language, or add a glossary term.
- You want to sync files from a terminal or CI: neither. Use the CLI or the GitHub Action.
Set up
Publishable keys
The browser-safe key the in-context editor starts its session with, the origins it works from, and how your backend grants write access.
Language server
Install the transglot language server to see translations beside your keys, flag missing ones, and extract hardcoded strings in Neovim, JetBrains IDEs, Helix, Sublime Text or any other editor with an LSP client.