MCP Connector

Your AI. Your conversations. Connected.

Ask Claude, ChatGPT or Cursor about the calls, texts and records your team already has in QuorumVoice. Give the answer somewhere real to start.

Or try Quill live in your browser →
Illustrative example
ClaudeQuorumVoice connected
What happened with Dana’s gate issue?
QuorumVoice · ready to read
Find Dana’s contact
Read contact history

Your assistant writes the answer. QuorumVoice supplies the records.

Maria
Work where you think

Keep your assistant. Add the context.

Preparing for a meeting, catching up on a resident, or investigating a busy week? Bring the records into the conversation you’re already having.

Less copying. More context.

Your assistant can look up a person, read their conversation history and find the follow-up that still needs attention. When source links are returned, it can point you back to the original record.

ClaudeQuorumVoice connected
Prep me for tonight’s board meeting. What did residents call about this month?
quorumvoice get_stats✓quorumvoice topic_activity✓

412 calls. Top topics: pool access, gate codes (up 40%) and the special assessment. Here’s a one-page brief with three talking points…

GChatGPTQuorumVoice connected
Write a newsletter blurb about the new gate code, using what residents actually asked.
quorumvoice search_communications✓

From 14 calls and texts this week: “The front gate has a new code as of the 1st. If yours isn’t working, text the office and we’ll send it…”

ClaudeQuorumVoice connected
Who is still waiting on us for an answer?
quorumvoice list_loose_ends✓quorumvoice most_active_contacts✓

Four people: Sam Ortiz (gate code, promised Friday), Tom Alvarez (assessment), Priya Shah (leak) and Nina Park (pool hours).

Claude CodeQuorumVoice connected
Build a weekly call-volume chart for the board deck from our QuorumVoice data.
quorumvoice get_timeseries✓

✓ Pulled 12 weeks · wrote call-volume.tsx · 1 chart, 12 bars

ClaudeQuorumVoice connected
What exactly did Tom Alvarez say about the special assessment?
quorumvoice find_contacts✓quorumvoice get_contact_history✓

Tom called twice and emailed once. He isn’t disputing the amount, only the due date, and asked for a payment plan on the 14th.

CursorQuorumVoice connected
Compare the main line and the maintenance line this month.
quorumvoice get_lines✓quorumvoice get_line_usage✓

Main line: 312 calls, 284 answered and 28 missed. Maintenance: 100 calls, 92 answered and 8 missed.

GChatGPTQuorumVoice connected
Turn our pool rules into a friendly sign for the clubhouse.
quorumvoice search_knowledge✓

“Welcome to the pool! Open 10 to 8 daily. Up to two guests per unit, each with a wristband from the office…”

Illustrative examples
A connected record

Ask across your team’s work.

The connector draws from the same read-only tool family as Quill Assistant. Available tools follow your plan and role.

Find the people, patterns and promises.

Read conversations and contact histories. Review open follow-ups, search your knowledge base, or ask for activity totals and trends. Each request stays scoped to the organization you connected.

Explore the recordsIllustrative example

“What did Dana say about the gate?”

Search by words or meaning
Read summaries and transcripts
Open a text thread

The call and text thread, with the original records.

Prepare the briefing.

Ask what changed, who has been in touch, and which questions remain open. Let your assistant shape the findings for the meeting.

Follow the evidence.

Ask what a caller actually said, then open the conversation behind the answer. The record stays available for your team to verify.

Bring the numbers.

Read activity totals, daily trends and busy hours. Your connected assistant decides how to present or use those results.

Get connected

A sign-in, or a personal token.

Start in QuorumVoice’s MCP settings. Choose the connection method your AI client supports.

Two paths to the same records.

For Claude.ai and ChatGPT, add the connector endpoint, sign in and review the access request. For Claude Code, Claude Desktop and Cursor, create a personal token and use the configuration supplied in settings.

Illustrative example

Claude.ai and ChatGPT

Connect with your QuorumVoice sign-in.

  1. 1Add the connector
  2. 2Sign in to QuorumVoice
  3. 3Review and allow access
  4. 4Ready to ask a question

Example setup only. No account is connected and no credential is created here.

Access stays tied to your account.

A personal token belongs to one person and organization. Choose an expiry, see when it was last used, and revoke it when it’s no longer needed. Tool access follows your current role and plan.

Access follows the personIllustrative example

Maria · Oak Hollow

One person. One organization.

My laptopActive

qv_mcp_••••••••••••••••

Example token · 90-day expiry

Connect your tools

Create a named token for the client you want to connect.

Read-only by design

Useful context. Clear boundaries.

Your connected client can read the tools it has access to. Sending messages and changing QuorumVoice records stay outside this connector.

Your organization’s records.

Each connection resolves to a person and an organization. It does not provide a search across other organizations.

The tools your role allows.

The connector presents the tools enabled for your plan and role. A change in access is checked when the next request arrives.

Your choice of AI client.

Information returned by the connector is shared with the client you connect. Choose a provider and account appropriate for your organization’s data.

The same record, wherever the work happens.

Questions about the MCP connector

MCP stands for Model Context Protocol. The connector lets a compatible AI client request information from your QuorumVoice organization through a defined set of read-only tools. The client writes the answer; QuorumVoice supplies records and source links.

The settings page provides connection paths for Claude.ai, ChatGPT, Claude Code, Claude Desktop and Cursor. Compatible MCP clients can also use the connector. Features, connector availability and setup requirements in another AI product depend on that provider and your account.

The tool catalog covers communications, contacts and their history, open follow-ups, knowledge, analytics, team information and phone lines. The exact tools available to you depend on your organization’s plan, your current role and which tools are enabled. Private team-message tools and the full email-thread tool are not exposed through this connector.

No. The connector’s tools are read-only. They cannot send a text, place a call, edit a contact or close a follow-up. Your connected AI client can use returned information to draft an answer or create something in its own workspace.

Tool results include source links when there are supporting records, so your AI client can cite them. How those citations appear depends on the client. Open the link in QuorumVoice to read the record with your normal account access.

Start in Settings → MCP. Claude.ai and ChatGPT use the connector endpoint and a QuorumVoice sign-in and consent flow. For Claude Code, Claude Desktop and Cursor, create a personal token and use the ready-made client configuration. Never share your token with another person.

Personal tokens can be revoked in Settings → MCP. Members manage their own tokens; owners and admins can see and revoke tokens across their organization. Tokens can have an expiry, and role and plan access are checked on subsequent requests. Sign-in connections use their separate authorization flow.

Available on Pro and Portfolio. Your plan must include the connector, and the specific tools must be enabled for your plan and role. A subscription to a separate AI client is not included with QuorumVoice.

Give your next question the whole conversation.

Not ready? Try Quill live first.