# Identity

Quo MCP server · 4 tools

Identity covers the workspace's people and numbers: users (members who own conversations and get tasks assigned) and phone numbers (the from-identity for outbound calls and texts).

## Quo Frequently Asked Questions

**What are the Quo Identity tools?**

This page lists the Identity tools in the Quo integration: 4 tools for working with identity. Each is exposed through your firm's Weave MCP connection and available to members whose access level permits it.

**How do I find the user to assign a task to?**

Use list-users (or get-user by ID) to look up workspace members, then pass that user ID to assign-task.

**Which number does an outbound message or call use?**

A Quo phone number is the sending identity. Use list-phone-numbers to find the number to send from; it is the phoneNumberId that message and call tools operate against.

**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/messages/
- /integrations/quo/calls/
- /integrations/quo/tasks/assign-task/

## Tools

- [Get Phone Number](/integrations/quo/identity/get-phone-number/) — Fetch a single phone number on the connected Quo account by ID.

- [Get User](/integrations/quo/identity/get-user/) — Fetch a single user (workspace member) from the connected Quo account by ID.

- [List Phone Numbers](/integrations/quo/identity/list-phone-numbers/) — List phone numbers assigned to the connected Quo account. Optionally filter to a single user's phone numbers via userId.

- [List Users](/integrations/quo/identity/list-users/) — List the users (workspace members) on the connected Quo account. Supports pagination via maxResults (1-50) and pageToken.
