The tracker your agent works.

Not a board you drag cards across. Your AI files the bug, claims the next task, does it, and closes it — and you read the same board, triage what it flags, and say what's next. Seventeen tools, one work loop.

$15 a month, and it isn't just this app — every Parsons product is on the same subscription. Cancel any time. Nothing is purged without a confirm, and an intake key can only write, so the people who report in can't read your board.

Works with ClaudeChatGPTCursorthe built-in chat
A real project. The console, on a phone.
tracker.parsons.ai
The Tracker dashboard: 325 open, 274 backlog, 1 in progress, 56 needing attention; created-vs-completed over 30 days; load by project; lead time 1.4 days.
The console, for when you want to look. Dashboard, projects, items, intake keys — with chat built in. Every button on it is also a tool your AI can call.
How it works

File it. Claim it. Close it. Read the board.

01

Make a project.

PLAT, SITE, CLIENT-A — a key, a name, and the statuses you want. Your AI can make it too.

Start a project for the website relaunch, key SITE.
Projects 3
PLPLAT · platform325 open
SISITE · website relaunch12 open
CACLIENT-A4 open
10,000 live rows included, account-wide
02

Paste one link into your AI.

Your account comes with one private address. Paste it into Claude, ChatGPT or Cursor once, and Tracker's tools are there. No AI of your own? The console has chat built in.

Your connection MCP Hub
https://mcp-hub.parsons.ai/p/prof_••••••••/mcp
ClaudeChatGPTCursorany MCP client
Paste it once. Tools you haven't granted aren't there.
03

Let the agent work the loop.

next_work hands your AI the highest-priority unblocked item and claims it. It does the work, comments, and closes — then asks for the next one. Two agents never take the same task.

Work the SITE backlog until it's empty.
Tool calls your AI · running
next_workSITE · claim_firstSITE-18 claimed
commentfix summary, 3 linesdone
resolveSITE-18 → donedone
next_workSITESITE-19 claimed
Four items an hour. You read the comments.
04

Let people report in.

An intake key is write-only. Put it in a form, a bot, an email rule — reports land in the backlog, deduped, and the reporter never sees your board.

Give the support form an intake key for CLIENT-A.
Intake keys
IKsupport form · CLIENT-Awrite-only6 today
IKSlack bot · PLATwrite-only2 today
Duplicates are merged before they count.
What you get

A work loop, a board, and a door for reports.

PPLAT-311 · triageP1
PPLAT-309 · todoP2
SSITE-19 · claimed by AIP2
01

Items with priority, status and an owner

Bugs, features, chores. Priorities that mean something because the agent works them in order.

Lead time
1.4d
created → done · 30 days · 39d 90th
02

A dashboard that tells the truth

Created vs completed, load by project, lead time. The numbers an agent-run backlog actually produces.

next_workPLAT · claim_firstPLAT-311
resolvePLAT-311done
03

The claim loop

next_work returns one item and claims it. Two agents reading the same list never collide. A file can't do that.

What's blocked, and by what?
Two items. SITE-14 waits on the DNS cutover (PLAT-290), SITE-16 on the logo files — I've asked in the CLIENT-A thread.
04

Ask the board

Blocked, stale, overdue, who's on what — answered from the rows, not from a saved filter.

IKsupport@ form6 / day
IKin-app report2 / day
05

Intake keys

Write-only keys for the people and bots that report. They can file; they can't read.

purge_taskSITE-3 · without confirmrefused
purge_taskconfirm: truegone
06

Delete is one step harder

resolve is easy. purge needs a confirm. An agent can't clear a backlog by misreading you.

What it can't do

It works your backlog. It cannot pretend it did.

  • ×Purge anything without a confirmpurge_task refuses on the first call. The second call has to say confirm: true.
  • ×Let an intake key read the boardIntake keys are write-only by construction. A leaked key can file spam; it cannot see a row.
  • ×Give two agents the same itemnext_work claims atomically. The second caller gets the next one.
  • ✓File, triage, claim, comment, resolve — as your AI or as you
  • ✓Read every project, every item, every comment
  • ✓Hand out and revoke intake keys
Your AIasks for work
Trackerclaims one item
The boardyou read the same rows
× intake key reads the board · no path from here
What we holdYour items and comments, per project. 10,000 live rows included, counted account-wide.
What can change a rowA member, or an AI with a granted profile. Every change carries who and when.
What leaving doesExport is a call. Delete a project and its rows go with it — after a confirm.

There is no security slogan on this page and no badge we haven't earned. Everything in that list is a thing you can check; the full mechanism and every tool are on the details page.

Pricing

Fifteen dollars a month — and it isn't just this app.

Parsons Cloudmonthly
Every product, one login15.00
Tracker · projects, items, intake0.00
Tool calls in your own AI uncapped0.00
10,000 live rows account-wide0.00
Projects unlimited0.00
Seats nobody is billed as one0.00
Total$15.00/mo
or $150 a year — two months free
Start your 14-day trial
Card at checkout · cancel any time · no free tier

Is it worth it? Start where we look worst.

One person, one tracker, no agent: a single seat elsewhere is cheaper than our $15. Here are the published seat prices.

Linear Basic · per seat$8 / mo
Jira Standard · per seat$7.53 / mo
Asana Starter · per seat$10.99 / mo
Parsons — every product$15 / mo

Ours is $15 for the whole account, with agents and people both uncounted, and the same $15 runs CRM, Email, Deploy and the rest. Add a second person and the seat lines above double; ours doesn't. And there is no free tier because a tracker that sells your usage is a tracker you'll leave.

Make a project, hand it to your agent, and read the board tomorrow.