Connect Tracker to Claude

East Agile Tracker ships a remote MCP server, so Claude can work your board directly: search stories, pick one up, move it through the state machine, comment with @-mentions — as you, with your own project memberships deciding what it can see and touch. You add it once as a connector; no API key to mint, copy, or store.

The connector URL is:

https://api.eastagiletracker.com/mcp

Connecting is a browser sign-in plus a consent screen. Claude never sees your password — it holds its own tokens, which you can revoke at any time from your account settings.

What you need

• A Tracker account — any member. Your existing sign-in works: password, TOTP, passkey, or GitHub/Google.
• A Claude client signed in to your Claude account — one of:
  • Claude.ai, Claude Desktop, or the Claude mobile app. You add the connector once in Claude.ai or Claude Desktop, and it is available in all three.
  • Claude Code.

Add the connector in Claude.ai and Claude Desktop

Tracker is listed in Claude’s connectors directory as East Agile Tracker, at claude.ai/directory/eastagiletracker.

1. Open the listing — follow that link, or open Customize → Connectors, choose Discover, and search for East Agile Tracker.
2. Check you have the right one: it is published by East Agile, listed as a community connector, and the page shows the connector URL https://api.eastagiletracker.com/mcp.
3. Choose Connect to Claude. A Tracker sign-in opens in the browser — authenticate the way you always do, second factor included.
4. Tracker shows a consent screen naming claude.ai as the requesting app. Choose Approve, and you land back in Claude with the connector connected.

The connector then appears in Claude Desktop and the Claude mobile app on the same Claude account; there is nothing to add again.

Adding it by URL instead. The directory listing and a custom connector point at the same server, so either route works. Choose Add in Customize → Connectors, enter a Name (for example East Agile Tracker) and the MCP server URL https://api.eastagiletracker.com/mcp — no OAuth client ID or secret is needed — then Continue and Connect. Sign-in and consent are the same as above.

Team and Enterprise plans. On a Claude Team or Enterprise organization, the connectors members can reach are controlled at the organization level, so an Owner may need to enable Tracker for the organization before it appears. Each member then connects and signs in with their own Tracker account, so every connection still acts as the member who approved it.

Add the connector in Claude Code

One command:

claude mcp add --transport http tracker https://api.eastagiletracker.com/mcp

The first use triggers a browser flow: /mcp in Claude Code opens a Tracker sign-in — authenticate the way you always do, the full login flow applies, second factor included. Tracker then shows a consent screen identifying the requesting app and what the connection grants: Claude acts as you, across the projects you are a member of. Choose Approve, and the session lands back in the terminal. Tokens are stored by Claude Code; nothing Tracker-related needs to go in your shell profile or a .env.

To connect a different Tracker account, revoke the connection first (below), then add the connector again.

What Claude can do

With the connector connected, Claude works within the projects you are a member of:

• Read — list your projects; search and open stories with their comments; look up epics, iterations and project members; open a story from a short link; list the comments that mention you.
• Write — create and edit stories, move them through their states, archive and restore them, add comments with @-mentions, add or remove story owners, and mark mentions as read.

Nothing on the connector hard-deletes data. Anything beyond these — bulk operations, settings, imports — stays in the app and the API.

Approvals

Claude runs reads directly. Tools that change your board ask for your approval before they run, unless you have allowed them in Claude’s connector settings.

Example prompts

• “What’s in the current iteration of Acme Checkout, and who owns each story?”
• “Turn these meeting notes into stories with estimates and labels.”
• “Summarize the open bugs labelled android and their latest comments.”
• “Start ‘Pay with Apple Pay’, assign it to me, and comment that I’m picking it up.”
• “Show the comments that mention me and mark them as read.”

Replace the project, label and story names with your own.

What the consent grants

Approving the consent screen gives Claude a member-scoped connection:

• It acts as you. Every story it creates, transition it makes, and comment it writes is attributed to your member identity, exactly as if you had done it in the app.
• Your roles decide what it can do. Authorization is per-project role, the same as the app and the API. A project you are not a member of does not exist to the connection — lookups return not-found, not permission-denied.
• It holds tokens, not your password. The connection runs on short-lived access tokens with a rotating refresh token — the same session machinery as a browser sign-in. Your password, second factor, and passkeys are never shared with Claude.

Revoke a connection

Account → Connected apps lists every app you have approved — when it was connected and when it was last used. Revoking a connection takes effect immediately: its tokens stop working on the next request, and Claude has to go through sign-in and consent again to reconnect.

Revoking the connection does not touch your other sessions or any API keys.

Connector or API key?

Both reach the same API with the same permissions model. The difference is who holds the credential:

• The connector is for interactive use — Claude acting as you in Claude.ai, Claude Desktop or Claude Code, with browser sign-in, consent, and one-click revocation. Prefer it whenever a human is in the loop.
• API keys (ea_user_…, ea_agent_…) are for headless automation — CI jobs, scripts, and long-running agents that cannot open a browser. Mint them under Account → API Keys (user keys) or Project Settings → Agents (agent keys); see the API Guide.

Troubleshooting

• The sign-in loops or the consent screen never appears — make sure you entered the connector URL exactly: https://api.eastagiletracker.com/mcp.
• Claude gets “not found” on a project you can open in the app — the connection was approved by a different Tracker account than the one you are thinking of. Check Account → Connected apps in the account that approved it, revoke, and reconnect as the right member.