All servers / Productivity / Progressor MCP server
Progressor MCP server
An MCP server that keeps an AI Agent and the Developer focused on their Goals across context compression and distractions.
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 1.4.0. Package: progressor-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.3 seconds including download)
- Tools offered: 31
- Last published: 2026-11-17
- Weekly downloads (npm): 567
- License: PolyForm-Noncommercial-1.0.0 · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_status3 of 3 parameters describedCompact summary of every Goal this Session holds (current Task, open Detour, Tasks with a helper or waiting on the Developer, next Task, decisions and open notes) and the Developer's Standing Instructions. Call it at the start of every conversation and after context compression. With project, another project's Goals and Tasks instead, to change them from here. With for_helper, only the Developer's rules as a block to paste into the brief of a helper agent you start (helpers don't see the Standing Instructions, so include it whenever you brief one).
get_item2 of 2 parameters describedLook up one Goal, Task, Detour, decision, note or Standing Instruction by its ref (progressor://<goal>/<item>, or progressor://roadmap/<instruction>), with its file and line. Use it when the Developer pastes a ref or you need one item's details; for where the work stands overall, use get_status.
add_goal12 of 13 parameters describedAdd a Goal to the end of the Roadmap, with an optional Task list and Outcome; with claim: true, also claim it to start work. A title another Goal already has is refused unless allow_duplicate is set. To record work already finished, set done on the Goal and on every Task. Plan each Goal with an Outcome (one sentence on what done looks like) and Tasks that each have a short title, the files they touch, a one-line summary and an estimate. Tell the Developer the plan in a few plain lines first. With claim: true the answer is the whole status.
add_hotfix4 of 4 parameters describedAdd a hotfix: a bug the Developer wants fixed before any other work, often from a customer report. Pass the report word for word. It goes at the top of the Roadmap with two Tasks (a test that shows the bug, then the fix), and every Session is told it is waiting until one claims it. With claim: true, claim it now; otherwise finish the step you are on first, then claim it.
update_goal7 of 7 parameters describedRename a Goal, set its Outcome or its estimate, or mark it needed for the launch (for_launch). Its ID, refs and Plan File stay the same, and it needs no Claim. To change a Goal's Tasks, claim it and use add_tasks, update_task or update_tasks.
launch_readiness1 of 1 parameter describedAnswer 'are we ready to launch?': what still stands before the launch or the next release, grouped by who it waits on (you, the Developer, other people), with serious risks nothing is reducing. It is the same summary as the dashboard's Ready to launch? page, so answer from it. It counts the next open release goal and what it bundles, else the goals marked for launch (update_goal for_launch), else every open goal.
move_goal4 of 4 parameters describedMove a Goal right before or after another Goal, so the Roadmap lists the work in the order it should happen. Give exactly one of before and after. The dashboard lists the Goals that need the Developer (things to try, steps to check, questions) in this order too, so put the one they should check first in front.
drop_goal3 of 3 parameters describedDrop a Goal that will not be done, with the reason; its Plan File stays as a record. Releases this Session's Claim on it. A Goal another running Session holds, or one already done, cannot be dropped. To drop a single Task, use update_tasks (action drop).
claim_goal2 of 2 parameters describedClaim a Goal for this Session, so only this Session works on it. The Session keeps any other Goals it holds; while it holds several, pass goal to the tools that change one. Fails if another running Session holds it. Claiming a done Goal reopens it: its finished Tasks stay done, and add_tasks adds the new work to the same list.
resource7 of 7 parameters describedA named shared resource that only one session or helper can use at a time (a dev window that allows a single instance, plasmashell, a port). claim it before you or a helper start something that needs it: refused, saying who holds it, since when and why, when someone else has it; then do not start it, do other work and try again later (nothing waits for you). Claiming your own again refreshes its time. It frees itself after `minutes` (30 unless given, at most 240) from the last claim, when its Session ends, or when you release it. A helper usually cannot call Progressor: claim on its behalf with label such as 'helper: media run'. release it as soon as the work that needed it ends (a helper's too), with the same label; another holder's is refused unless force, only when the Developer says the holder is gone. list says who holds what (get_status shows the same).
release_goal1 of 1 parameter describedRelease this Session's Claim on a Goal, leaving it paused for a later Session.
complete_goal3 of 3 parameters describedMark the claimed Goal done and release it, once its Outcome is true and its Tasks are done, released or dropped (not with a helper, waiting on the Developer or only checked). While the Developer still has hand tests (save_hand_test) to mark, the Goal is released as built and waiting on their tests instead: it finishes by itself when they mark the last one, and a failure reopens it with a new Task. unmarked_hand_tests_ok finishes it now, only when the Developer says to finish anyway. If more work turns up later, claim_goal reopens it.
add_tasks2 of 3 parameters describedAppend Tasks to the claimed Goal's plan, each with an estimate of how long it takes. For work that is not part of the plan, declare a Detour instead. Set done on a Task that is already finished: a small change you have made is recorded in this one call, with hand_test for what the Developer should try. A quick fix that belongs to no Goal goes under Small fixes with add_small_fix instead.
add_small_fix5 of 5 parameters describedRecord a small one-off fix you have made that belongs to no Goal (a dev-server speed-up, a typo, formatting) as a finished step of the project's standing Small fixes goal, made the first time. Nothing is claimed and the Goals you hold are untouched. hand_test adds what the Developer should try. For work that is part of a Goal, use add_tasks with done: true instead.
save_risk9 of 9 parameters describedAdd a risk to the project's risks list: something that could go wrong, how likely and how bad, what would reduce it, who owns it and the goals that reduce it. Add the ones you notice as you work, without being asked; the Developer sees the list on the dashboard. With risk (its ID): change any of its fields, or its status (reduced once the work that lowers it is done, closed when it can no longer happen). Keep the list true as goals finish.
set_task_state10 of 11 parameters describedSet a Task's state. 'with a helper': handed to a helper agent that is working on it (several Tasks can be). 'waiting on you': you are waiting on the Developer, such as for them to test something by hand; the dashboard shows the Goal as waiting on them, so tell them what you need. 'waiting on someone': waiting on a person other than the Developer (a team member, a lawyer, a provider): give person and need; it is shown apart from what waits on the Developer. 'checked': you checked a helper's work (tests, review) but it is not merged or released yet; give evidence, one short line on what you checked ("715 passed, live send OK"), which the Developer sees on the step. With 'with a helper', give helper_branch, helper_folder (the worktree path) and helper_label: they are recorded with the Task and shown in get_status and on the dashboard, and get_status warns when a finished Task's helper branch still has unmerged work. 'released': merged and out (shipped, installed or published); counts as done. 'pending', 'in progress' and 'done' work too (in progress allows one Task of a Goal at a time). Set a state as soon as it changes, such as 'checked' right after you check a helper's work, so the Developer's dashboard keeps moving. If the project has a helper limit (get_status shows it), keep at most that many Tasks with a helper: one more is still set, with a warning. To drop a Task, use update_tasks (action drop).
update_tasks2 of 3 parameters describedStart, complete or drop Tasks, one or several in one call: start one before you change code for it (only one Task of a Goal is in progress at a time); complete it when done, with the files it touched (code), and the new summary when what you built differs from it; drop one that is no longer needed, with the reason. Also sets states and estimates. The operations are applied in order, so a start can follow the complete of the Task that was in progress; if any one fails, none is applied. A 'state' operation takes the same helper_branch, helper_folder, helper_label (with 'with a helper') and evidence (with 'checked') as set_task_state. Each operation can name its own claimed Goal with goal, else the call's goal (or the only Goal held) is used. Answers briefly, with the time a completed Task took and where the work stands, not the whole status.
move_task5 of 5 parameters describedMove a Task of a claimed Goal to another Goal when it belongs there. It keeps its title, summary, files and state, gets a new ID at the end of the other Goal's list (or right before or after the Task given in before or after) and a 'moved from' line. In the old Goal it stays as a dropped Task whose reason is where it went, so refs and history still work. The other Goal must not be dropped, done or held by another running Session; a Task in progress can move only if the other Goal has none in progress.
update_task7 of 7 parameters describedChange a Task's title, summary, files or estimate, for instance when the fix turns out different from the plan or you learn it takes longer. Leaves its status alone.
start_detour3 of 3 parameters describedDeclare that the work is splitting off from the planned Tasks, before doing it. Branches from the current Task. Only one Detour can be open.
end_detour2 of 3 parameters describedEnd the open Detour. 'merge back': it was small and is done; the plan is unchanged. 'return': go back to the plan, appending `tasks` for the Detour's intended work if any. 'recalibrate': drop every remaining Task and replace them with `tasks`.
save_decision4 of 4 parameters describedRecord a choice made for a claimed Goal along the way, such as 'old models get thinking on/off only', so it survives context compression; get_status shows it with its ID (c1, c2...). With id: reword it, or remove it with an empty text. Not for lasting project rules (save_standing_instruction) or project-wide background (update_context).
save_note5 of 5 parameters describedNote something you spotted that belongs to a Goal, such as a bug found during cleanup that belongs to the Voice Goal, instead of dealing with it now. Any Goal on the Roadmap that is not dropped, claimed or not. get_status shows the open notes of the Goals this Session holds. With id: resolve it once dealt with (resolved: true), reopen it (false), reword it, or remove it with an empty text.
ask_developer8 of 8 parameters describedAsk the Developer a question on the dashboard, with 2 to 4 short choices they can click (they can also answer in their own words), instead of stopping in the chat. Use it for product and UX choices only they can make; carry on with other work meanwhile. Their answer reaches you at your next Progressor call, under 'New from the Developer', and is kept as a decision on the Goal. While a question is open the dashboard shows the Goal as waiting on them. To offer ways to go instead, give alternatives and recommended: nobody has to pick, you go ahead with yours. To take back a question that no longer needs an answer, pass withdraw with its ID instead.
reply_to_developer4 of 4 parameters describedAnswer a message the Developer sent you on the dashboard (shown under 'New from the Developer' with its ID, such as m2): say in a sentence or two, in plain words, what you did or will do about it. The reply shows under their message on the dashboard. Reply to every message, even if only to say you will do it later. A message to the whole project is answered with whole_project: true and needs no Goal.
save_hand_test4 of 4 parameters describedAdd something only the Developer can try by hand to a claimed Goal, such as 'OpenCode may ask permission to read an attached file: allow it and check the reply'. Put it here instead of in your chat summary: the Developer sees the Goal's hand-test list on the dashboard and marks each one there as works, doesn't work (with a note) or won't test. A failure adds a Task to the Goal by itself; get_status shows what is still open and the new marks. complete_goal with tests unmarked leaves the Goal waiting on them, and it finishes when the last is marked. With id: reword it, change which Task it is about, or remove it with an empty text (for one that turned out not to need testing); its mark stays, and only the Developer marks tests.
attach_picture6 of 6 parameters describedShow the Developer a screenshot or a short screen recording on the dashboard instead of naming a file in chat. It is copied (not moved) next to the plan, stays on this computer and out of git, and appears on the Goal, on the step or on the hand test you name; the Developer clicks it to enlarge. Allowed: .png .jpg .jpeg .webp .gif and .webm .mp4, up to 10 MB, with a short caption. To take one back, pass remove with its ID (such as 'p2') instead.
save_standing_instruction5 of 5 parameters describedSave a lasting rule from the Developer about how you should work in this project, such as 'ask me before changing the plan'. get_status lists it from then on. Use it only for rules meant to last; a one-off request is just done. A rule the Developer says holds in every project ('in all my projects...', 'always, everywhere...') goes in with global: true: it is saved once for this computer and every project's get_status shows it. With id (s1, s2... in get_status; g1, g2... for a rule for everything): reword it when the Developer changes it, make it hard (hard: true) or ordinary again (false), set the helper limit it holds, or remove it with an empty text. What you leave out stays.
update_context3 of 3 parameters describedReplace the project's Important context: lasting background you and the Developer need in every conversation, such as what the project is, key facts, where things live and choices that hold for the whole project. Not for rules (save_standing_instruction) or for one Goal's details. get_status shows the current text: send the whole new text, or an empty text to clear it. At most 4000 characters.
plan_history2 of 2 parameters describedThe plan's recent changes (who, when, what). restore: <id> goes back to before that change; that can be undone too.
handoff4 of 5 parameters describedA markdown handoff of a stretch of work, for whoever picks it up next. Without text: the facts for the range (steps, decisions, open items, commits, files). Write the handoff from them, then call again with text and title to save it for the dashboard.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.