# Report on a project: progress, overdue items, and how it compares with last week

> Report on a project: progress, overdue items, and how it compares with last week: 0 companies fully do it, 11 with a limit, 18 carry the tag. Every listing in Project & task management with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/project-management.status-report/
- Markdown: https://www.anchorterminal.com/niches/project-management.status-report/index.md (~1,550 tokens)
- Slim: https://www.anchorterminal.com/niches/project-management.status-report/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/project-management.status-report/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 11 | 18 | 16 | 9 |

## What counts as done

Counts by status, overdue items with owners, and the latest and previous status updates for the period; a posted status update returns its link.

Measured, for our own tests: the reads take at most three calls.

How agents ask for it: give me a daily summary of this project; how is the sprint going; compare this week's status update with the last three; post an at-risk status update on the project

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Asana (Asana, Inc.)**: get_status_overview aggregates status, task summaries and blockers in one call, but the connector reads only the latest status update (acc-39) and a posted update returns no link (acc-38); REST lists history with created_since, on a separate token.
- **Basecamp (37signals LLC)**: The overdue report and gauge needles (a project's status history, newest first, with colour and description) cover overdue work and past updates, but no endpoint returns counts by status, so the agent assembles them from to-do lists.
- **Financial Cents MCP (Financial Cents LLC)**: list_tasks returns done, not_done and overdue counts with group_by project, client or assignee in one call, but there is no project status update to read or post.
- **monday.com (monday.com Ltd.)**: board_insights aggregates, filters and groups board data in one call and get_board_activity reads activity logs, but there is no project status update object to list or post.
- **ONES (The Beautiful ONES Technology PTE. LTD.)**: Sprint details and ONESql give counts the agent can assemble, but no status update object or project summary tool appears in the MCP tool list.
- **Plane (Plane Software, Inc.)**: workitem count with pql and group_by gives counts by state in one call and cycles list their work items, but there is no status update object with history to read or post.
- **Shortcut (Shortcut Software Company)**: Epic and objective health-history endpoints list past health updates most recent first, and iteration stories are listable, but acc-33 found iteration stats and point totals missing from the MCP and no single summary call.
- **Taiga (Taiga Cloud Services, S.L.)**: Project stats, issue stats and milestone stats endpoints return counts and progress in one call each, but Taiga has no status update object, so 'compared with last week' has no history.
- **Teamwork.com (Teamwork Crew Limited)**: count_tasks with date_filter counts overdue work and Project Update can be listed, but the MCP cannot post a project update, and an at-risk update needs the web app or REST.
- **Todoist (Todoist Inc.)**: get-project-health, get-project-activity-stats and get-overview give project summaries and activity, but Todoist has no status update object, so prior reports and a posted at-risk update with a link aren't available.
- **Wrike (Wrike, Inc.)**: get_item_history reads field-change history over a date range, including project status changes, but there is no status update object or summary tool, so counts by status need search_items per status.

- not this job: ClickUp (Mango Technologies, Inc. DBA ClickUp): Time-in-status and filter tools give raw counts, but there is no project status update object to read or post and no project summary tool; dashboards are only found by search.
- not this job: OpenProject (OpenProject GmbH): No status update or project summary tool is in the MCP list, and acc-55 found project custom field values unreadable; the agent would count work packages page by page.
- not this job: Redmine (Redmine project): The REST API has no project summary, counts-by-status or status update resource; an agent pages /issues and counts itself.
- not this job: Roma (Milo Mode Inc.): Roma keeps personal and shared lists; there is no project status update, summary or counts-by-status tool.
- not this job: Taskade (Taskcade Inc.): No status update, summary or counts tool; the agent reads the project tree and counts completed flags itself.
- not this job: Trello (Trello, Inc.): Trello has no project status update, summary or counts endpoint; an agent reads board cards and counts by list itself.
- not this job: YouTrack (JetBrains s.r.o.): No status update, report or counts tool among the predefined MCP tools; get_project returns project details only.

## What stops agents finishing

- only the latest status update is readable, so trends need the UI
- read-only mode removes the tools that read column data
- project custom field values not exposed
- created status update returns no link to hand the user

## Around it

Before: project-management.find-work. After: email.send, messaging.post-update, spreadsheets.append-row.

## Where this comes from

Weight 16 of 100 in Project & task management: 9 of 58 accounts; weekly workload reviews through ChatGPT, daily project summaries, morning briefings, Shortcut iteration progress, setting project status, and read-only modes that leave too little to report on.

As data: https://www.anchorterminal.com/api/v1/use-cases/project-management.status-report.json, or the MCP tool get_use_case with id project-management.status-report. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
