Weave
Sign InSign Up
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 Messages (quo_list-messages)

List SMS/MMS messages sent or received on a Quo phone number with a set of participants (1:1 or group conversation), with optional date-range filtering and pagination.

Tool Input

phoneNumberIdstringrequired— Internal identifier of the Quo number used to send or receive the messages.(min length: 1)
participantsarrayrequired— Phone numbers involved in the conversation, in E.164 format, excluding your Quo number (1-10 items). A single participant fetches a 1:1 conversation; multiple participants fetch a group conversation.(min items: 1, max items: 10)
[]string(min length: 1)
maxResultsintegerrequired— Maximum number of results to return per page (1-100).(>= 1, <= 100)
pageTokenstring— Opaque pagination token from a prior response's nextPageToken, to fetch the next page.
userIdstring— Filter to messages sent by this user's internal identifier.
createdAfterstring(date-time)— Filter to messages created after this ISO 8601 timestamp.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$)
createdBeforestring(date-time)— Filter to messages created before this ISO 8601 timestamp.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$)

Tool Output

dataarrayrequired— The page of messages returned.
[]object
idstringrequired— Internal identifier of the message.
toarrayrequired— Recipient phone numbers, in E.164 format.
1 field
[]string
fromstringrequired— The sender identifier — typically an E.164 phone number, but can vary in format.
textstringrequired— The content of the message.
phoneNumberIdstringrequired— Internal identifier of the Quo number used to send or receive this message.
conversationIdstringrequired— Internal identifier of the conversation this message belongs to.
directionstringrequired— The direction of the message relative to the Quo number.(enum: "incoming", "outgoing")
userIdstringnullrequired— Internal identifier of the user who sent the message, or null for incoming messages.
statusstringrequired— The status of the message.(enum: "queued", "sent", "delivered", "undelivered", "received")
createdAtstringrequired— ISO 8601 timestamp the message was created.
updatedAtstringrequired— ISO 8601 timestamp the message was last updated.
mediaarray— Media attachments on the message, with upstream URLs omitted (design §7). Absent when the OpenAPI response omits the field.
1 field
[]object
1 field
typestringnull— MIME type of the attached media, or null/absent if unknown. NOT live-verified (every observed row had an empty media array).
totalItemsintegerrequired— Total message count across all pages, as reported by Quo. Quo documents this figure may be inaccurate.
nextPageTokenstringnullrequired— Opaque token for the next page, or null when there is no further page.

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 Messages tool do?

This page documents the List Messages tool (quo_list-messages). List SMS/MMS messages sent or received on a Quo phone number with a set of participants (1:1 or group conversation), with optional date-range filtering and pagination. It is one of the Quo Messages 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

list-conversationsget-messagesend-message