READ

list_teams

List every team the authenticated person owns or belongs to. Read-only — changing a team stays in the application and the REST API.

List every team the caller has visibility into. Useful before minting a token scoped to a specific team: an agent can surface a picker instead of making the person hunt for a UUID. Read-only; creating, renaming and deleting a team stays in the application and the REST API.

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

This tool takes no arguments.

What it returns

{  "data": [    {      "id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",      "name": "Zuse Technologies",      "owner_user_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",      "created_at": "2026-01-12T10:05:00+00:00"    }  ],  "meta": { "total": 1 }}

How it fails

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks team:view-any.

How is this guide?

Last updated on