- Home
- MCP servers
- POEditor
POEditor
- javascript
3
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"ryan-shaw-poeditor-mcp": {
"command": "npx",
"args": [
"poeditor-mcp@latest"
],
"env": {
"POEDITOR_API_TOKEN": "your_api_token_here",
"POEDITOR_PROJECT_ID": "your_project_id"
}
}
}
}You run a POEditor MCP Server to interact with POEditor’s translation management API through the MCP protocol. It lets you manage terms, translations, languages, and project details from an MCP client with a simple, scalable server that handles requests against POEditor.
How to use
You configure the MCP server in your client by adding the POEditor MCP configuration to your MCP settings. Once wired up, you can create terms, add translations, update existing translations, list terms, and manage languages and project details directly from your MCP client.
How to install
Prerequisites: you need Node.js and npm installed on your machine.
Install dependencies and build the server.
npm install
npm run build
Configuration and usage notes
Configure the MCP server in your client by adding a POEditor entry to your MCP settings. The key configuration detail is the command to run the MCP server along with any required environment variables.
{
"mcpServers": {
"poeditor": {
"command": "npx",
"args": ["poeditor-mcp@latest"],
"env": {
"POEDITOR_API_TOKEN": "your_api_token_here",
"POEDITOR_PROJECT_ID": "your_project_id"
}
}
}
}
Security and environment notes
Keep your API token secure. Do not commit it to public repositories. Use environment-specific values and rotate tokens as needed.
Required environment variables:
- POEDITOR_API_TOKEN: Your POEditor API token Optional:
- POEDITOR_PROJECT_ID: Default project ID (can be overridden per tool call)
Troubleshooting tips
- Invalid API token or project ID
- Network access blocked to POEditor API
- Mismatched term context when updating translations
Examples of typical usage flows
Create new terms with translations in one operation to minimize round-trips.
Add translations for existing terms without overwriting existing values unless you explicitly want to update them.
Available tools
add_terms_with_translations
Create multiple new terms and add their translations in one operation
add_translations
Add translations for existing terms (does not overwrite)
update_translations
Update/overwrite existing translations
list_terms
List all terms (with optional translations)
project_details
View project metadata (name, counts, last activity)
delete_terms
Remove one or more terms by term/context
update_terms
Update term metadata (rename, change context, references, tags)
delete_translations
Remove translations for specific term/context pairs
list_languages
List languages currently enabled in a project
list_available_languages
List all languages that POEditor supports
add_language
Add a new language to the project