list_invitations

List pending project invitations with their ids. With project (owner only): the invitations that project has sent, for cancel_invitation. Without project: the invitations addressed to you, for answer_invitation. 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-09 — With project: the invitations are read page by page from the database (newest first) instead of all at once; the total counts every pending invitation of the project, the page numbers in the reply and the cursor work as before. Invitations addressed to you (no project) are paged the same way: a page from the database, the total of all of them, the cursor continues where the page ended.
• 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 invitation is {id, project, name, role, by, at} for you, or {id, email, role, at} for a project.
• 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.