list_deployments
Lists a project's deployments, the newest first, with the environment each went into, the version, the commit and branch, where it stands, where the record came from and the timing; narrows by environment, component, status, source and words.
Read what was deployed where, and how it went. Give project_id; narrow with environment_id, component_id, status (queued, running, succeeded, failed, rolled_back or cancelled), source (ci, github, manual or rollback) and search (words in the version, the commit or the branch); page with limit and page. Each row is the record GET /v1/projects/{project}/deployments answers, with environment_name beside environment_id. Read it to answer which deployments failed lately, which version a staging environment has had and when, or whether a deployment is still running before starting another; get_environment_status answers the same for one environment with what runs there now. Staff only: a guest token is refused, because deployments are the team's business. It needs deployment:view-any.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Annotations
It reads and never changes anything.
Arguments
project_id*stringUUID of the project whose deployments to list.
environment_idstringoptionalNarrow to the deployments into one environment, by UUID.
component_idstringoptionalNarrow to the deployments of one component, by UUID.
statusstringoptionalNarrow to one status.
queuedrunningsucceededfailedrolled_backcancelledsourcestringoptionalNarrow to one source.
manualcigithubrollbacksearchstringoptionalWords the version, the commit or the branch must contain.
limitintegeroptionalDeployments per page (1..100, default 25).
1max100pageintegeroptional1-indexed page number.
1What it returns
{ "data": [ { "id": "6a7b8c9d-0e1f-4a2b-9c3d-4e5f6a7b8c9d", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "component_id": "d4e5f6a7-b8c9-4d0e-9f1a-2b3c4d5e6f70", "environment_id": "e5f6a7b8-c9d0-4e1f-8a2b-3c4d5e6f7081", "environment_name": "Staging", "release_id": null, "version": "1.4.0", "commit_sha": "a1b2c3d4e5f60718293a4b5c6d7e8f9012345678", "branch": "main", "status": "succeeded", "source": "ci", "triggered_by": "3f8a1c2e-7b4d-4e5f-9a6b-1c2d3e4f5a6b", "external_id": null, "pipeline_url": "https://ci.example.test/runs/4821", "started_at": "2026-11-03T10:12:00+00:00", "finished_at": "2026-11-03T10:15:30+00:00", "duration_seconds": 210, "notes": null, "rollback_of_id": null, "created_at": "2026-11-03T10:12:00+00:00", "updated_at": "2026-11-03T10:15:30+00:00" } ], "meta": { "page": 1, "limit": 25, "total": 1, "last_page": 1 }}How it fails
VALIDATION_FAILEDenvironment_id or component_id is not a UUID, or status or source is not one of the values listed.
RESOURCE_NOT_FOUNDunknown project_id, or a project the token may not see.
FORBIDDENthe token is a client guest's, or the holder may not read the project's deployments.
TOKEN_MISSING_ABILITYtoken lacks deployment:view-any.
How is this guide?
Last updated on