trackmyprop docs
Workflows

AI connections

Connect a supported AI client to use your latest available trackmyprop data from anywhere, then disconnect it whenever you choose.

An AI connection lets a supported AI client read selected cloud-synced trackmyprop data so you can ask questions about your trading. The AI client runs the conversation; trackmyprop does not provide an AI chat inside the app.

AI connections are available only when your trackmyprop account and AI client support them. In the desktop app, open Settings → AI connections to copy the server address, review connected clients, inspect redacted recent activity, or revoke access. The account portal provides the same revoke control when you are away from the app.

What an AI connection can read

After you approve the connection, the client can use the trackmyprop tools it is allowed to use to read your cloud-synced trading records and analytics. This can include accounts, trades, challenges, expenses, payouts, journal data, and the results of supported exports.

The connection keeps working when the desktop app is closed or cloud sync is behind. It uses the newest records already available to trackmyprop and labels them as current, possibly stale, or unknown so your AI client can answer from anywhere without requiring you to open the desktop first.

Journey answers use trackmyprop's own definitions for currently funded, ever funded, funded accounts lost, active evaluations, passed evaluations awaiting a funded Account, and Phase progression. Supported clients can also request a private Prop Firm Journey card built from those same definitions.

Supported clients can also create a private ROI card. Its cash-basis ROI is calculated per currency from recorded payouts minus challenge fees, activation fees and expense entries, divided by those costs. Different currencies are never combined.

A challenge's activation fee counts as a cost once the challenge is funded (or was funded and then breached), dated with the challenge fee. The ROI card, economics, statements and transaction lists show it as an Activation fee row. When a challenge has no saved status, the AI connection decides it the way the app does: an instant challenge is funded; otherwise it is funded once its linked payouts cover its fee and linked expenses, even if that payout falls outside the period you asked about. Expenses linked to no challenge are left out of ROI and reported separately.

The connection is permanently read-only. It cannot create, edit, delete, archive, restore, sync, publish, revoke, connect, disconnect, place trades, copy trades, or change a broker or account. It also cannot access your broker passwords, broker sign-in tokens, API keys, or other connection secrets.

The AI provider may interpret the data and notes it receives. Read that provider's privacy terms before connecting, and only ask it to use data you are comfortable sharing under those terms.

The trackmyprop server address

Use this exact address for a remote, Streamable HTTP MCP connection:

https://api.trackmyprop.app/mcp

You can also copy this address from Settings → AI connections in the desktop app.

When the client opens the sign-in page, sign in to trackmyprop and approve the read-only request. Do not paste your trackmyprop password, broker credentials, or an access token into a client configuration field.

Before you choose Allow read-only access, check that the approval page names your client's site (claude.ai, claude.com, chatgpt.com or chat.openai.com) or says an app on this computer. If it shows another site with an Unverified app label and you didn't start that connection, choose Cancel. The page also shows the email you are signed in with; Not you? signs you out so you can switch accounts.

Connect your client

Client menus change over time. If a label below differs from what you see, look for that client's current custom connector, MCP server, or remote-tools setup.

Claude

  1. In Claude, open Customize and then Connectors.
  2. Add a custom web connector and enter the trackmyprop server address above.
  3. Complete the trackmyprop sign-in and read-only approval.
  4. Turn the connector on for the conversation where you want to use it.

On Claude Team and Enterprise plans, an owner may need to add the custom connector for the organization before members can connect it. Claude's availability and connector limits depend on your Claude plan.

ChatGPT

  1. In ChatGPT, check whether your workspace offers developer mode for custom MCP apps.
  2. Create a custom app, provide the trackmyprop server address, and select its authentication option when prompted.
  3. Scan the available tools, complete the trackmyprop sign-in and read-only approval, then save the app.
  4. Enable the app in a new chat before asking a trackmyprop question.

Custom MCP app availability, workspace controls, and menu names vary by ChatGPT plan. A workspace admin or owner may need to enable developer mode or approve the app first.

Codex

In the Codex desktop app or IDE extension, open Settings (or the gear menu), choose MCP servers, add a Streamable HTTP server, and enter the trackmyprop address. Save it, restart when Codex asks, then choose Authenticate to complete trackmyprop sign-in.

For Codex CLI, add this to ~/.codex/config.toml, then sign in:

[mcp_servers.trackmyprop]
url = "https://api.trackmyprop.app/mcp"
codex mcp login trackmyprop

You can check the connection later with codex mcp list.

MCP Inspector

MCP Inspector is a developer testing tool, not a trading workspace. Run it with:

npx @modelcontextprotocol/inspector

In its connection pane, select Streamable HTTP, enter the trackmyprop address, and connect. Complete trackmyprop sign-in when it is requested. Use the Tools tab to confirm the available read-only tools and try a narrow question.

Another compatible client

Choose a remote Streamable HTTP MCP server, enter the trackmyprop address, and complete its OAuth sign-in flow. If the client only supports a local server, a bearer token, or an older transport, it is not compatible with this connection.

Questions to try

Ask for an explanation grounded in the records, not a trading instruction. For example:

  • “Why am I losing money buying evaluations and receiving no payouts? Show the evaluation fees, recorded expenses, payouts, and the periods they cover.”
  • “Compare my profitable and losing trading days this month. What differs in the data?”
  • “Which challenges cost me the most, and which ones resulted in payouts?”
  • “Show the largest loss streak in my selected period and the trades included.”
  • “If private statement exports are available in this connection, create one for my own records.”
  • “Create a private share card for my latest available Prop Firm ROI.”

An answer can help you investigate patterns, but it is not financial advice and does not prove intent, psychology, or a rule violation.

How answers count money and days

  • Currency. Each account's synced currency is used when it has one. Money with no synced currency is shown in USD (the desktop default) unless you synced a currency preference, and answers label that assumption. Trades still in their quote currency are left out of totals.
  • Days. Days follow each account's trading day: the CME session (17:00 Chicago) for futures, the broker server day (UTC) for cTrader, and otherwise the calendar day in your timezone. The timezone comes from your app setting or your Mac's own zone, and falls back to UTC with a note saying so. Hour and session breakdowns use each trade's entry time.
  • Periods. Money for a date range counts each fee, activation fee, expense and payout on its own date, as the app does. A payout or expense in the period still belongs to its challenge's firm when the challenge fee was paid earlier. Transaction totals always equal the sum of all pages.
  • Archived accounts are hidden from account lists and freshness unless you ask for them. Their trades still count in analytics.
  • Breakdowns keep every account and every challenge separate, even when their names match. Identical challenges (same firm, size and type) are labelled with their purchase date, and with a number when bought the same day (for example "Apex · $50k · 2-step · 2026-03-05 #2"). Account numbers inside account labels are masked, for example "Match-Trader ••••4567".
  • Calendar cards show timed events in your timezone. Holidays and all-day events keep the date the calendar gives them and show All day. P&L calendar cards color every day that has trades, even an evening futures trade that already counts toward the next CME session, and future weekend days show as weekends.

Freshness and missing data

AI connections use the latest cloud copy already available, so they keep working even when the desktop is closed or sync is behind. Every result includes freshness details, taken from the newest complete sync your desktop confirmed: current means confirmed within the last 30 minutes, unknown means the desktop has not confirmed a complete sync, and anything older is possibly stale. The client should answer from those records and describe them as the latest available snapshot when freshness is possibly stale or unknown.

If you specifically need activity that happened after the time shown in the freshness details:

  1. Open trackmyprop on the computer that has the newest records.
  2. Let cloud sync finish. If you also need new broker activity, refresh the broker connection first.
  3. Ask the client again and check the updated freshness time.

Old or incomplete sync does not disable the connection, analytics, exports, or share cards. When no matching records are available, the client should say that plainly instead of turning missing data into zero.

If an expected record is missing, confirm that it appears in the desktop app and has had time to sync. Some data stays on your computer by design, including broker credentials, raw import files, and certificate images.

If a payout, fee, or expense record has an invalid amount, trackmyprop still reports the exact number and type of recorded transaction entries, but marks every affected monetary total and calculation as incomplete. The AI client should explain which records were excluded instead of treating their amounts as zero or presenting a final net result or ROI. Correct the affected records in the desktop app, let cloud sync finish, and ask again.

If your client's tool list offers an export or private share card, its result is private and temporary. It is not published or saved as a public link unless you or the AI client save a copy.

Existing public verification links are different. The connection can read an existing link when supported, but it cannot create, extend, refresh, publish, or revoke one.

Revoke or disconnect

To stop future access from trackmyprop:

  1. In the desktop app, open Settings → AI connections.
  2. Find the AI client under Connected clients.
  3. Select Revoke and confirm.

If you cannot open the desktop app, use trackmyprop.app/portal#ai-connections and revoke the client there instead.

Revocation takes effect before the next request. Also remove or disconnect the server in the AI client. Removing it there stops that client from trying to use the connection; revoking it in trackmyprop is the account-level control.

The desktop activity list shows only the tool name, outcome, and time from the last 90 days. It never shows prompts or result contents.

Troubleshooting

authentication_required

The client is not signed in, its approval expired, or it cannot finish the sign-in window. Start the connection again, complete trackmyprop sign-in in the browser, and retry. If you recently revoked the connection, add and approve it again only if you want to restore access.

The approval page says your session ended or the request expired

If your trackmyprop session ends on the approval page, Sign in again brings you back to the same request. A request expires after about 10 minutes; start the connection again from the client.

entitlement_required

Your current trackmyprop access does not include AI connections. Check the account portal for your subscription status, then retry after eligible access is active. Admin Access is also eligible when this feature is available.

Data is stale or missing

The connection still answers from the latest records it has and shows their freshness. Refresh the desktop and let cloud sync finish only when you know newer activity is missing.

result_too_large

A request that would read more than 50,000 cloud records fails with result_too_large instead of answering from part of your data. Retrying or narrowing the question does not help, because the limit applies before any filter. Contact support if you see it.

The client cannot use a result

Some clients do not support every kind of file, image, or private link returned by an MCP server. Ask the same question for a simpler result, retry an export as a link if the client offers that choice, or use another compatible client. If the client cannot connect at all, confirm that it supports remote Streamable HTTP servers with OAuth.

On this page