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.

Install

The MCP server is shipped as @turaxia/mcp on npm. You do not need to clone the app repo.

{
  "mcpServers": {
    "turaxia": {
      "command": "npx",
      "args": ["-y", "@turaxia/mcp"],
      "env": { "TURAXIA_API_KEY": "${TURAXIA_KEY}" }
    }
  }
}

Put this in:

  • Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.
  • Cursor — settings panel → "MCP".
  • Zed — ~/.config/zed/settings.json → context_servers.
  • Any other MCP-capable client that supports the standard config shape.

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.

  • 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.

Beta modules (Studio, Flow, Intel) are available over MCP on Business and Enterprise plans. Private-alpha modules are offered through Enterprise engagements and are not exposed on the self-serve MCP 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.

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