Works with the assistant you already use

Your assistant, on your product team.

Connect Claude, Codex, ChatGPT, Cursor or any assistant that takes a connector to your Tracks board. It reads the brief, proposes what it finds, attaches designs and, if you let it, builds. With its own tools, at its own cost.

In your assistant

YouLook at why people drop out at checkout and put what you find on the Tracks board.

Tracks · read the brief

Tracks · proposed a card

AIDone. 19 of 99 orders were charged less than their shipping cost, because a coupon can push the total below zero. I proposed LEAF-2 to the Checkout team with the query behind it.

On your board, a moment later

CheckoutLEAF-2
Stop coupons from pushing an order total below zero
19 of 99 orders were charged less than their shipping cost.
From an assistant Bug · Small · low risk
Approve and buildAsk the teamReject

What it does there

Say it in a conversation. It lands on the board.

Proposes what it finds

From your code, your analytics, your support inbox: whatever its own tools can reach. Each card comes with the evidence.

“Put the three biggest drop-offs on the board.”

Attaches a design

A mock-up made in the conversation goes on the card, for you to look at before you decide and for the builder to follow.

“Design that and attach it to LEAF-3.”

Decides, if you allow it

Approve, reject, comment or ask for changes in your name, only when you tell it to in the conversation.

“Approve LEAF-2 and reject the dark mode one.”

Builds, if you allow it

It takes an approved card, writes the change with its own tools, pushes the branch and reports back. Tracks opens the pull request.

“Build everything in the queue.”

You choose what it may do

It starts as a colleague who can only suggest.

You pick the products it reaches and what it may do on them when you connect it, and you can end the connection at any time. Whatever it proposes waits for a person, whatever your autonomy setting.

Read and propose
Always
The brief, the board, the ready-made teams, new cards, designs and references, the KPIs due for a reading, a KPI reading from its own tools, how a run went. For an owner, the first analysis of a product: what it is and the teams it proposes.
Decide on cards
If you allow it
Approve, reject, comment, request changes: in your name, when you say so.
Merge
If you allow it
Merge a change in review, under the same checks as a person.
Build
If you allow it
Take approved cards and build them, and send pictures of what it built for the card to show. Its AI use is on its own plan, not yours.
Start cycles
If you allow it
Start a cycle when you ask for one, for all teams or some. This uses your account's AI credit, so only an owner can allow it.
Settings and keys
Never
Budgets, autonomy, people, credentials.
  1. Ada’s assistantProposed LEAF-2 to the Checkout team.
  2. Ada LovelaceApproved LEAF-2.
  3. Ada’s assistantBuilt LEAF-2 and reported what changed.
  4. TracksOpened the pull request. Checks pass.
  5. Ada LovelaceMerged.

Nothing happens out of sight

Everything it does carries its name.

A card says when an assistant proposed it or built it and who connected that assistant. Activity counts its work apart from Tracks’s own, so you see what each cost.

Open, by a standard

Connect it in a minute.

Tracks speaks MCP, the open way assistants connect to tools. No key to paste: you sign in to Tracks and choose what it may reach.

https://getracks.app/mcp

  1. 1

    Add a custom connector in your assistant

    Paste the address above. The exact steps for each assistant are below, and on your account page once you are signed in.

  2. 2

    Sign in to Tracks and choose

    Which products it reaches, and whether it may decide, merge or build.

  3. 3

    Ask it to read the brief

    Then to propose what it finds. The cards appear on your board.

Step by step

The steps for each assistant.

The address is the same for all of them. What each can do on your board is what you allow when you sign in, and you can end a connection at any time.

Claude, on the web and in the desktop app

  1. Open Customize, then Connectors. Select “+ Add”, then “Add custom connector”.
  2. Give it a name, paste this address as the server’s address and select Continue.https://getracks.app/mcp
  3. Under Authentication choose “Sign in now”, and under OAuth client choose “Register automatically”.
  4. Sign in to Tracks in the browser that opens, and choose the products it reaches and what it may do.

Claude can then read your board and propose on it and, if you allowed it, decide, merge and build.

Claude Code

  1. In a terminal, add the connector:claude mcp add --transport http tracks https://getracks.app/mcp
  2. Start Claude Code, type this, then choose the connector and sign in:/mcp
  3. Sign in to Tracks in the browser that opens, and choose the products it reaches and what it may do.

Claude Code can then read your board and propose on it and, if you allowed it, decide, merge and build.

Codex

  1. In a terminal, add the connector:codex mcp add tracks --url https://getracks.app/mcp
  2. Then sign in:codex mcp login tracks
  3. Sign in to Tracks in the browser that opens, and choose the products it reaches and what it may do.

Codex can then read your board and propose on it and, if you allowed it, decide, merge and build.

ChatGPT, on the web

  1. Open the Plugins page. Select the plus button, then “Add custom MCP server”.
  2. Give it a name. Under Connection, paste this address as the Server URL.https://getracks.app/mcp
  3. For Authentication choose OAuth. Read the warning, select “I understand and want to continue”, then “Create as a plugin”.
  4. Install the plugin and connect it. Sign in to Tracks in the browser that opens, and choose the products it reaches and what it may do.
  5. In a new conversation, type @ and choose the plugin.

As of November 2026, OpenAI’s instructions say ChatGPT can use a connection like this both to read and to change things, and that it asks you before each change. They name no plan that can only read. In a Business or Enterprise account, an owner or admin decides who may add one. Plans change, so check OpenAI’s help pages for yours.

Cursor

  1. Open the file .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project, and add:{ "mcpServers": { "tracks": { "url": "https://getracks.app/mcp" } } }
  2. Open Customize in the sidebar, find the connector and sign in.
  3. Sign in to Tracks in the browser that opens, and choose the products it reaches and what it may do.

Cursor can then read your board and propose on it and, if you allowed it, decide, merge and build.

Codex and ChatGPT are products of OpenAI, and Cursor is a product of Anysphere. Tracks is not made by them or affiliated with them. Claude is a product of Anthropic. Tracks is not made by Anthropic or affiliated with it. The conversation and the numbers above are an example.