Authorize MCP with OAuth 2.1

The MCP server connects directly to your Coralogix data using OAuth 2.1 with OpenID Connect (OIDC). The OAuth server issues a token to the client, which is then used to authenticate against the MCP server.

Use it to:

• Ensure MCP operates within the signed-in user’s existing access control and permissions
• Connect securely while you validate MCP behavior in a controlled team scope

This article explains how to configure and enable your MCP server to connect to Coralogix using OAuth.

What you need

You must have a client supporting automatic client registration, such as Cursor of Microsoft CoPilot, running on your machine in order to connect the MCP server using OAuth.

Configure and enable your MCP server

Set up MCP and start the OAuth flow.

1. In your mcp.json file, configure the MCP server.

   "coralogix-server": {
       "url": "https://api.https://api./mgmt/api/v1/mcp"
   }    
   

2. In your MCP client, select View: Open MCP settings.
3. Toggle to activate the server and select Connect.
4. You will be redirected to Coralogix for login (if needed) and authorization. Allow Cursor to access the Coralogix website by selecting Open.
5. Select a team, then select Allow access.

The server should now appear as enabled. If you are unsuccessful, clear all MCP tokens and try again.

If you need MCP access to another team, connect MCP again with a separate server for that team.

Security

When you approve access, Coralogix sends an authorization code to the integration. The integration exchanges that code for tokens (access_token and refresh_token) and then uses the access token to call Coralogix APIs on your behalf, limited to the requested scopes and your existing permissions.

• Your password is never shared with the MCP client.
• Your existing security policies still apply:
  • SSO and MFA requirements are enforced at login.
  • If your account is disabled or your team membership changes, your access will change accordingly.
• To protect your security, the system disconnects every hour on the hour. Reconnect your server as necessary.

Revoking access

To block MCP from accessing Coralogix, use one of these options.

From the MCP client

Many MCP clients include a Disconnect from Coralogix or Log out of Coralogix option. Use that option first when available.

From Coralogix

• Remove the user from the selected team to block access to that team.
• Adjust the user’s roles or permissions to reduce what the token can do. MCP is limited by the user’s permissions.
• Contact Support to revoke tokens associated with a specific integration if needed.

After access is blocked or tokens are revoked, the next time MCP tries to use Coralogix, it fails and prompts you to reconnect through the OAuth flow.