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 talk to Quill live in your browser →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.
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.
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.
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.
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.
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.
Bring the context from QuorumVoice into the AI tools you already use.
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 → Integrations. 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 → Integrations. 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 Advanced. 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.