Skip to main content
Quo MCP currently exposes the same complete toolset to Claude, ChatGPT, and other connected MCP clients. A client can call several tools in one task—for example, discover an inbox, fetch its recent messages, and create follow-up tasks from the results. Tool names and parameters are stable identifiers. How you select or approve a tool call depends on your MCP client.

​
Workspace discovery

Example prompts:
  • “Which Quo numbers can I use, and who is assigned to each one?”
  • “Find Jamie’s user ID and show the inboxes assigned to them.”

​
Messages and conversations

​
Choose the correct send tool

​
Bulk message modes

send-bulk-messages accepts one of two input modes:
  • Same message: Provide to as an array of 2–40 phone numbers and content as the message sent to every recipient.
  • Personalized messages: Provide messages as an array of 2–40 objects, each containing that recipient’s to phone number and content.
Use exactly one mode per call. Do not combine messages with to or content, and include each recipient only once. Use send-message when sending to one person. All three send tools:
  • Require a from number that belongs to the connected Quo workspace. The tool accepts its E.164 number or PN… phone-number ID.
  • Accept message content up to 1,600 characters.
  • Use prepaid messaging credits and count as API-powered messages. See API pricing.
  • Cannot undo or recall a message after it is sent.
Confirm the sender, recipients, message content, and whether the recipients should share a thread before sending. In particular, never substitute send-group-message for a private broadcast.
Example prompts:
  • “Show me yesterday’s messages across the support inbox and summarize the open questions.”
  • “Draft a reply to +14165550100, but ask me to approve it before sending.”
  • “Send this service notice privately to these 12 customers so none of them can see the other numbers.”
  • “Send each attendee their own confirmation time from this list as a private message.”

​
Calls and voicemail

Voicemail processing is asynchronous. If a voicemail has an in-progress status, its duration, transcript, and recording URL may be empty; retry after processing completes. A missed call with no voicemail is still returned. Call and message results include activity IDs (AC…). Multi-contact results can also include conversation IDs (CN…). Use these IDs to link a follow-up task to the exact call, message, or conversation. Example prompts:
  • “What calls did we miss yesterday, and which callers left a voicemail?”
  • “Summarize this week’s completed call transcripts for the sales inbox.”
  • “Find Pat’s call from this morning and create a task linked to that call.”

​
Contacts

Phone numbers are normalized to E.164. Email values must be valid email addresses. Example prompts:
  • “Look up the contact with +14165550100 and show their custom fields.”
  • “Create a contact for Priya Shah at Northwind, then show me the new contact ID.”
  • “Clear the outdated role on this contact without changing any other field.”

​
Tasks

When creating a task, use the most specific link available:
  1. Use an activityId (AC…) for one particular call or message.
  2. Use a conversationId (CN…) for the whole thread with a contact.
  3. Use an inbox number or PN… ID only when the task is not about a specific activity or conversation.
update-task can update the title and description together as one change. Assignment, unassignment, due-date changes, completion or reopening, and conversation linking or unlinking are separate change types. Example prompts:
  • “List the open tasks and show who each is assigned to.”
  • “Create a follow-up task for tomorrow linked to this missed call and assign it to Alex.”
  • “Mark task TK… complete.”

​
Fetch modes and pagination

The fetch tools can search a specific contact deeply or discover activity across an inbox broadly.

​
One contact

Set participantPhoneNumber to query one contact.
  • fetch-messages, fetch-call-transcripts, and fetch-missed-calls return up to 100 matching records per page.
  • If the response includes a next-page token, call the same tool with the same filters plus pageToken.
  • A pageToken can be used only when participantPhoneNumber is set.

​
Whole inbox

Omit participantPhoneNumber to discover active conversations across the inbox.
  • fetch-messages returns up to 10 in-window messages per contact across up to 50 contacts. It flags contacts with more messages so the client can re-query that contact in one-contact mode.
  • maxResults applies to one-contact message queries and is ignored by the whole-inbox message view.
  • Call tools aggregate matching calls across discovered participants, up to the requested result limit.
  • If a response indicates that older conversations remain, continue discovery with the returned conversationPageToken.
The tool response includes the token and guidance needed for the next call. Treat page tokens as opaque and do not modify them.

​
Dates, times, and phone numbers

  • Pass createdAfter, createdBefore, and task due dates as ISO 8601 datetimes with Z or an explicit offset, such as 2026-08-21T14:00:00-04:00.
  • Fetch results use UTC timestamps. A client should convert relative requests such as “yesterday” from the user’s local timezone to the corresponding UTC range, then present results in the user’s timezone.
  • Use E.164 for external phone numbers, such as +14165550100. International numbers are supported.
  • When a tool accepts an inbox, use either its E.164 number or its PN… ID. Run list-inboxes to discover valid values.