Skip to main content
Developers

MCP Tools: Users

Last updated 1 day ago

MCP Tools: Users ​

All calls: POST /api/mcp with {"method":"tools/call","params":{"name":"<tool>","arguments":{…}}}.

list_users ​

Lists all users in the organization. read · follower

ParameterTypeDefaultDescription
statusenum active | inactive | suspended–Filter by status
roleenum admin | user | guest–Filter by role
teamIdstring–Filter by team membership
searchstring–Search in name and email
limitnumber50Number of results
offsetnumber0Skip results

Response: { users, total, limit, offset, has_more }.

get_user ​

Details of a single user. read · follower

ParameterTypeDefaultDescription
userIdstring (required)–UUID of the user

get_me ​

The currently authenticated user. read · guest

No parameters.

get_user_workload ​

Workload (assigned items by status). read · follower

ParameterTypeDefaultDescription
userIdstringcurrent userWhich user to query

Response: { total_cards, total_overdue, by_status[] }.

invite_user ​

Invites one or more people into the current organization by email and sends each an invitation mail with a join link.

write · admin
ParameterTypeDefaultDescription
emailsstring[] (1–20) (required)–Email addresses
roleenum user | guestuseruser = full member, guest = follows only the projects in lists
listsstring[]–Only for guest, required there: IDs or SIDs of the projects the guest follows

Only admins/owners may invite members. Guests may also be invited by the owner of all given projects. Guests require the Pro plan. All of this is enforced server-side. The response contains a result per email (invited / already a member / already invited).

What a guest can do is described under Teams & Workspace → Guests.

Confirm first

Agree the addresses, the role and, for guests, the projects with the user before calling — an invitation cannot be taken back.