POEditor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POEDITOR_API_TOKEN | Yes | Your POEditor API token (get it from POEditor API Access) | |
| POEDITOR_PROJECT_ID | No | Default project ID (can be overridden per tool call) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_detailsB | Retrieve project metadata such as name, terms count, and last activity. Useful before performing other operations on the project. |
| add_translationsA | Add translations for EXISTING terms in a language (does not overwrite). Use this only when terms already exist. If you need to create new terms AND add their translations, prefer using add_terms_with_translations instead. Important: if a term was created with a context, you must provide the same context value to match that term. |
| update_translationsC | Update/overwrite translations for a language. Important: if a term was created with a context, you must provide the same context value to match that term. |
| list_termsB | List all project terms (optionally include translations for a specific language). Returns only term names, contexts, and translation content to minimize response size. Use limit, search, count_only, and fields parameters to reduce token usage. |
| delete_termsC | Remove one or more terms from the project. Provide the exact term and context combination to delete. |
| update_termsC | Update term metadata such as the display text, context, references, or tags. Identify each term by its current term/context values. |
| list_languagesC | List languages in the project. |
| list_available_languagesA | List all available languages that POEditor supports (not project-specific, but all possible language codes). |
| add_languageC | Add a new language to the project. Provide the language code (e.g., 'en', 'de', 'fr'). |
| add_terms_with_translationsA | PREFERRED METHOD: Create multiple new terms and add their translations in one operation. Use this instead of calling add_terms followed by add_translations separately. This ensures terms and translations are properly linked (especially important when using context). |
| delete_translationsB | Delete translations for specific terms in a language. Only remove translations you are certain are obsolete. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there is some overlap between add_terms_with_translations and the separate add_terms/add_translations pair, which could cause confusion despite clear guidance. Tools like list_available_languages and list_languages are well-differentiated by scope.
All tool names follow a consistent verb_noun pattern with underscores, such as add_language, delete_terms, and update_translations. This predictability makes the set easy to navigate and understand.
With 11 tools, the server is well-scoped for managing translations in POEditor, covering core operations like adding, updating, deleting, and listing terms, languages, and translations. Each tool serves a clear purpose without bloat.
The tool set provides comprehensive CRUD coverage for terms, translations, and languages, with minor gaps such as no direct tool for creating a project or managing project settings. However, core workflows for translation management are fully supported.