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.

Only those tools listed in the MCP Server Settings page are availble, such as creating an item, copying, moving, or renaming an item.

Configuring Access to the CTERA MCP Server

1. In the global administration view, select Services > MCP Server in the navigation pane.
   The MCP Server page is displayed.
   
2. Click Settings.
   The Settings page is displayed.
   
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_DIAPLAY_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 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.