TotersLokalise MCP Server
Related Servers
Alternatives to TotersLokalise MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to query and edit translation projects, files, strings, terms, tasks, and collaboration data through stdio, with role-checked write operations.547 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through a hosted OAuth endpoint or a local stdio package, and to generate MCP tools from OpenAPI specs.2,530 npmMIT
- AlicenseBqualityBmaintenanceEnables MCP clients such as Claude and Cursor to invoke one tool per API operation for campaign management, audience import/export, conversation replies, account login jobs, and media uploads with scoped authentication.49MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude, Cursor, and VS Code to delegate coding tasks to OpenCode, including asking questions, implementing features, monitoring background work, handling prompts and permissions, and reviewing changes across projects.22,181 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to discover and execute hosted project-management tools through one PipMCP API key, including reading work items and applying explicitly approved changes under policy controls.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to review deployments and create approved projects on the connected provider through one PipMCP API key, with hosted schemas, policy approvals, and governed execution.MIT
TDQS
Scored across 9 tools
The import cluster (analyze_import, get_import_session, list_import_items, proceed_import, cancel_import) has clearly separated roles described in lifecycle terms, and create_keys is distinct as the only key-writing tool. The only real overlap is export_translations vs export_files, which both read translations but differ in output form (raw data vs app-ready files).
Every tool uses the same toterslokalise_ namespace prefix followed by a snake_case verb_noun pattern (list_projects, export_files, analyze_import, proceed_import, cancel_import). No mixed casing or inconsistent verb styles.
Nine tools sit in the well-scoped 3-15 range and each maps to a real step: project discovery, two export paths, a multi-step import workflow, key creation, and import cancellation. Nothing appears redundant or padding.
Read/export and import workflows are well covered, but the write surface is thin: there is no update of existing translation text (only create_keys with an overwrite flag) and no delete of keys or translations, which are core operations in a translation-management domain. Listing languages/environments or project metadata is also absent, leaving agents with dead ends for common edits.