list_stakeholders
Paginated list of the people a project answers to, with their side, role, weight and the approvals that name them, narrowed by side, role, approval or search words.
Return the stakeholders of one project in the project's order: who they are, whose side they speak for (client, zuse or third_party), what they do for the project, how much weight their word carries, their default RACI letter and which approvals and reports name them. Read it before drafting an approval request, a status report or a question for the client, so you address the person who decides rather than a generic contact.
Narrow with side, role (sponsor, product_owner, business_owner, subject_matter_expert, end_user_representative, technical_lead, architect, security, legal, finance, operations, other), approves (requirements, uat or releases: the people that approval names) and search (words in the name, the email, the organisation or the title). A client guest's token receives each row without email, phone, influence, interest, raci_default, notes and user_id.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
It reads and never changes anything.
Arguments
project_id*stringUUID of the project whose stakeholders to list.
sidestringoptionalNarrow to one side.
clientzusethird_partyrolestringoptionalNarrow to one role.
sponsorproduct_ownerbusiness_ownersubject_matter_expertend_user_representativetechnical_leadarchitectsecuritylegalfinanceoperationsotherapprovesstringoptionalNarrow to the people an approval names: `requirements`, `uat` or `releases`.
requirementsuatreleasessearchstringoptionalWords the name, the email, the organisation or the title must contain.
limitintegeroptionalStakeholders per page (1..100, default 25).
1max100pageintegeroptional1-indexed page number.
1What it returns
{ "data": [ { "id": "a7b8c9d0-e1f2-4a3b-8c4d-5e6f7a8b9c01", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "user_id": null, "name": "Jane Perera", "email": "jane@acme.example", "phone": "+94 77 123 4567", "organisation": "Acme Retail", "side": "client", "title": "Head of Digital", "role": "product_owner", "influence": "high", "interest": "high", "raci_default": "accountable", "approves_requirements": true, "signs_off_uat": true, "approves_releases": false, "receives_status_reports": true, "notes": "<p>Prefers a call over email for anything urgent.</p>", "position": 0, "created_at": "2026-10-20T09:10:00+00:00", "updated_at": "2026-10-27T11:30:00+00:00" } ], "meta": { "page": 1, "limit": 25, "total": 1, "has_more": false }}How it fails
VALIDATION_FAILEDside or role is not one of its values, or approves is not requirements, uat or releases.
RESOURCE_NOT_FOUNDunknown project_id, or a project outside the token's scope or the person's visibility.
TOKEN_MISSING_ABILITYtoken lacks stakeholder:view-any.
How is this guide?
Last updated on