Service enablement guide for the Coevera MCP Server and the Automation Hub connectors that link a customer's CRM to AI assistants such as Claude and ChatGPT.
A secure bridge that lets an AI assistant read and update a customer's Coevera CRM in plain conversation.
Three connectors in the Automation Hub: verified Claude and ChatGPT connectors, plus a configurable Custom connector.
No exports, no copy-paste. The customer asks; the AI answers and acts on live CRM data, with their own permissions.
The Coevera MCP Server connects a customer's CRM to AI assistants. Instead of exporting spreadsheets and pasting them into a chat window, the customer's chosen assistant connects directly to their Coevera space and can search, summarise, create, and update CRM records on request.
It is built on the Model Context Protocol (MCP) — an open industry standard for connecting AI assistants to external tools and data. Because it is a standard, the same server works with Claude, ChatGPT, and other MCP-compatible assistants. The customer never sees the protocol; they just enable a connector and start asking questions.
Customers reach these connectors from CRM Space Administration, under Automation Hub. There are three of them, described next.
| Connector | Status | Configuration | Intended audience |
|---|---|---|---|
| Claude Connector | Verified | No — enable & connect | End customers using Claude (claude.ai, Claude Desktop, or the Claude apps). |
| ChatGPT Connector | Verified | No — enable & connect | End customers using ChatGPT. |
| Custom MCP Connector | Custom | Yes — connection settings required | Internal development and testing, custom in-house assistants, and approved third-party AI agents that speak the MCP standard. |
The two verified connectors (Claude and ChatGPT) are officially approved and listed in the Coevera app catalogue. They have no configuration options — the customer simply enables the connector and connects their AI account. The Custom connector is configurable and is meant for development and third-party agents.
A pre-approved, verified connector published in the Coevera app catalogue. It is dedicated to Anthropic Claude and ships with everything pre-configured. There are no settings to fill in — the customer simply enables it and connects their Claude account.
Who it's for: End customers using Claude (claude.ai, Claude Desktop, or the Claude apps).
A pre-approved, verified connector published in the Coevera app catalogue. It is dedicated to OpenAI ChatGPT and, like the Claude connector, has no configuration options. The customer enables it and connects their ChatGPT account.
Who it's for: End customers using ChatGPT.
A flexible, configurable connector for cases the two verified connectors do not cover: development and QA, bespoke integrations, or connecting a third-party AI agent. Because it can point at any compatible MCP endpoint, it exposes connection settings (covered in detail below) and is intended for technical users rather than a one-click customer experience.
Who it's for: Internal development and testing, custom in-house assistants, and approved third-party AI agents that speak the MCP standard.
Unlike the verified connectors, the Custom MCP Connector opens a configuration dialog. It is used when a connection must point at a specific MCP server — for example an internal development or staging environment, or an approved third-party AI agent. The dialog collects the following:
| Field | What it means |
|---|---|
| Server URL | The address of the MCP server the connector talks to, ending in /mcp (for example a staging or production Coevera MCP endpoint). This is what makes the connector "custom" — the verified connectors have this baked in. |
| Client ID | The public identifier of the OAuth application the connector authenticates as. Issued when the connector is registered with the CRM. |
| Client Secret secret | The confidential password paired with the Client ID. Treated as a secret — it is masked in the dialog and must never be shared in customer-facing documents. |
| Redirect URLs | The allow-list of addresses the OAuth server may send the user back to after they sign in and approve access. Each entry is added explicitly; requests to any other address are rejected. This is a security control that prevents tokens from being delivered to an untrusted destination. |
Illustration of the configuration dialog — values shown are placeholders.
CRM › Space Administration › Automation Hub › Addons › locate the connector tile
Because it requires connection details and credentials, the Custom connector is for technical users — not part of the standard customer self-service flow.
Everything below respects the signed-in user's permissions. Rows marked reads data only look things up; rows marked changes data create or modify CRM records.
| Capability | Effect | Example |
|---|---|---|
| Ask questions about CRM data | reads data | “Which accounts in Germany have open opportunities over €50k?” The assistant searches and filters live CRM records and answers in natural language — no manual exports or report building. |
| Summarise and segment | reads data | Summarise this quarter's open pipeline, group leads by source, or list every contact at an account. The assistant reads records and synthesises them on demand. |
| Discover the data model | reads data | The assistant can list the entity types a user can see (Accounts, Contacts, Leads, Opportunities, Tasks, custom entities, …) and inspect their fields, so it always works with the customer's real schema — including custom fields. |
| Create records | changes data | “Create a follow-up task for this contact next Tuesday.” The assistant creates Contacts, Tasks, Appointments, Opportunities, and more, with the user's permissions. |
| Update records | changes data | Change a deal's close date, update a contact's phone number, or correct an account field — the assistant updates only the fields it is told to. |
| Attach documents | changes data | “Upload this signed contract to the account's Documents folder.” The assistant can file documents the user shares with it (PDFs, images, spreadsheets, …) into a CRM document folder, where they appear like any other uploaded file. Uploads happen through a short-lived, single-use link, and the file is stored under the user's own identity and permissions. Note: depending on the client application (Claude or ChatGPT), the domain *.coevera.com may need to be allowed in the app's security settings before file uploads work — see the app preferences. |
| Run business operations | changes data | Beyond simple edits, the assistant can perform real sales operations: move or archive batches of opportunities, qualify leads into opportunities, reassign ownership, and complete pipeline-step checklist requirements — each triggering the CRM's own business logic. |
documents.full permission,
which is part of the standard set the customer approves at sign-in.
*.coevera.com has to be added to the allowed domains in the app's security / network
preferences — otherwise the assistant can prepare the upload but the file never arrives. If a customer
reports that “the upload fails” while everything else works, check this setting first.crm.coevera.comWhen connecting, the customer grants the connector these CRM permissions: