View as .md ↗
Quo

Quo

MCP server · Communications · quo.com · 6 categories · 36 tools

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.

List Phone Numbers (quo_list-phone-numbers)

List phone numbers assigned to the connected Quo account. Optionally filter to a single user's phone numbers via userId.

Tool Input

userIdstring— Filter to phone numbers assigned to this user id.(min length: 1)

Tool Output

dataarrayrequired— The phone numbers on the connected Quo account.
[]object
idstringrequired— Internal identifier of the phone number.
groupIdstringrequired— Internal identifier of the workspace/group that owns the number.
portRequestIdstringnullrequired— Identifier of the in-progress port request, or null if the number was not ported.
formattedNumberstringrequired— Human-formatted representation of the phone number.
forwardstringnullrequired— Number this phone number forwards to, or null if forwarding is not configured.
namestringrequired— Display name assigned to the phone number.
numberstringrequired— The phone number in E.164 format.
portingStatusstringnullrequired— Status of an in-progress port, or null if the number is not being ported.
symbolstringnullrequired— Emoji/symbol assigned to the phone number for display, or null if unset.
usersarrayrequired— Users the phone number is assigned to (reduced user shape, not `quoUser`).
1 field
[]object
6 fields
emailstringrequired— The user's email address.
firstNamestringnullrequired— The user's first name, or null if unset.
lastNamestringnullrequired— The user's last name, or null if unset.
idstringrequired— Internal identifier of the user.
rolestringrequired— The user's workspace role — one of owner, admin, or member.(enum: "owner", "admin", "member")
groupIdstringrequired— Internal identifier of the workspace/group the user belongs to.
createdAtstringrequired— ISO 8601 timestamp the phone number was created.
updatedAtstringrequired— ISO 8601 timestamp the phone number was last updated.
restrictionsobjectrequired— Calling/messaging restrictions for the phone number.
2 fields
callingobjectrequired— Calling restrictions, by region.
3 fields
CAstringrequired— Restriction value for Canada (e.g. 'unrestricted'/'restricted').
Intlstringrequired— Restriction value for international destinations (e.g. 'unrestricted'/'restricted').
USstringrequired— Restriction value for the United States (e.g. 'unrestricted'/'restricted').
messagingobjectrequired— Messaging restrictions, by region.
3 fields
CAstringrequired— Restriction value for Canada (e.g. 'unrestricted'/'restricted').
Intlstringrequired— Restriction value for international destinations (e.g. 'unrestricted'/'restricted').
USstringrequired— Restriction value for the United States (e.g. 'unrestricted'/'restricted').

We're Adding More Quo Tools Constantly!

Don't see a specific Quo tool you need? Email [email protected] and we can add it.

Quo Frequently Asked Questions

What does the List Phone Numbers tool do?

This page documents the List Phone Numbers tool (quo_list-phone-numbers). List phone numbers assigned to the connected Quo account. Optionally filter to a single user's phone numbers via userId. 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 Tools