Articles in this section

Connect the Celigo MCP server to Claude and Cursor

Teena Killa
Updated

Connect AI tools like Claude (desktop), Cursor (desktop), or any MCP-compatible client to Celigo in minutes using built-in OAuth without any custom authentication setup required. Celigo uses your existing integrator.io login (email, Google, or SSO) to provide a fast, secure connection without manual OAuth app configuration.

Learn how to connect from Claude and Cursor, explains the OAuth sign-in flow, and outlines common troubleshooting steps.

Prerequisites

  • You must have a Celigo MCP server. If you do not have access, ask your account admin to add you to the MCP server.

  • The MCP server must use Celigo as the identity provider (the default) or an external IdP that your account admin configured.

  • Your MCP client (such as Claude or Cursor) must support MCP client OAuth specification.

Known provider compatibility limitations

If your admin has configured an external identity provider, be aware of the following:

  • Auth0: Works when the Resource Parameter Compatibility Profile is enabled in Auth0

  • Microsoft entra ID: Currently unsupported for MCP OAuth because it does not support the resource parameter in authorization requests

  • Google identity: Currently unsupported because the requested MCP server's scopes may be rejected by Google Identity

If you encounter issues with an external IdP, contact your account admin.

Supported MCP clients

Celigo MCP servers use the streamable HTTP transport with OAuth 2.1 (PKCE). The following clients are compatible:

Web apps

Client

Notes

Claude.ai

Streamable HTTP with OAuth. Add as a custom connector via Settings.

ChatGPT

Streamable HTTP with OAuth. Requires ChatGPT Plus, Pro, or Enterprise.

Copilot Studio

Streamable HTTP with OAuth 2.0 and dynamic client registration.
Desktop / IDE (Integrated development environment)

Client

Notes

Cursor

Streamable HTTP + SSE.

VS Code + Copilot

Streamable HTTP. Auto-discovers MCP servers.

Claude Desktop

Supports direct connection (custom connector) and mcp-remote proxy.

Windsurf

Streamable HTTP + SSE.
CLI (Command line interface)

Client

Notes

Claude Code

Streamable HTTP natively. No proxy needed.

OpenAI Codex CLI

Streamable HTTP. Uses TOML config. Requires rmcp_client flag.

Gemini CLI

Streamable HTTP. No web app support for custom MCP servers yet.

OAuth sign-in flow overview

When you connect an MCP client to a Celigo MCP server that uses Celigo authentication, the following sequence occurs:

Note

If the MCP server is configured with an external identity provider, the browser redirects you to that provider’s sign-in page instead of Celigo.

  • Your MCP client initiates an OAuth connection using the MCP server URL.

  • A browser window opens and takes you to the Celigo sign-in page.

  • You sign in with your Celigo credentials. If SSO is enabled, you’re redirected to your organization’s provider (for example, Google Workspace or Okta) and then back to Celigo.

  • After successful authentication, you’re redirected back to your MCP client with a valid access token.

  • The MCP client uses this access token to communicate with the MCP server. The token expires after 1 hour. A refresh token is used to maintain the session without requiring you to sign in again and expires after 14 days.

Connect to MCP server from Claude desktop

You can add your MCP to Claude desktop in two ways:

  • Open Claude desktop and go to Settings → Developer

    1. Click Edit config to open the mcp.json file.

    2. Enter the MCP server URL provided by your Celigo admin and close the json file.

      For example:

      {
  "mcpServers": {
    "YOU_MCPSERVER_NAME": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "YOUR_CELIGO_MCP_URL"
      ]
    }
  }
}

    3. Restart Cluade to view the MCP server under Edit config section.

    4. Click Connect.

    5. The system redirects you to the Celigo (or external identity provider) sign-in page.

    6. Sign in with your credentials.

    7. When the browser prompts you to open Cluade, select Open Claude.

    8. Claude connects to the MCP server.

  • Open Claude desktop and go to Settings → Connectors

    Claude_MCP_server_connectors.png

    1. Click Add custom connectors.

      connector_add__custom_MCP.png

    2. In the Name field, enter a name for the MCP connector.

    3. In the Remote MCP server URL field, paste the MCP server URL provided by your Celigo admin.

    4. Click Add. The MCP server is listed under Installed MCP servers list.

    5. Click Connect.

    6. The system redirects you to the Celigo (or external identity provider) sign-in page.

    7. Sign in with your credentials.

    8. When the browser prompts you to open Claude, select Open Claude.

    9. Claude connects to the MCP server.

Connect to MCP server from Cursor desktop

Perform the following steps to add your MCP server to Cursor:

  1. Open Cursor and on the top right click Settings.

  2. Click Tools and MCPs in the left pane menu.

  3. Click New MCP Server to open the mcp.json file.

    cursor_new_MCP_.png

  4. Enter the MCP server URL provided by your Celigo admin and close the json page.

    For example:

    "YOUR_MCP_NAME": {
"type": "streamableHttp",
"url": "YOUR_CELIGO_MCP_URL"
}

  5. The MCP server appears in the Installed MCP server list. Click Connect.

    cursor_MCP_connect.png

  6. The system redirects you to the Celigo (or external identity provider) sign-in page.

  7. Sign in with your credentials.

  8. When the browser prompts you to open Cursor, select Open Cursor.

  9. Cursor connects to the MCP server.

Connect to MCP server from other MCP clients

Any MCP-compatible client that supports OAuth 2.1 with PKCE can connect to a Celigo MCP server. Perform the following steps:

  1. Locate the MCP server connection settings in your client.

  2. Enter the MCP server URL provided by your Celigo admin.

  3. Provide authentication using one of the following methods:

    • Enter an API token (available under Home → Resources → API Tokens)

    • Use OAuth to authenticate (available under Home → MCP servers → server → Access tab → Authentication)

  4. Complete the Celigo (external provider) sign-in flow in the browser window that opens.

  5. Confirm the connection is successfully established in your client.

Additional supported clients

Claude.ai (web)

  1. Go to claude.ai and open Settings.

  2. Under Integrations or MCP servers, select Add custom connector.

  3. Enter the MCP server URL.

  4. Complete the Celigo sign-in flow in the browser window that opens.

  5. The MCP server's tools are now available in your conversations.

VS Code + Copilot

  1. Open VS Code and make sure GitHub Copilot is installed and active.

  2. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and search for MCP: Add Server.

  3. Select HTTP as the server type and enter the MCP server URL.

  4. Complete the Celigo sign-in flow in the browser window that opens.

Windsurf

  1. Open Windsurf and go to Settings → MCP.

  2. Select Add Server and enter the MCP server URL.

  3. Complete the Celigo sign-in flow in the browser window that opens.

Claude Code (CLI)
claude mcp add celigo-mcp --transport http YOUR_CELIGO_MCP_URL

When you first use the server, a browser window opens for authentication. Claude Code stores and refreshes the token automatically.

OpenAI Codex CLI

Add to your codex.toml or .codex/config.toml:

[[mcp_servers]]
name = "celigo-mcp"
url = "YOUR_CELIGO_MCP_URL"
transport = "http"

Note

Codex CLI may require the rmcp_client flag to be enabled. Check the Codex documentation for the latest MCP configuration options.

Gemini CLI
gemini mcp add celigo-mcp YOUR_CELIGO_MCP_URL

Note

Gemini CLI supports custom MCP servers in the CLI only. Web app support for custom MCP servers is not yet available.

Connect using an API token

If your MCP client does not support OAuth, or if you are connecting to a non-interactive service, you can use an API token instead.

  1. Ask your Celigo admin to generate an API token from the MCP server's Access tab.

  2. In your MCP client, set the required headers, for example: "Authorization": "Bearer 181667f7161a464f802e8e61d14d74cb".

    For example:

    {
  "mcpServers": {
    "qaprod": {
      "url": "https://api.qaprod.staging.integrator.io/mcp/automation-tools-server-3",
      "headers": {
        "Authorization": "Bearer 181667f7161a464f802e8e61d14d74cb"
      }
    }
  }
}

  3. After configuring the headers and saving the MCP configuration JSON file, the MCP client connection is established.

API tokens expire based on the configuration set by your admin during creation and your admin can revoke tokens at any time.

API token configuration by client

Cursor
{
  "mcpServers": {
    "celigo": {
      "url": "YOUR_CELIGO_MCP_URL",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
Claude Code
claude mcp add celigo-mcp --transport http \
  --header "Authorization: Bearer YOUR_API_TOKEN" \
  YOUR_CELIGO_MCP_URL
VS Code + Copilot

add to .vscode/mcp.json or workspace mcp.json:

{
  "servers": {
    "celigo": {
      "type": "http",
      "url": "YOUR_CELIGO_MCP_URL",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Troubleshoot connection issues

Authorization error after signing in

You authenticated successfully, but the MCP server returned an authorization error. This means your Celigo account does not have access to this specific MCP server. Ask your account admin to add you to the MCP server's user list.

Browser window does not open

Some MCP clients use redirect URIs like http://127.0.0.1:PORT/callback or custom protocol handlers (for example, mcp://cursor/auth). Verify your browser is not blocking pop-ups or redirect URIs from Celigo. Check that your MCP client is up to date.

SSO redirect loop

If your Celigo account uses SSO and you are stuck in a redirect loop between Celigo and your SSO provider, verify that your SSO session is active by signing in to integrator.io directly. If that works, try the MCP connection again. If the problem persists, contact your IT admin to check the SSO configuration.

Token expired

Access tokens expire after 1 hour. Most MCP clients handle token refresh automatically using the refresh token. If your client loses the connection after about an hour, check that it supports OAuth refresh tokens. Reconnecting manually (repeating the sign-in flow) also resolves the issue.

Unexpected identity provider

If you are directed to an unexpected sign-in page (for example, an Okta page when you expected Celigo), the MCP server might be configured with an external identity provider. Check with your admin to confirm which identity provider is configured for the server.