MCP server
LingoHub MCP by usefulapi
MCP server for LingoHub — localization projects, resources, exports and repository pushes.
- Runs
- Remotely
- Version
- 1.11.0
- Listing updated
- 4 days ago
About LingoHub MCP by usefulapi
LingoHub MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.
Install
Run in a terminal
claude mcp add --transport http lingohub https://lingohub.usefulapi.io/mcpAdd to Settings → Connectors → Add custom connector
https://lingohub.usefulapi.io/mcpInstall in CursorOpens Cursor, which asks you to confirm. Or add it by hand:
Add to ~/.cursor/mcp.json
{
"mcpServers": {
"lingohub": {
"url": "https://lingohub.usefulapi.io/mcp"
}
}
}Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:
Add to .vscode/mcp.json
{
"servers": {
"lingohub": {
"type": "http",
"url": "https://lingohub.usefulapi.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"lingohub": {
"serverUrl": "https://lingohub.usefulapi.io/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"lingohub": {
"type": "http",
"url": "https://lingohub.usefulapi.io/mcp"
}
}
}Tools this server provides (14)
Read directly from the server.
- lingohub_list_projects
- List every Lingohub project this API key can see (owned and shared, across workspaces). Each entry has the title, its links and the workspace_url + project_url slugs that every other tool needs. GET /v1/projects.
- lingohub_get_project
- One project: title, description, owner email, configured locales (project_locales), timestamps and links. GET /v1/{workspace_url}/projects/{project_url}.
- lingohub_get_project_status
- Translation status of one project: each resource file with per-locale segment counts (NOT_TRANSLATED, DRAFT, TRANSLATED, APPROVED, ...), failing quality checks, the export formats it supports and whether a Git repository is connected and can be pushed to. GET .../projects/{project_url}/status.
- lingohub_get_workspace_status
- Translation progress of every project in one workspace: title, app URL, total segment count and per-locale counts by status (NOT_TRANSLATED, DRAFT, TRANSLATED, PREFILLED, APPROVED). GET /v1/{workspace_url}/projects/status.
- lingohub_create_project
- WRITE: create a new localization project in a workspace (needs settings-management permission on the key). Returns the new project with its links. It adds a project and changes nothing existing; repeating the call can create a second project. POST /v1/{workspace_url}/projects.
- lingohub_list_resources
- List a project's resource files: name, locale and links (including a download link). GET .../projects/{project_url}/resources.
- lingohub_download_resource
- Download one resource file as text, in one language. file_name is the file name as list_resources shows it (the folder goes in `path`). Long files are cut at 40000 characters (truncated: true); use request_export for a full copy. GET .../projects/{project_url}/resources/{file_name}.
- lingohub_upload_resource_file
- WRITE: upload one text resource file (JSON, properties, XLIFF, PO, ...) into a project. The language comes from the file name or from `language`. The import flags decide whether existing segments are changed or deactivated: with updating or deactivation on, translations already in Lingohub can be overwritten or switched off, so state the flags you want. Never retried. POST .../projects/{project_ur
- lingohub_delete_resource
- WRITE, DESTRUCTIVE: delete a resource container: the source-language file AND all its target-language files with their translations. file_name and path must address the source-language file. This cannot be undone through the API. Never retried. DELETE .../projects/{project_url}/resources/{file_name}.
- lingohub_request_export
- Start an asynchronous export of a project's resource files as a ZIP. It creates an export job and changes no project data. Returns the export id; poll get_export until its status is SUCCESS to get the download URL. Without filters it exports every file and language. POST .../projects/{project_url}/exports.
- lingohub_get_export
- Status of an export started with request_export: overall and per-file status (NEW, SCHEDULED, PROCESSING, SUCCESS, SKIPPED, ERROR), error details and, when done, the pre-signed download URL of the ZIP. GET .../projects/{project_url}/exports/{export_id}.
- lingohub_list_context_images
- List the context images (screenshots that show translators where a text is used) of a project, with connected-segment counts and processing status. Paginated; page is zero-based. GET .../projects/{project_url}/contextImages.
- lingohub_delete_context_image
- WRITE, DESTRUCTIVE: delete one context image and its connections to text segments. Never retried. DELETE .../projects/{project_url}/contextImages/{image_id}.
- lingohub_push_to_repository
- WRITE: push the project's resource files to its linked Git repository (GitHub, GitLab, Bitbucket or Azure DevOps; the connection must already exist). Depending on push_type this commits to a branch or opens a pull request, so it changes the user's repository. Never retried. POST .../projects/{project_url}/push.
LingoHub MCP by usefulapi FAQ
How do I add LingoHub MCP by usefulapi to Claude Code?
Run this command in your terminal: claude mcp add --transport http lingohub https://lingohub.usefulapi.io/mcp