← Back to TP1

DocsStats

Connect TP1 to Claude

Let Claude read the same statistics the Stats pages show, with a key you can revoke at any time.

Connect TP1 to Claude (Connect to Claude in the Stats side panel) sets up a connector so Claude can read the same statistics the pages show, with the count and window on every number, and your own Journal trades. No market prices, levels or forecasts. One key, one URL, and you can revoke the key any time.

Create a key

  • Give it a Key name (it starts as “Claude”).
  • Tick can upload signal sets only if you want Claude to upload signal sets for you.
  • Hit Create key. The key is shown once, with the Claude Code command and the URL form already filled in. Copy them then.
  • Your keys lists your active keys with when each was created and last used. Revoke stops anything using a key within a minute.

You can have 5 active keys; try a sixth and you'll see “You have 5 active keys; revoke one to create another.” Each key gets 60 calls a minute and 5,000 a day, and the page shows your tool calls over the last 30 days.

Set it up

Most people don't need a key. In Claude, TP1 is in the connector directory: go to Customize, Connectors, Browse connectors, search for Taking Prophets and connect. ChatGPT isn't in its directory yet, so add https://www.takingprophets.com/api/mcp as a custom connector with OAuth. Both sign in with your TP1 account; the TP1 connector page has the full steps.

For a key, the page shows three ways in:

  1. Claude Code. In a terminal, run claude mcp add --transport http tp1-stats https://www.takingprophets.com/api/mcp --header "Authorization: Bearer <your key>". Then ask something like “how often does NQ fill the gap on Fridays?” The page also links a skill file that teaches Claude Code the tools and the sample floors. Save it as .claude/skills/tp1-stats/SKILL.md.
  2. Claude Desktop and claude.ai, with a key. Go to Customize, Connectors, add a custom connector, and paste the URL form of your key. There's no OAuth step.
  3. Any other MCP client. Streamable HTTP at the same address, with an Authorization: Bearer <key> header. It's POST only, with JSON responses and no event stream.

What Claude can see

  • The reports and their rows, Discover, the weekly digest, the bias scorecard, and signal sets and their results.
  • Your own Journal: your trades one by one, as you logged them (including your entry and exit prices and your notes), your trades split with and against the bias call, your patterns, and your odds. The tools that do this read only the Journal of the member whose key is used.
  • Every result ends with the count, the window, the method version and the disclaimer. No market prices, levels, bars or live data go out through the connector, and nothing is a forecast or advice.