get_client
Fetch a single client by UUID — its name, contacts, status and notes.
Fetch one client in full once list_clients has named it or a project's client_id has pointed at it: the registered name, the website, the country and timezone, the primary contact, the notes the team keeps and where the relationship stands. A client outside the token's team, or one a guest's projects do not name, 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
client_id*stringUUID of the client to fetch.
What it returns
{ "data": { "id": "c1a2b3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d", "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86", "name": "Acme Retail", "legal_name": "Acme Retail (Pvt) Ltd", "website": "https://acme.example", "industry": "Retail", "country": "LK", "timezone": "Asia/Colombo", "primary_contact_name": "Jane Perera", "primary_contact_email": "jane@acme.example", "notes": "<p>Prefers a weekly status call on Tuesdays.</p>", "status": "active", "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_FOUNDunknown client_id, or a client outside the token's team or the person's visibility.
TOKEN_MISSING_ABILITYtoken lacks client:view.
How is this guide?
Last updated on