Connect the Celigo MCP server to Claude and Cursor

Teena Killa

Updated August 26, 2026 16:46

You can connect AI clients like Claude, Cursor, and other MCP compatible applications to a Celigo MCP server using built in OAuth. It does not require any OAuth app registration or custom authentication setup. When your client connects, a browser window opens, you sign in, and the client receives an access token scoped to what your admin has granted you.

This article is for end users who consume MCP tools through AI clients. You don't need access to integrator.io to connect through MCP. As an end user can't sign in to integrator.io. Your access is limited to the MCP servers and capabilities assigned to them, see Set up authentication for an MCP server and Invite and manage end users.

You sign in with your Celigo end user credentials that would be the email and password you set when you accepted your invitation or through your company's identity provider if your admin has configured one for your email domain. If you're also a workspace user who builds integrations, the credentials are the same either way, what changes is which tools you get access to afterward.

This article also covers the supported MCP clients, how to find your MCP server URL, how the sign in flow works, per client setup steps, connecting with an API token when OAuth isn't an option, and common troubleshooting.

Prerequisites

You must be an end user with access to the MCP server: Your admin either invited you (check your email for an invitation from Celigo, see Connect to a Celigo MCP server as an end user for account setup) or, if your company signs in through an identity provider using JIT (just in time) provisioning, your end-user record is created automatically the first time you connect. Access to specific servers and tools is granted by your admin through end user groups and direct assignments.
Workspace access alone doesn't grant MCP access: Being an administrator in integrator.io doesn't let you use MCP servers, only the account owner connects without an end-user record. If you're an admin who wants to use MCP tools, invite yourself as an end user and grant yourself access like anyone else.
You need the MCP server URL: Your admin provides it.
Your MCP client must support remote MCP servers: See Supported MCP clients for the requirements and the list of verified clients. Clients that don't support OAuth can connect with an API token instead.
If you connected before end users were introduced: MCP access used to be granted to workspace users on each server's user list. Access is now managed through end user records, groups, and capability assignments. If a connection that used to work now returns an authorization error, ask your admin to confirm your end-user access.

Supported MCP clients

Celigo MCP servers are remote servers using the streamable HTTP transport with OAuth 2.1 (PKCE and dynamic client registration). Any client that supports those can connect with OAuth. Clients that instead let you set a custom Authorization header can connect with an API token:

Web apps

Client	Notes
Claude.ai	Add as a custom connector under Settings > Connectors. Available on all plans. Free accounts are limited to one custom connector. On Team and Enterprise plans, an Owner adds the connector first.
ChatGPT	Requires Developer mode (available on Plus, Pro, Business, Enterprise, and Edu, not free). OpenAI currently limits custom connectors on Plus and Pro plans to read-only tools. Write capable tools require a Business, Enterprise, or Edu workspace.

Desktop / IDE (Integrated development environment)

Client	Notes
Claude Desktop	Same custom connector mechanism as Claude.ai. Go to Settings > Connectors. No proxy or config file needed.
Cursor	Configured in mcp.json with the server URL. OAuth sign-in opens in your browser.
VS Code + Copilot	Added with the MCP: Add Server command. Requires VS Code 1.101 or later for remote MCP servers with OAuth.
Windsurf	Configured in mcp_config.json using the serverUrl field.

CLI (Command line interface)

Client	Notes
Claude Code	Native streamable HTTP support, one command to add, then authenticate in your browser.
OpenAI Codex CLI	Configured in config.toml. OAuth requires the experimental RMCP client flag.
Gemini CLI	Added with gemini mcp add --transport http.

If your client isn't listed, it can still connect as long as it supports the streamable HTTP transport and OAuth 2.1 with PKCE.

Find your MCP server URL

End users get the MCP server URL from their admin as they can't sign in to integrator.io to look it up.

Admins can find it in integrator.io:

Go to AI studio > MCP servers and select the MCP server.
On the Configuration tab, find the Relative URI field.
The full MCP server URL is the base URL plus the relative URI. For example: https://api.integrator.io/mcp/your-account-alias/your-server-name

Field reference

Relative URI: The MCP server's path segment, shown on the server's Configuration tab. Combine it with the base URL (https://api.integrator.io) to form the full MCP server URL.

Copy this URL. You'll enter it in your MCP client when you connect, in the client-specific steps later in this article.

How sign in works

When you connect an MCP client to a Celigo MCP server, the following happens:

Your MCP client starts an OAuth connection to the MCP server URL.
A browser window opens with the Celigo sign in page, which asks for your email address.
Celigo routes you based on your email domain:
- If your domain matches an identity provider your admin configured, you're redirected to your company's sign in page (for example, Okta or Microsoft Entra ID). Sign in with your work credentials. If your company requires an MFA, you complete it there. If JIT (just-in-time) provisioning is on and this is your first connection, your end-user record is created automatically with no invitation needed.
- Otherwise, you sign in with Celigo credentials, the email and password from your account setup. Sign in with Google is also available. If your admin requires MFA, you're prompted to enter a verification code, or to enroll with an authenticator app on your first sign in.
After you sign in and approve the connection, the browser redirects back to your MCP client with a valid access token. The tools your admin has granted you appear in the client.

Access tokens expire after 1 hour. Your client uses a refresh token, valid for 14 days, to get new access tokens without asking you to sign in again, most clients handle this automatically. If the server goes unused long enough for the refresh token to expire, you sign in again.

If the browser opens your identity provider's page directly, with no Celigo sign in page first, the MCP server is configured for Token validation. In that mode your organization's IdP handles the connection end to end, and the end user sign in described in this article doesn't apply. Check with your admin.

Known limitations with Token validation

The following provider limitations apply only when the MCP server's Type is set to Token validation on its Access tab, not to end user sign in through Celigo, where Okta, Entra ID, and Google all work:

Auth0: works when the Resource Parameter Compatibility Profile is enabled in Auth0.
Microsoft Entra ID: currently unsupported for direct MCP OAuth because it doesn't support the resource parameter in authorization requests.
Google Identity: currently unsupported because it may reject the MCP server's requested scopes.

If you have issues with a server in Token validation mode, contact your account admin.

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.

Claude.ai and Claude Desktop use the same mechanism: custom connectors. Custom connectors are available on every Claude plan. Free accounts are limited to one.

Perform the following steps to add your MCP server to Claude on a Free, Pro, or Max plan:

Open Claude (web or desktop) and go to Settings > Connectors.
Select Add custom connector.
Enter a Name and paste the MCP server URL.
Select Add, then Connect.
A browser window opens with the Celigo sign in page (or your company's sign in page). Sign in with your credentials.
When the browser prompts you to return to Claude, select Open Claude. The MCP server's tools are now available in your conversations.

On a Team or Enterprise plan, an owner adds the connector first under Organization settings > Connectors, entering the same URL. Each member then goes to Settings > Connectors, finds the connector, and selects Connect to sign in with their own credentials.

Note: Claude connects to custom connectors from Anthropic's cloud, not from your device. The same connector works across Claude.ai, Claude Desktop, and Claude mobile once added.

Connect from Claude Code

Add the server from your terminal:

claude mcp add --transport http celigo-mcp YOUR_CELIGO_MCP_URL

Then authenticate: run /mcp inside a Claude Code session and select the server to start the browser sign-in, or run claude mcp login celigo-mcp from your shell. Claude Code stores the token securely and refreshes it automatically.

Connect to MCP server from Cursor desktop

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

Open Cursor and on the top right click Settings.
Select Tools and MCPs in the left pane menu.
Seletc New MCP Server to open the mcp.json file. you can also edit ~/.cursor/mcp.json directly
Add the MCP server URL provided by your Celigo admin and close the json page to save it. For example:
```
{
  "mcpServers": {
    "celigo": {
      "url": "YOUR_CELIGO_MCP_URL"
    }
  }
}
```
The MCP server appears in the Installed MCP server list. Select Connect.
When Cursor prompts you to authenticate the server, a browser window opens with the Celigo sign in page (or your company's sign-in page). Sign in.
When the browser prompts you to open Cursor, select Open Cursor.
Cursor connects to the MCP server and all the server's tools are now available.

Connect to MCP server from other MCP clients

Any MCP-compatible client that supports remote servers over streamable HTTP with OAuth 2.1 (PKCE and dynamic client registration) can connect:

Locate the MCP server connection settings in your client.
Enter the MCP server URL your admin provided.
Complete the Celigo (or your company's) sign in flow in the browser window that opens.
Confirm the connection is established in your client.

If your client doesn't support OAuth, use an API token instead. If you're unsure how to configure an MCP server in your client, check that client's documentation.

Additional supported clients

Connect from VS Code + Copilot

If you're in an organization with Copilot Business or Enterprise, your admin must have the "MCP servers in Copilot" policy enabled before you can add a remote server.

Open VS Code and make sure GitHub Copilot is installed and active. Remote MCP servers with OAuth require VS Code 1.101 or later.
Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and run MCP: Add Server.
Select HTTP as the server type and enter the MCP server URL.
When prompted to authenticate, complete the Celigo sign in flow in the browser window that opens.
The server's tools are available to Copilot in agent mode.

Connect from Windsurf

Open Windsurf's settings and select Add Server, or edit ~/.codeium/windsurf/mcp_config.json directly.

Windsurf uses serverUrl (not url) for remote servers:

}
  "mcpServers": {
    "celigo": {
      "serverUrl": "YOUR_CELIGO_MCP_URL"
    }
  }
}

Save and refresh the MCP list, then complete the Celigo sign in flow in the browser window that opens.

Connect from ChatGPT

Custom MCP connectors in ChatGPT require Developer mode, available on Plus, Pro, Business, Enterprise, and Edu plans. On Plus and Pro, OpenAI currently limits custom connectors to read-only tools, write-capable tools require a Business, Enterprise, or Edu workspace, where an admin may need to enable Developer mode for you.

ChatGPT's setup flow changes frequently. Confirm the steps below against OpenAI's current documentation before you begin.

In ChatGPT's settings, turn on Developer mode (under Security and login).
Create a new connector with the MCP server URL and select OAuth as the authentication method.
Complete the Celigo sign in flow in the browser window that opens.
Enable the connector in a conversation to use its tools.

Connect from OpenAI Codex CLI

Add the server to ~/.codex/config.toml. OAuth requires Codex's experimental RMCP client, and the flag must appear above the server tables:

experimental_use_rmcp_client = true
[mcp_servers.celigo]
url = "YOUR_CELIGO_MCP_URL"

Then run codex mcp login celigo to start the browser sign-in. Check the Codex documentation for the latest MCP configuration options -- the flag is experimental and may change.

Connect from Gemini CLI

To add the server, the --transport http flag is required, because Gemini CLI defaults to local servers:

gemini mcp add --transport http celigo-mcp YOUR_CELIGO_MCP_URL

Then authenticate with gemini mcp auth celigo-mcp (or run /mcp auth celigo-mcp inside a session). A browser window opens for the Celigo sign in flow.

Connect using an API token

If your MCP client doesn't support OAuth, or you're connecting a non interactive service like a CI/CD pipeline or automation script, use an API token instead.

Ask your admin for a token. Admins can create them in integrator.io. Go to AI studio > MCP servers, select the MCP server, open the Access tab, select API tokens, and select Create token. The token is similar to a password, anyone who has it can use the server with the token's access.

Field reference

Auto purge: How long the token remains valid before it's automatically revoked. Accepted values: 1 hour to 30 days, or never (no automatic expiration). Admins can also revoke a token manually at any time.

Configure your client to send the token as a bearer header:

For example:

Authorization: Bearer YOUR_API_TOKEN

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 sign in

You authenticated successfully, but the MCP server returned an authorization error. Signing in doesn't grant access. Your end user record doesn't have access to this specific MCP server, then ask your admin to add you to a group with access to it, or to grant you direct access. Being an admins doesn't grant MCP access, only the account owner connects without an end user record.

Missing or stale tools

You signed in successfully, but the tools you expect aren't showing up, or the list looks out of date. Start a new chat first, an AI chat only sees the tools that existed when it began, so access your admin granted a minute ago won't appear in an open conversation. If a new chat doesn't help, restart your client (most clients only read their server configuration at startup), then disconnect and reconnect the server. Celigo applies access changes on your very next tool call, so if the tools still don't match what your admin granted, the grant itself is worth re-checking.

The browser window doesn't open

Some MCP clients use redirect URIs like http://127.0.0.1:PORT/callback or custom protocol handlers. Make sure your browser isn't blocking pop-ups or redirects from Celigo, and check that your MCP client is up to date.

Unexpected sign in page

Celigo routes end users by the email domain they enter, so this is usually configuration, not an error:

You expected a Celigo password page but were sent to your company's sign-in: Your email domain is routed to an identity provider your admin configured. Sign in with your work credentials.
You expected your company's sign-in but got a Celigo password page: Check the email address you entered. A personal address won't route to your company's provider. If the address is right, your admin may not have configured an identity provider for that domain.
Your identity provider's page opened directly, with no Celigo page first: The MCP server is configured for Token validation. That's a different setup, check with your admin.

Redirect loop with your company's sign in

If you bounce between Celigo and your identity provider without landing back in your client, your IdP session may be stale. Confirm you can sign in to another app protected by the same provider, then retry the connection. If the loop persists, contact your admin or IT team to check the identity provider configuration. As an end user, if you try to sign in to integrator.io, you'll see an error because end users don't have access to integrator.io. This is expected and doesn't indicate an issue with your account.

Token expired

Access tokens expire after 1 hour, and most clients refresh them automatically. If your client loses the connection after about an hour, check that it supports OAuth refresh tokens. Reconnecting manually or repeating the sign in flow can also resolves it.

Your invitation link doesn't work

Invitation links expire 7 days after they're sent. Ask your admin for a new invitation. Admin requires to remove your end user record and invite you again, since re-inviting the same address without removing is rejected. See Invite end users to your Celigo account.