---
title: "Adding the CTERA MCP Server to an AI Agent"
slug: "using-the-ctera-mcp-server-1"
tags: ["MCP", "Cursor", "Claude", "Portal", "8.4"]
updated: 2026-11-09T15:36:11Z
published: 2026-11-09T15:36:11Z
canonical: "kb.ctera.com/using-the-ctera-mcp-server-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding the CTERA MCP Server to an AI Agent

The MCP client, such as Claude Desktop, used to communicate with CTERA MCP Server, must be configured for secure access to the CTERA MCP Server. Once connected, the MCP client will be able to perform actions on the specific portal which has the CTERA MCP Server enabled. Security is enabled using OAuth 2.0. All access to the CTERA MCP Server is authorized by OAuth 2.0.

## Configuring Access to the CTERA MCP Server

You configure access to the CTERA MCP server after [enabling AI integrations](/v1/docs/setting-up-the-mcp-server-service-1).

1. In the global administration view, select **AI Content Services > AI Integrations** in the navigation pane.  

The **AI Integrations** page is displayed.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-XRHF2DSD.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A07%3A30Z&se=2026-11-11T05%3A07%3A30Z&sr=c&sp=r&sig=FUKMtgz%2FK94vxCz2bdby6ZGuG%2FVhvBFcgZRjqeD1ktk%3D)
2. Click **Settings**.  

The **Settings** page is displayed.  

![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ASF1NRNZ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A07%3A30Z&se=2026-11-11T05%3A07%3A30Z&sr=c&sp=r&sig=FUKMtgz%2FK94vxCz2bdby6ZGuG%2FVhvBFcgZRjqeD1ktk%3D)
3. Copy the Portal URL suffix from the **Settings** page.  

You will use this URL suffix when setting up the AI agent connection to the CTERA MCP server.
4. In your Idp (Identity Provider) software, define the Oauth 2 users and roles.
5. On the primary, database, portal server, edit `portal-oauth2-proxy.env`, in `/etc/oauth2-proxy` to set up the portal.
  1. Under **PROVIDER CONFIGURATION (Environment-Specific)** make the following changes:  

**OAUTH2_PROXY_PROVIDER_DISPLAY_NAME** – The Idp name. For example, `"EntraID"` when using Microsoft Azure Entra ID.  

**OAUTH2_PROXY_OIDC_ISSUER_URL** – The URL for the OIDC provider.  

**OAUTH2_PROXY_CLIENT_ID** – The client ID, from the Idp.  

**OAUTH2_PROXY_CLIENT_SECRET** – The client secret key, from the Idp.
  2. Under **Populate Only PORTAL_HOST for IDP Redirect** change **OAUTH2_PROXY_REDIRECT_URL** to the URL to the portal/oauth2/callback. For example, `https://myportal.ctera.me/oauth2/calback` where *myportal* is the default portal.
  3. Under **SECURITY SECRETS** change **OAUTH2_PROXY_COOKIE_SECRET** to the cookie secret key.
6. Run `systemctl restart portal-oauth2-proxy` to commit these changes.
7. In the AI Agent, add a connector using the portal name and portal suffx that you noted from the **Settings** page.

## CTERA MCP and Claude

In Claude, under **Organization settings** and click **Add custom connector** to add the CTERA MCP Server. Specify the following and then click **Add**:

- **Name** – A name for the connector.
- **Remote MCP server URL** – The CTERA MCP server endpoint: `mcp_endpoint` where *mcp-endpoint* is the system assigned **Portal URL** value in **MCP Server > Settings**. For example, `myportal.example.com/mcp`
- **OAuth Client ID (optional)** – The client ID, from the Idp f(Identity Provider).
- **OAuth Client Secret (optional)** – The  client secret key from the Idp (Identity provider).