# Get User

`quo_get-user` · Quo MCP tool · Identity

Fetch a single user (workspace member) from the connected Quo account by ID.

## Quo Frequently Asked Questions

**What does the Get User tool do?**

This page documents the Get User tool (`quo_get-user`). Fetch a single user (workspace member) from the connected Quo account by ID. It is one of the Quo Identity tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

**What is the Quo integration?**

The Quo integration connects your firm's Quo account to Weave. Quo is a cloud phone/SMS platform. This integration exposes calls, messages, contacts, conversations, and tasks as governed MCP tools, scoped per member by access level. It groups 36 tools into 6 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

**How does my firm connect Quo to Weave?**

An admin connects Quo once for the whole firm by entering your Quo workspace API key in the Weave console. Every member then works through that single connection; there is no per-user Quo login. Your key is encrypted at rest and stays inside Weave's infrastructure.

**Do I need to install or configure anything locally?**

No. Weave is fully hosted, so there is nothing to install, run, or maintain on your own machines. After an admin connects Quo once from the console, each member simply points their AI assistant at your firm's Weave MCP endpoint, and the tools they are allowed to use appear automatically based on their access level.

**Can everyone on my team use every tool?**

No. Tools are exposed per member by access level, so each person only sees the Quo tools their role permits.

**Are changes made through these tools reversible?**

Reads are always safe. Sending a text cannot be undone, once sent it can't be recalled, and it spends the workspace's prepaid SMS credits. Deletes are irreversible: delete-contact and delete-task permanently remove the record from Quo. Most other actions can be reversed with a follow-up tool (for example reopen-task or unassign-task).

**Why can't I send a text to a US number?**

Sending SMS to US numbers requires your Quo account to have completed US Carrier Registration. That is a Quo-side prerequisite; once it is done, send-message works for US recipients.

## Related
- /integrations/quo/identity/list-users/
- /integrations/quo/tasks/assign-task/

## Input

- **userId** `string` (required, min length: 1) — Internal identifier of the user to fetch.

## Output

- **data** `object` (required) — The requested user.
  - **id** `string` (required) — Internal identifier of the user.
  - **email** `string` (required) — The user's email address.
  - **firstName** `string | null` (required) — The user's first name, or null if unset.
  - **lastName** `string | null` (required) — The user's last name, or null if unset.
  - **pictureUrl** `string | null` (required) — URL of the user's profile picture, or null if unset.
  - **role** `string` (required, enum: "owner", "admin", "member") — The user's workspace role — one of owner, admin, or member.
  - **createdAt** `string` (required) — ISO 8601 timestamp the user was created.
  - **updatedAt** `string` (required) — ISO 8601 timestamp the user was last updated.