READ

get_project

Fetch a single project by UUID — its key, status, methodology, visibility, health, leads and dates.

Fetch one project in full once list_projects has named it: the key every reference inside it carries, where it is in its lifecycle, how the team works it, who leads each discipline and the dates it runs between. A project 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 action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

project_id*string

UUID of the project to fetch.

What it returns

{  "data": {    "id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",    "client_id": "c1a2b3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",    "key": "CRM",    "name": "Customer Portal",    "tagline": "Self-service portal for the client's account holders",    "description": "<p>Account holders manage invoices, tickets and contacts without calling support.</p>",    "status": "in_development",    "methodology": "scrum",    "visibility": "team",    "health": "on_track",    "lead_pm_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "lead_ba_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "lead_dev_id": "5e0c7a2d-9b1f-4c3e-8d6a-2f4b7c9e1a30",    "lead_qa_id": null,    "starts_on": "2026-09-01",    "target_launch_on": "2027-01-15",    "launched_on": null,    "budget_hours": 1200,    "archived_at": null,    "created_at": "2026-08-20T10:05:00+00:00",    "updated_at": "2026-10-24T16:40:00+00:00"  },  "meta": {}}

How it fails

RESOURCE_NOT_FOUND

unknown project_id, or a project outside the token's scope or the person's visibility.

TOKEN_MISSING_ABILITY

token lacks project:view.

How is this guide?

Last updated on