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.

Get Call (quo_get-call)

Fetch a single call from Quo by its ID.

Tool Input

callIdstringrequired— Internal identifier of the call to fetch.(min length: 1)

Tool Output

dataobjectrequired— The requested call.
answeredAtstringnullrequired— ISO 8601 timestamp the call was answered, or null if it was never answered.
answeredBystringnullrequired— Internal identifier of the Quo user who answered an incoming call, or null for outgoing/unanswered calls.
initiatedBystringnullrequired— Internal identifier of the Quo user who initiated an outgoing call, or null for incoming calls.
directionstringrequired— The call's direction relative to the Quo number.(enum: "incoming", "outgoing")
statusstringrequired— The call's current status.(enum: "queued", "initiated", "ringing", "in-progress", "completed", "busy", "failed", "no-answer", "canceled", "missed", "answered", "forwarded", "abandoned")
completedAtstringnullrequired— ISO 8601 timestamp the call ended, or null if ongoing/not completed.
createdAtstringrequired— ISO 8601 timestamp the call record was created.
callRoutestringnullrequired— How the call reached the user's inbox (e.g. phone-number, phone-menu), or null for outbound calls.
durationintegerrequired— Total duration of the call in seconds.
forwardedFromstringnullrequired— Phone number or Quo user id the call was forwarded from, or null if not forwarded.
forwardedTostringnullrequired— Phone number, Quo phone number id, or Quo user id the call was forwarded to, or null if not forwarded.
aiHandledstringnullrequired— Type of AI that answered the call (e.g. ai-agent), or null for a human-answered call.
idstringrequired— Internal identifier of the call.
phoneNumberIdstringrequired— Internal identifier of the Quo number associated with the call.
participantsarrayrequired— E.164 phone numbers of the call participants, excluding the Quo number.
[]string
updatedAtstringnullrequired— ISO 8601 timestamp the call record was last updated, or null. See note above.
userIdstringnullrequired— Internal identifier of the Quo user account associated with the call, or null. See note above.

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 Get Call tool do?

This page documents the Get Call tool (quo_get-call). Fetch a single call from Quo by its ID. It is one of the Quo Calls 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

get-call-recordingsget-call-summaryget-call-transcriptget-call-voicemail