GUIDE

Use EXIPRA from your AI tools

About this guide

Everything EXIPRA does is exposed as an API, operable from chat AIs and coding agents over MCP (Model Context Protocol). There are two ways in: chat AIs (Claude, ChatGPT) sign in with OAuth; development environments (Claude Code, Codex CLI, any stdio MCP client) use a connection key. Search and preview work without authentication on every path.

1. From Claude (claude.ai)

Open Claude settings → Connectors → "Add custom connector".
Enter https://exipra.com/api/mcp/mcp as the URL (leave Client ID / Secret empty).
Sign in to EXIPRA and approve the connection.
Ask things like "search EXIPRA for ..." — search, purchase and managing your own listings all work in chat.

2. From ChatGPT

Add a connector in ChatGPT developer mode (available on Plus and above).

Settings → Connectors → Advanced → enable Developer mode.
Create a connector with https://exipra.com/api/mcp/mcp (leave OAuth ID / Secret empty — registration is automatic).
Complete the EXIPRA sign-in and consent screen.

When EXIPRA adds or updates tools, an already-connected connector may keep its old tool list (the snapshot from connection time). If a new tool does not appear, refresh the connector or remove and re-add it. The same applies to Claude connectors.

3. From a development environment (MCP clients)

For Claude Code, Codex CLI or any stdio MCP client, use a connection key.

Issue a key on your account page (/me/keys). The key is shown once, and it acts as you. Keep it private; revoke it anytime.
Register the EXIPRA server with your client.

Claude Code (project .mcp.json):

{
  "mcpServers": {
    "exipra": {
      "command": "npx",
      "args": ["-y", "@exipra/mcp"],
      "env": {"EXIPRA_CONNECTION_KEY": "exipra_ck_..."}
    }
  }
}

Codex CLI (~/.codex/config.toml):

[mcp_servers.exipra]
command = "npx"
args = ["-y", "@exipra/mcp"]
env = { EXIPRA_CONNECTION_KEY = "exipra_ck_..." }
# only for non-interactive runs (codex exec):
# default_tools_approval_mode = "approve"

In Codex VS Code extension and Codex app sessions, EXIPRA is reached through the ChatGPT connector (the hosted variant from §2) — local stdio tools are not surfaced to the model (measured 2026-07-19). Judged publishing still works on this path: the hosted exipra_publish issues a short-lived publish bridge key and returns the publish-run commands (§5), which your agent executes on your own machine. On every path, the isolated judgment runs only on the seller's machine.

4. What you can do (tools)

Tool	Auth	What it does
exipra_search	none	Search designs by keyword, category, tags
exipra_preview	none	Public preview, sealed-content list, what-you-get manifest, price, rails
exipra_purchase	key	Request purchase; stripe/paypal return a checkout URL, the manual rail returns payment instructions
exipra_load	key	List purchases / load a granted document into context
exipra_status	key	Your listings and incoming transactions
exipra_update	key	Update listing metadata and the what-you-get manifest
exipra_withdraw	key	Withdraw a listing (existing buyers keep access)
exipra_publish	key	Staged publish with the reproducibility check (below)

5. Judged publishing (exipra_publish)

A staged flow that verifies — with an isolated judge on your own machine — how much of the document can be disclosed without the implementation assets becoming reproducible.

Prerequisite: judging runs a headless claude CLI locally (it consumes your Claude subscription quota; there is no metered billing).
Flow: analyze (structure, manifest candidates, execution estimate) → judge (isolated judgment; roughly declared assets × 3 + 1 executions) → preview (see exactly what buyers will see) → commit (create, record the judgment, publish). Your agent walks you through a confirmation at each stage.
On hosts where stdio tools are not surfaced (Codex VS Code extension, Codex app), exipra_publish issues a publish bridge key (publish-only scope, valid 2 hours) and returns publish-run commands that execute the same staged flow locally — same confirmations, same badge conditions. Bridge keys are visible and revocable on /me/keys.
While the published disclosure matches the judged line, the listing shows the isolation-verified badge. The judgment is a snapshot by the judge model at judgment time.

6. Buying through an agent

Check the content and price via search/preview (you see the public part and the list of what stays protected).
Run purchase. Stripe/paypal rails return a checkout URL to pay in the browser; the manual rail (bank transfer etc.) returns the seller's payment instructions — pay, then declare the payment on the transaction page.
Once the seller grants access, load pulls the full document into your agent's context. Load before grant is refused.

Payment always flows directly from buyer to seller. EXIPRA never holds funds.