---
title: Custom MCP connector
description: Connect any other MCP client through the MCP Connector tile. Coevera issues the client ID and secret; you add your client's redirect URLs.
canonical: https://developers.coevera.com/ai/custom-connector/
section: ai
publisher: Coevera
---

# Custom MCP connector

**Answer:** For an MCP client other than Claude or ChatGPT, request the MCP Connector tile. Once Coevera activates it, its configuration dialog shows the server URL, a client ID and a client secret; you add your client's redirect URLs. Your client then signs users in with the OAuth 2.0 authorization code flow with PKCE (S256).

Use the MCP Connector for developers' own clients, in-house assistants and approved third-party
agents. It is meant for technical users; Claude and ChatGPT have their own connectors that need no
configuration ([Connect Claude](/ai/connect-claude/), [Connect ChatGPT](/ai/connect-chatgpt/)).

## Before you begin

- The **MCP Connector** is active for the space. An admin requests it under **Space
  Administration › Automation Hub › Addons** and Coevera Customer Success activates it; see
  [Activate a connector](/ai/activation/).
- Your MCP client supports remote servers over Streamable HTTP and the OAuth authorization code
  flow with PKCE, with a pre-registered client. The server does not offer dynamic client
  registration.

## Configure the connector

Open the **MCP Connector** tile in the Automation Hub. Its dialog, **OAUTH2 MCP Server -
configure**, has three parts.

**Credentials**, each with a copy button:

| Field         | Use it as                                                                                                |
| ------------- | -------------------------------------------------------------------------------------------------------- |
| Server URL    | The MCP endpoint your client connects to                                                                 |
| Client ID     | Your client's OAuth client ID                                                                            |
| Client Secret | Your client's OAuth client secret. It is masked; show it only to copy it into your client's secret store |

The server URL is:

```text
https://mcp-server.coevera.com/mcp
```

**Redirect URLs.** The list starts with the predefined redirect URLs of the supported AI
clients. Add your client's callback URL, for example `https://agent.example.com/oauth/callback`.
The list is an allow-list: an authorization request with any other redirect URL is refused.

**Permissions Scopes.** The dialog lists an access level per scope: **Full Access**, **Read
Only** or **No Access**. In release 6.5 a change made there is not saved. The server lists all 15
scopes on [OAuth and scopes](/ai/oauth-and-scopes/) as required, so have your client request all
of them: a token that lacks a required scope is answered `403`.

Save the dialog, then configure your client.

## Configure your client

Give your client:

- the server URL above;
- the client ID and client secret, sent to the token endpoint as `client_secret_basic` or
  `client_secret_post`;
- PKCE with the `S256` method.

The client can read the endpoints from the server's discovery document:

```text
https://mcp-server.coevera.com/.well-known/oauth-authorization-server
```

A request without a valid token is answered `401` with a `WWW-Authenticate` header that points to
`https://mcp-server.coevera.com/.well-known/oauth-protected-resource`, so clients that follow
RFC 9728 find the authorization server on their own.

Clients that call the server directly must send `Accept: application/json, text/event-stream`,
or the server answers `406`.

## Sign in and approve

The first connection opens the Coevera sign-in. The user signs in, picks a space and approves the
scopes. Only users with the **Admin API Access** right in the space can approve, and only active
spaces with an active subscription are offered.

## 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 authorization request is refused.** Check that the redirect URL your client sends is in
  the dialog's list, exactly as written.
- **`406 Not Acceptable`.** Send `Accept: application/json, text/event-stream`.
- **Uploads or export downloads fail.** The file travels straight between your client's
  environment and the server's upload or download address: allow outbound requests to
  `*.coevera.com`.