Skip to content

Trade PrimeDelta from an AI assistant

PrimeDelta ships three ways to trade the exchange programmatically: a Claude Desktop plugin for point-and-click agentic trading, a Python SDK to build on, and a self-hostable MCP server you run yourself. They share one core, so a guardrail you learn in one holds in the others.

This moves real funds

Every write tool signs an on-chain or brokerage transaction with your key — PrimeDelta never holds it. The assistant proposes; the signing mode and the off-assistant spend caps decide what it can actually do. Read Risk & responsible use before you connect a funded account.

  • Trade in Claude Desktop

    Install the .mcpb plugin, pick a signing mode, and place your first trade.

    Plugin quickstart

  • Build with the SDK

    pip install the SDK, log in, and script quotes, swaps, orders, and liquidity.

    SDK quickstart

  • Self-host the MCP

    Run the server behind your own KMS and connect Claude web or any MCP client.

    Self-host quickstart

What's under the hood

  • Signing modes — browser, execute (server-side KMS/private key), and craft-only. The mode is the boundary of what the assistant can do without you.
  • Guardrails — per-trade and daily spend caps enforced off the assistant, plus opt-in gates for deposits, withdrawals, orders, and subaccounts.
  • Reference — the tool list, plugin config, and SDK API are generated from the code itself, so they can't drift.

Reference

  • MCP tools

    Every tool the server exposes, with its spend gate — generated from the running server.

    Tool reference

  • Plugin config

    Every field in the Claude Desktop extension — generated from the .mcpb manifest.

    Plugin config

  • SDK API

    The Python client, signers, and parameter types — generated from the docstrings.

    SDK reference