get_stakeholder
Fetch a single stakeholder by UUID — their side, role, weight, RACI default, approver flags and, for a staff token, contact details, notes and linked account.
Fetch one stakeholder in full once list_stakeholders has named them: whose side they speak for, what they do for the project, which approvals and reports name them, and for a staff token how to reach them and what the team noted about them. A stakeholder outside the token's team or project scope, or one the person cannot see, answers RESOURCE_NOT_FOUND, never a permission error, so existence does not leak.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same actions 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
stakeholder_id*stringUUID of the stakeholder to fetch.
What it returns
{ "data": { "id": "a7b8c9d0-e1f2-4a3b-8c4d-5e6f7a8b9c01", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "user_id": "6b2d9f41-0c7e-4a58-9d3f-1e8a7c5b2d90", "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": true, "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": {}}A guest's token receives the same record without email, phone, influence, interest, raci_default, notes and user_id.
How it fails
RESOURCE_NOT_FOUNDunknown stakeholder_id, or a stakeholder outside the token's scope or the person's visibility.
TOKEN_MISSING_ABILITYtoken lacks stakeholder:view.
How is this guide?
Last updated on