# PaperTiger for ChatGPT, Codex, and Claude PaperTiger provides a hosted MCP server and an installable plugin for designing, executing, and analyzing paper-trading experiments. Claude can connect to the same production server as a custom connector. Nothing runs on the user's computer. - MCP endpoint: `https://api.papertigerapp.com/mcp` - User installation guide: `https://papertigerapp.com/integrations` - OAuth authorization server: `https://api.papertigerapp.com/.well-known/oauth-authorization-server` - Protected-resource metadata: `https://api.papertigerapp.com/.well-known/oauth-protected-resource` - Scope: `papertiger:account` ## Authentication and authority Account linking uses OAuth 2.1 authorization code with PKCE S256. Access tokens are audience-bound to the hosted MCP resource, expire after one hour, and use rotating 30-day refresh-token families. Reuse of a consumed refresh token revokes its family. ChatGPT, Codex, and Claude register dedicated public clients through `POST /oauth/register`. PaperTiger advertises this dynamic registration endpoint in authorization-server metadata, permits HTTPS and loopback-HTTP callbacks, and requires `token_endpoint_auth_method: none` plus PKCE S256. Users enter their credentials only on PaperTiger's OAuth page; clients receive revocable tokens rather than passwords or PaperTiger API keys. The grant represents full authority over one PaperTiger account. It can read all virtual wallets, create, modify, reset, and destroy virtual wallets, place and cancel paper orders, and manage experiments. PaperTiger is simulation-only: none of these operations submits a real-money venue order. PaperTiger is for users aged 13 and older. Users under their local age of majority need permission from a parent or legal guardian. Registration records an explicit eligibility acknowledgement. The integration does not target children under 13 and must not be used to facilitate real-money gambling, investment execution, money or crypto transfers, or evasion of third-party access restrictions. Raw account API keys are not sent to ChatGPT, Codex, or Claude. The OAuth grant maps to the same account-level authority on the PaperTiger server. Reset and destroy tools require the exact wallet name as confirmation, and every MCP write is recorded in the server audit ledger. ## User installation ### ChatGPT and Codex PaperTiger's public Plugins Directory listing is pending OpenAI review. After publication: 1. In ChatGPT web, turn on Work and open Plugins. In the ChatGPT desktop app, use ChatGPT Work or Codex and open Plugins. 2. Search for PaperTiger, open its listing, and select the plus button. 3. Select Connect when prompted, sign in on PaperTiger's OAuth page, and approve the `papertiger:account` grant. 4. Start a new chat and ask for a PaperTiger outcome directly, or type `@` to select PaperTiger explicitly. The OpenAI plugin includes both this MCP connection and the bundled `papertiger-research` skill. ### Claude Claude Free, Pro, Max, Team, and Enterprise users can connect now. Free users are limited to one custom connector: 1. Free, Pro, and Max users open Customize, then Connectors. Team and Enterprise Owners or Primary Owners open Organization settings, then Connectors. 2. Individual users select `+`, then Add custom connector. Organization owners select Add, then Custom, then Web. Name it PaperTiger and enter `https://api.papertigerapp.com/mcp`. 3. Select Add, then Connect. Sign in on PaperTiger's OAuth page and approve the `papertiger:account` grant. 4. In a conversation, select `+`, open Connectors, and enable PaperTiger. Claude receives the same 24 MCP tools but not the OpenAI plugin's bundled research skill. The MCP server's safety instructions and tool annotations remain available to both clients. ## Tool groups - Orientation: capabilities and account context. - Discovery: live Polymarket and Kalshi search and exact URL resolution. - Accounts: create, update, reset, and destroy virtual wallets. - Experiments: hypotheses, immutable strategy versions, historical backtests, and managed forward-paper runs. - Run control: status, pause, resume, and stop. - Analysis: deterministic funnels, economics, comparisons, and reproducibility exports. - Paper brokerage: place and cancel simulated orders. The MCP tools intentionally expose user goals instead of mirroring every REST endpoint. Calculations such as fees, P&L, fill rate, and rejection funnels are performed by PaperTiger and returned as structured data. The complete 24-tool inventory, example prompts, safety guidance, and troubleshooting steps are maintained at `https://papertigerapp.com/integrations`. ## Managed forward-paper semantics The forward runner uses immutable V2 strategy versions and the same canonical paper brokerage as direct PaperTiger orders. It searches current rolling-market families, uses executable public books, enforces timing, score, freshness, depth, slippage, expected-net-edge, position, and exit gates, and records each causal decision stage. Current-book price, book/depth imbalance, and microprice signals are supported by the first managed engine. Signals that require authoritative continuous order-flow, public-trade, persistence, resilience, ephemeral-liquidity, or reference-price history abstain. Score-persistence, reference-agreement, ephemeral-liquidity, and nonzero execution-latency gates likewise fail closed until the managed worker has a durable continuous observation state. The runner never approximates them from midpoint or metadata. Those strategies remain fully supported by causal historical V2 backtests and externally hosted forward runs that ingest their own decision events. ## Example > Show my PaperTiger wallets. Create separate $1,000 wallets for two competing > BTC five-minute hypotheses, create immutable V2 strategy versions, backtest > both on the same complete causal window, and compare their rejection funnels > and net results. Do not start forward runs until I approve them.