list_projects

List your projects: those you are a member of plus featured ones (featured: true; read-only). Other public projects are not listed: read one by key, or join_project. Each has its key, your role, issue counts (open, total, per status category and per status key), visibility and whether you pinned it, and unseen: what others changed since you last opened the project in Sprintree. Pinned projects come first, in your sidebar order. Each project has the group you filed it in (save_project_group, move_project); group lists one group's projects. The status keys are what search_issues, update_issue_status and get_issue_stats take; list_statuses names them. Answers are compact JSON; pass format="text" for a readable Markdown answer. Results are paged: if the answer has a cursor, call again with it (a missing cursor means the last page) — never assume the first page is everything.

• 2026-10-01 — Every project now shows its issue counts per status category (to do, in progress, review, done) and per status key, custom statuses included.
• 2026-10-05 — Each project can carry unseen: what other people changed in it since you last opened it in Sprintree (total, and new_issues / status_changes / comments / assigned_to_me / other_edits when not 0; capped: true reads "99+"). The text table has an Unseen column. Only the projects of the page are counted; nothing here marks a project seen.
• 2026-10-05 — unseen.badge shows the badge setting of the project (dot or off; absent: counts, see pin_project). A project set to dot or off is listed with unseen even when nothing is new (total 0); off is not counted.
• 2026-10-06 — Each project shows the group and group_id of your own sidebar folder it is filed in (absent when none; the text table has a Group column), and the new group argument (name or id) lists only that group's projects. Groups are personal: nobody else sees yours. See save_project_group and move_project.
• 2026-10-06 — Lists the projects you are a member of plus featured ones (featured: true on the row, role viewer), no longer every public project. Join one with join_project; reading it by key still works.
• 2026-10-02 — Answers are compact JSON by default (one document, no Markdown, nothing said twice); format="text" gives the readable Markdown without the json block. Each project is {key, name, role, open, total, todo / in_progress / review / done (not when 0), by_status {status key: count}, visibility, featured and pinned (only when true)}.
• 2026-10-02 — Paged: new optional limit and cursor arguments. The answer carries the paging (total, totalApproximate, page, pages, count, limit, cursor; a missing cursor means the last page); format="text" opens with a header (Page N of M · X items · showing a–b) and ends with the next cursor or Last page.
• 2026-10-03 — Also answers structuredContent (see outputSchema); a failed call adds structuredContent.error. Text unchanged. Details: /docs/mcp, "Structured results and errors".
• 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.
• 2026-10-04 — format="text" now also answers structuredContent {"text": the Markdown} (it was the JSON document), so a client that reads only structuredContent gets the Markdown it asked for.