Model Context Protocol (MCP) connects compatible external AI assistants to the Qonvera CRM records you are allowed to access. Ask about a contact, review an opportunity or catch up on a conversation without granting unrestricted access to your business.
Sales context sits across customer conversations, contacts, company accounts, opportunities and follow-ups. An external assistant cannot understand that context from a disconnected chat alone. Qonvera's MCP integration provides permitted record access through a connection your team explicitly authorizes.
MCP is separate from Qonvera's Receptionist, Qualification and Sales Assistant agents. It connects an external assistant to your approved workspace; it does not purchase those agents, enable automatic customer replies or replace your team's responsibility for sales decisions.
Find a contact or account, review an opportunity and its service items, summarize an accessible conversation or list follow-ups. Ask for supporting Qonvera record links and a fresh read when checking an answer.Explore opportunity and pipeline context
Authorize one workspace and review the requested permissions. Your current role, membership and record access still apply to every operation. Conversation access includes message text; share it deliberately.Review Qonvera team roles and workspaces
Where supported and enabled, approve specific create or edit permissions separately. Read access alone cannot change records. Any supported change must also pass Qonvera's normal role, record-version and creation-limit checks.Check supported actions and limitations
Review external AI connections in Settings and revoke access to stop future requests. Permission or membership changes can also stop access. Revocation does not erase information already shared with the external provider.Read Qonvera's privacy policy
Illustrative workflow: start with synthetic sample records and read-only access. This is a setup example, not a customer result or a promise of universal client compatibility.
Confirm that your assistant supports Qonvera's remote connector setup and that MCP access is available for your workspace subscription. Open Settings → Developers → External AI assistants.
Copy the server URL displayed in Qonvera into the assistant's connector settings. Sign in to Qonvera, check the client and callback domain, then approve only the workspace and permissions you intend to share.
For example: “Review this sample opportunity and list its follow-ups with supporting record links.” Begin with a specific accessible record; ask for another page if the results are incomplete.
Open the supporting records in the connected workspace, confirm the current details and decide what to do next. A generated summary is not a sent message, a completed follow-up or a won opportunity.
Bring permitted CRM context into a compatible external assistant for research and review. Keep client support, record access and human decisions explicit.
Compatible ChatGPT and Claude remote connector setups depend on provider plans, organization policies and Qonvera availability. A public Qonvera directory listing is not guaranteed. Use the verified setup instructions rather than assuming every assistant or account can connect.
MCP is a separately priced workspace add-on, not a base-plan inclusion or an AI-agent bundle. Confirm current monthly or annual terms and workspace availability with Qonvera. Your assistant provider may charge separately, and connecting does not reset Qonvera allowances.
Read permissions may expose customer details, notes and conversation text to the external provider. Conversation context is bounded and paginated; attachments are not shared. Review that provider's privacy and retention settings before authorizing access.
Supported optional actions depend on the client and approved permissions. The current read-only public-plugin package cannot edit records. Message sending, ownership reassignment, pipeline stage/won/lost changes and Qonvera-agent activation are unavailable through this integration. Reviewed archive actions, where available, require separate approval in Qonvera.
MCP stands for Model Context Protocol, an open standard for connecting AI applications to external data and tools. Qonvera uses it to let a compatible external assistant work with permitted CRM records through an authorized workspace connection.Read the official MCP introduction
Compatible remote connector setups can connect where the assistant's plan and organization policies permit it and Qonvera access is available. Check the current setup guide or ask Qonvera support. A private connected account does not establish public plugin-directory availability.Follow the external AI assistant setup guide
Depending on approved permissions and your current access, it can find contacts and accounts, review opportunities and their service items, summarize accessible conversations and list follow-ups. Reads are paginated, long message text may be shortened and attachments are not shared.
No. Each connection is bound to your Qonvera user and one approved workspace. Your current role, assignments and record access still apply. To connect a different workspace, start a separate connection and authorize that workspace.
Read-only permission cannot change records. Optional create/edit actions require explicit approval, client support, rollout availability and normal Qonvera authorization. The current read-only public-plugin package cannot change records. This integration does not send customer messages or change opportunity stage/won/lost outcomes.
No. Receptionist responds to incoming enquiries using approved knowledge and human handover. Qualification identifies service interest and scores leads. Sales Assistant helps your team with summaries, questions and next steps. MCP connects a separate external assistant and does not include or activate those agents.Compare Qonvera's three AI-agent roles
MCP provides a connector and consent workflow for an external AI assistant. The public API is for software integrations using their own credentials and scopes. They are separate purchases and access paths; an MCP connection does not grant an API key.Review public API and webhook setup
MCP is priced separately for the workspace you connect. Confirm current monthly or annual terms and availability with Qonvera before purchasing; external assistant-provider fees may also apply. MCP access does not purchase Qonvera agents or reset their usage allowances.Review base plans and separate add-ons
Qonvera checks subscription access, user permissions and connection authorization on each operation. Revocation or loss of required access stops future requests; an already admitted read may finish. Earlier answers can remain in the external assistant's history, so review that provider's retention controls.
No. Use the server URL shown in Qonvera and complete the Qonvera sign-in and permission approval flow. Never paste API keys, database credentials, account passwords or access tokens into an assistant conversation.
Get a focused walkthrough built around your customer messaging workflow.