TURAXIA

Docs · mcp

MCP

How to wire Turaxia as an MCP server into Claude Desktop, Cursor, Zed, or any MCP-capable client — with scoped keys and typed tool contracts.

Turaxia is MCP-native. Every GA module exposes the same primitive you call over REST as a typed MCP tool, with Connect managing the workspace-level scoping underneath.

Remote surfaces

Turaxia currently ships remote MCP endpoints over HTTPS, not a local @turaxia/mcp package.

Current MCP surfaces:

  • https://api.turaxia.com/mcp — authenticated remote MCP for workspace-scoped Turaxia primitives.
  • https://api.turaxia.com/public/mcp — public-safe remote MCP with one anonymous draft-bundle tool for controlled demos and connector distribution.

The public-safe server is also published in the official MCP Registry as com.turaxia/connect:

Use the config or connector flow your MCP host expects for a remote Streamable HTTP server. A common JSON shape looks like this:

{
  "mcpServers": {
    "turaxia": {
      "url": "https://api.turaxia.com/mcp",
      "headers": {
        "Authorization": "Bearer ${TURAXIA_KEY}"
      }
    }
  }
}

Some hosts use a UI instead of a JSON file. In those cases, enter the same remote MCP URL and the same bearer token there instead.

Common entry points:

  • Claude Desktop — remote MCP settings or config file, depending on the current client release.
  • Cursor — settings panel → "MCP".
  • Zed — remote context server settings.
  • ChatGPT Developer Mode — connector flow under Settings → Apps & Connectors.

Restart the client. The Turaxia tools will show up under the turaxia namespace.

Tools

Every tool below is typed end-to-end. Inputs are validated server-side; outputs are structured JSON.

  • Authenticated /mcp surface:
    • turaxia.parse — supplier URL or raw HTML → typed product record with per-field confidence.
    • turaxia.localize — typed product record + target locale → translated, glossary-consistent copy.
    • turaxia.price.quote — typed record + destination country → landed-cost quote.
    • turaxia.route.resolve — typed record + destination → carrier + package plan.
    • turaxia.connect.workspace.bootstrap — create or refresh a workspace, service account, API key, webhook.
    • turaxia.console.bootstrap — issue a deterministic dashboard bootstrap for an operator handoff.
  • Public-safe /public/mcp surface:
    • build_turaxia_draft_bundle — one approved supplier URL in, one localized Turaxia draft bundle plus Shopify-ready draft payload out.

Beta modules (Studio, Flow, Intel) remain plan-gated on the authenticated surface. Private-alpha modules are offered through Enterprise engagements and are not exposed on the public-safe server.

Scoping and safety

  • API keys are workspace-scoped via Connect. The MCP surface never gets a broader grant than the underlying API key.
  • Audit events are emitted for every tool call. They are visible on the dashboard and in the REST /audit endpoint.
  • The retry path has no paid-provider dependency — see the retry card in the proof bundle.
  • The anonymous public surface stays intentionally narrow and allowlisted. It is for controlled discovery and connector setup, not for broad unauthenticated access to the full Turaxia control plane.
  • Registry and connector discovery metadata are public:
    • https://api.turaxia.com/.well-known/mcp/server-card.json
    • https://api.turaxia.com/.well-known/glama.json

What this is not

  • Turaxia's MCP server is not a "buying agent". It is a substrate layer. The agent keeps all reasoning; Turaxia ships typed primitives.
  • Turaxia's MCP server does not ship convenience wrappers that hide multi-primitive choices. If you want "parse then price then route" as a macro, compose it in the agent or use Flow (Beta).
← All docs