Developers
ChangelogSupportcoevera.comGet API keys
Set your API contextPick a region and space ID once. Every sample fills in your base URL.
Where do I find these?

In Coevera: open your space's API application and choose Show Access. It shows the space ID and the base URL, whose host starts with your region.

From the API: if you know the space ID, the discovery endpoint GET /api/discovery/spaces/{space_id} returns its region and base URLs, without credentials.

Only the region and space ID are kept, in this browser. Never paste a key or password here.

More in the quickstart

AI & MCPConnect Claude

Connect Claude

View as Markdown/ai/connect-claude.mdOpen in ClaudeAsk Claude about this pageOpen in ChatGPTAsk ChatGPT about this page

Four steps. An admin requests the Claude Connector and Coevera activates it; the user adds the server in Claude, signs in and approves the scopes.

Answer

After Coevera activates the Claude Connector for your space, add a custom connector in Claude with the server URL https://mcp-server.coevera.com/mcp, then sign in to Coevera, pick the space and approve the scopes. Only a user with the Admin API Access right in the space can approve. Claude then works within that user's access and the approved scopes.

The same server serves every client. For ChatGPT see Connect ChatGPT; for any other MCP client see Custom MCP connector.

Set up

1. An admin requests the connector in Coevera

Go to Space Administration › Automation Hub › Addons, open Claude Connector and click Request. Coevera Customer Success approves the request and activates the connector for the space. See Activate a connector.

2. Add the server in Claude

In Claude, open Settings › Connectors and add a custom connector with this server URL:

Text
https://mcp-server.coevera.com/mcp

3. Sign in and approve

Connecting opens the Coevera sign-in. The user signs in, picks a space and approves the scopes on the consent screen.

  • Only users with the Admin API Access right in the space can approve.
  • Only active spaces with an active subscription are offered.
  • File uploads, and exports that Claude downloads to analyse, need *.coevera.com in the allowed domains of Claude's network settings, because the file travels straight between Claude's environment and the server.

4. Try a first prompt

Ask something your own records can answer, for example:

Which of my opportunities close this month, and what is the next step on each?

To answer, Claude can call me to learn the user and space, then search_records on opportunities with a filter on the closing date.

What users approve

The consent screen lists the scopes the connector asks for, for example accounts.full or pipelines.read. Approving creates an application of type OAuth in the space, and Claude then works within the signed-in user's access and those scopes. The full list and what each scope grants are on OAuth and scopes.

Troubleshooting

The connector is not active yet

The connectors are in beta. After an admin clicks Request, the connector stays inactive until Coevera Customer Success approves it, and sign-in cannot complete until then.

  • The consent is refused. The user lacks the Admin API Access right in that space, or the Claude Connector is not active for it.
  • The space is not offered at sign-in. The space is not active or has no active subscription.
  • Everything works except file uploads or exports. Allow *.coevera.com in Claude. Upload and download links are single-use and expire after a few minutes, so start the upload or the export again.
  • A request fails with a rate-limit error. See Limits and errors.