List the saved views of a project: your personal views first, then the project's shared ones, each by name. A view is a named filter, sort and mode (board, list, tree, map) of the web app. Each has id, name, scope (personal or project), mode, query (the web grammar, ids), filters (the same, readable: usernames, label names, epic / story keys, status keys), url, createdBy, updated, rev and canManage. Run one with search_issues view=<id>; change one with save_view. 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.
cursorstringoptionalCursor from `Next page` of an earlier result of this call (omit for the first page); pass it unchanged, with the same other argumentsformatenumoptionalAnswer format: "json" (default) is one compact JSON document; "text" is a readable Markdown answerjsontextlimitintegeroptionalHow many views per page (1–100, default 50)projectstringrequiredProject keyscopeenumoptionalall (default), personal (yours) or project (shared)allpersonalproject
Returns
One of these shapes, depending on the arguments:
Shape 1
countintegerrequiredlimitintegerrequiredprojectstringrequiredviewsarray of object | nullrequired
Shape 2
Optional fields, when present
cursorstringoptionalnotestringoptionalpageintegeroptionalpagesintegeroptionaltotalintegeroptionaltotalApproximatebooleanoptional
- 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.