Connect Your Trading Journal to Any Agent (MCP)

A trading journal MCP connection lets an agent read the journal you already keep and write back into it. You do not export a CSV every time you want a second opinion on last week’s trades.

VeloTape exposes that connection at https://velotape.com/api/mcp. You create a key in Settings. The agent sends it as Authorization: Bearer vt_live_…. The key is shown once. Revoke it in the same screen if you pasted it into the wrong chat.

The product page is /mcp. The habit underneath is still how to keep a trading journal: log the trade, tag the setup, review on a calendar. The agent is a faster way to do those steps, not a replacement for them.

What the agent can do

It can list and update your accounts, trades, tags, playbooks, and notebook entries. It can create a trade from executions, replace notes, set a 1–5 rating, and assign a playbook. It can add a Prop Desk event you already decided to log: payout requested, payout received, account blown, reset purchased, or a note.

Analytics are the same closed-trade overview you see in the app: net P&L, win rate, and profit factor. Prop Desk gauges are closed-trade compliance against the rules you stored. They are not live mark-to-market, and they do not block orders at the broker.

Screenshots are explicit. A list returns file name, type, and size. The agent downloads pixels only when it calls the read tool. An upload checks the file type (PNG, JPEG, or WebP), the 10 MB per-file cap, and the storage left on your plan.

What it cannot do

The key cannot read another user’s journal, broker passwords, SnapTrade tokens, or billing. It cannot run Coach AI, so it does not spend AI credits. It cannot bulk-import a CSV. It cannot mark an evaluation as funded — that transition stays in the app.

If the agent asks for a broker password, refuse. The journal never needs it for MCP.

Free plan, with caps

MCP is on Free, Essential, and Pro. The caps exist so a loop cannot page your whole history or pull every screenshot in one afternoon.

A write counts as a call and as a write. A screenshot read counts against the read cap. A prepare-upload counts against the upload cap. There is also a short burst limit (10 / 60 / 120 requests per minute). When a cap is hit, the tool returns an error the agent can read. It does not silently keep going.

Page size is capped too (50 / 100 / 200). Ask for the next cursor instead of one giant list.

Connect Cursor or Claude Code

1. Open Settings → Agents and create a key. Name it after the app (Cursor).
2. Copy the secret immediately.
3. Add this server. Replace the token with yours.

{
  "mcpServers": {
    "velotape": {
      "url": "https://velotape.com/api/mcp",
      "headers": {
        "Authorization": "Bearer vt_live_..."
      }
    }
  }
}

That is the whole install. No plugin. Claude on the web can paste the same header only on plans that allow a custom connector. ChatGPT’s sign-in flow wants OAuth, which this version does not speak yet. Use Cursor or Claude Code until that ships.

Then give the agent a narrow job: “List last week’s trades, tag the ones without a setup, and stop.” Check Settings for today’s usage if a run feels large. The numbers there are the same caps as the table above.

If you are starting from an empty journal, use the free trading journal guide first, then point the agent at the account you created. More questions live in the trading journal FAQ.

Create a free account and issue one key. Revoke it the moment you do not recognize a client.