Quick Start

Three steps to full MCP integration: generate credentials in Open Platform → write mcp.json → restart the client.

Prerequisite: enable Open Platform for the project

MCP Token is only the "entry credential". The server still needs the project's App Key / App Secret to sign downstream REST calls. If the project has never enabled Open Platform, every MCP call returns 401 Invalid token (the message is misleading — the real cause is the missing App Key / App Secret).

Open the console → target project → Open Platform, and verify that App Key / App Secret are already generated. First-time users click "Generate App Secret".

Order matters

You can generate the MCP Token first, but as long as either credential is missing, MCP will 401. Recommendation: generate both in the same session.

Step 1: generate an MCP Token

On the same Open Platform page, scroll to the AI Agent Access card and click Generate MCP Token.

The plaintext token (lox_mcp_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX) is shown exactly once — closing the dialog makes it unrecoverable. The page also provides a copy-ready mcp.json snippet.

Token handling rules

• The plaintext is shown only this once — closing the dialog makes it unrecoverable; save it into your secret store immediately
• Console Reset / Revoke takes effect on the very next request (returns 401) — no cache, no transition window
• Lost or leaked? Click Reset MCP Token to issue a new one (the old one dies immediately)

Step 2: write mcp.json

The console provides a snippet like this (the Bearer value is your token):

{
  "mcpServers": {
    "loxily": {
      "url": "https://mcp.loxily.com/mcp",
      "headers": {
        "Authorization": "Bearer lox_mcp_XXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
  }
}

Paste or merge this into your MCP client's config file (per-client paths on the Client Setup page).

Step 3: restart the client

After restarting Cursor / Claude Desktop / Cline etc., the tool list should show 21 loxily_* tools (loxily_list_languages, loxily_create_task, ...).

First call: validate the pipeline

Recommended first call: loxily_list_languages (zero arguments, read-only, idempotent):

> List the target languages supported by this project.

Expected: the tool returns project_id / source_language / target_languages. Success means the full pipeline MCP client → mcp.loxily.com → project credential lookup → downstream REST signing → Open Platform is working end-to-end.

If it fails, use the error message to locate the fix in Troubleshooting.

Recommended first business flow

1. loxily_list_languages — fetch the project's enabled target_languages (avoid 422 for unsupported languages in the next step)
2. loxily_create_task — create a task (strings for inline string array, or xlsx_url for a public URL)
3. loxily_wait_for_task — server-side blocking poll until completed / failed / waiting_confirmation
4. If auto_apply_terms=false: loxily_query_task_terms → adjust → loxily_confirm_terms to resume
5. loxily_publish_task — publish to CDN, or loxily_export_ini to download INI/ZIP

One natural-language prompt is enough — the agent will chain these tools on its own.