MCP Integration

Loxily MCP (Model Context Protocol) service wraps the Open Platform REST endpoints into tools that AI agents can call directly. Popular AI clients — Cursor, Claude Desktop, Cline — pick up the full task / terms / export toolset with a single mcp.json entry. No signing code needed.

• Service URL: https://mcp.loxily.com/mcp
• Transport: Streamable HTTP (MCP protocol version 2025-06-18)
• Auth: Bearer Token (shown in plaintext exactly once at generation time)
• Tools: 29 loxily_* tools, one-to-one with Open Platform REST endpoints

When to use MCP vs plain REST

Aspect	MCP	Plain Open Platform REST
Target user	AI agents, IDE assistants, automation scripts	Backend services, CI/CD, custom SDKs
Auth credential	Single Bearer <MCP Token>	X-Loxily-AppKey + X-Loxily-Timestamp + X-Loxily-Sign
Signing overhead	None (server signs for you)	MD5(timestamp + body + appSecret) per request
Call model	Natural language → LLM tool selection → typed args → execute	URL / body / signature by hand
Argument validation	Server-side Zod schemas, errors surfaced early	REST 422 only after the call
Typical scenarios	"Translate this batch of Chinese to ja/ko/en"	Batch scripts, CI integration, custom portals

Both paths hit the same project and the same data. MCP is a thin agent-friendly wrapper — it still uses the project's App Key / App Secret under the hood to sign downstream REST calls. You can use both.

Tool catalog (29 total)

Naming convention

All tools follow loxily_<domain>_<action> so LLMs can pattern-match reliably. Full inputSchema for each tool lives in the Open Platform API reference — MCP arguments mirror REST request bodies exactly.

Project & Languages (1)

• loxily_list_languages — Query project source language, enabled targets, full language tree

Task lifecycle (8)

• loxily_create_task — Create a translation task (async)
• loxily_query_task_status — Fetch task status and stage (single pull)
• loxily_wait_for_task — Server-side blocking poll until a terminal state (recommended for agents)
• loxily_query_task_strings — Paginated JSON query of a task's strings and translations (available as soon as the task is completed, no publish required)
• loxily_publish_task — Publish completed translations to the project level (async, returns a publish_open_... job_id)
• loxily_query_publish_status — Fetch publish status (single pull, see Query Publish Status)
• loxily_wait_for_publish — Blocking poll until the publish reaches a terminal state; wait for completed before exporting
• loxily_supplement_translate — Add / retranslate strings in an existing task

Task-level terms (4)

• loxily_query_task_terms — Query scanned terms
• loxily_update_task_term — Update a single task term
• loxily_delete_task_term — Delete a single task term
• loxily_confirm_terms — Confirm term choices and resume translation (when auto_apply_terms=false)

Project-level termbase (4)

• loxily_create_terms — Bulk upload project terms
• loxily_list_terms — List project terms
• loxily_batch_update_terms — Bulk update
• loxily_batch_delete_terms — Bulk delete

Translation memory (3)

• loxily_list_tm — Paginated query of project TM records (filter by source language / content / keyword)
• loxily_update_tm — Fix a TM translation (sync)
• loxily_delete_tm — Delete TM records (sync)

Export templates (5)

• loxily_list_export_templates — List templates
• loxily_get_export_template — Fetch a single template
• loxily_create_export_template — Create a template
• loxily_update_export_template — Update a template
• loxily_delete_export_template — Delete a template

Export & misc (4)

• loxily_export_ini — Export INI (or ZIP), returns a signed download URL; sync by default, async=true enqueues and returns a job_id immediately (recommended for large multi-language exports)
• loxily_query_export_status — Fetch async export progress / terminal state (single pull)
• loxily_wait_for_export — Blocking poll until an async export finishes, returns the download_url
• loxily_whats_new — Query platform release notes

Next steps

1. Quick Start — connect your MCP client in 3 minutes
2. Client Setup — Cursor / Claude Desktop / Cline / custom-client mcp.json snippets
3. Auth & Security — token lifecycle, rotate, revoke
4. Troubleshooting — 401 / 422 classification and signal reading