get_component
Fetch a single component by UUID — its name, slug, kind, description, tech stack, owner and archive stamp.
Fetch one component in full once list_components has named it, or once an environment's component_id has: what the application is, the slug its versions carry, the technologies it is built with and who answers for it. A component 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
It reads and never changes anything.
Arguments
component_id*stringUUID of the component to fetch.
What it returns
{ "data": { "id": "d4e5f6a7-b8c9-4d0e-9f1a-2b3c4d5e6f70", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "name": "Customer Web App", "slug": "web", "kind": "web_app", "description": "<p>The portal account holders sign in to.</p>", "tech_stack": ["Laravel 13", "Livewire 4", "PostgreSQL 18"], "owner_id": "5e0c7a2d-9b1f-4c3e-8d6a-2f4b7c9e1a30", "position": 0, "archived_at": null, "created_at": "2026-10-20T09:00:00+00:00", "updated_at": "2026-10-27T11:25:00+00:00" }, "meta": {}}How it fails
RESOURCE_NOT_FOUNDunknown component_id, or a component outside the token's scope or the person's visibility.
TOKEN_MISSING_ABILITYtoken lacks component:view.
How is this guide?
Last updated on