Setup and installation

The MCP server is fully remote and does not require any local installation.

Staying on MCP server v1

The configuration examples below use v2, the current MCP server version. If you need to stay on v1, send the mcp-version: v1 header instead. v1 is deprecated and will be removed, so plan to migrate to v2.

Using Olly through MCP

Olly tools are hidden by default. To use them, add the x-allow-costly-use: true header to your MCP server configuration alongside mcp-version: v2. See Olly for the full setup.

Connecting with Cursor

OAuth (recommended)

Add the following to your .cursor/mcp.json file:

{
  "mcpServers": {
    "coralogix-server": {
      "url": "https://api./mgmt/api/v1/mcp",
      "headers": {
        "mcp-version": "v2"
      }
    }
  }
}

Open the MCP settings in Cursor and enable the new MCP server.
A browser window will open — log in to Coralogix and click Authorize to complete the connection.

Cursor handles authentication via OAuth 2.1 with OpenID Connect (OIDC). For more details, see Authorize MCP with OAuth 2.1.

API key

Add the following to your .cursor/mcp.json file:

{
  "mcpServers": {
    "coralogix-server": {
      "url": "https://api./mgmt/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR-API-KEY>",
        "mcp-version": "v2"
      }
    }
  }
}

Replace <YOUR-API-KEY> with a personal Coralogix API key. The MCP server inherits the permissions associated with the user's personal API key. Find out more in Permissions.

Open the MCP settings in Cursor and enable the new MCP server.

Note

If necessary, modify the https://api./mgmt/api/v1/mcp endpoint to correspond to your Coralogix domain using the domain selector at the top of the page.

Connecting with Claude Code

Configure the MCP server using the Claude Code CLI.

OAuth (recommended)

Register the MCP server:

claude mcp add --transport http coralogix-server https://api./mgmt/api/v1/mcp --header "mcp-version: v2"

Authenticate:
```
claude /mcp
```
- Select coralogix-server.
- Select Authenticate.
- A browser window will open — log in to Coralogix and click Authorize to complete the connection.

Claude Code handles authentication via OAuth 2.1 with OpenID Connect (OIDC). For more details, see Authorize MCP with OAuth 2.1.

API key

claude mcp add coralogix-server \
  --transport http \
  https://api./mgmt/api/v1/mcp \
  --header "Authorization: Bearer <YOUR-API-KEY>" \
  --header "mcp-version: v2"

Replace <YOUR-API-KEY> with a personal Coralogix API key. The MCP server inherits the permissions associated with the user's personal API key. Find out more in Permissions.

Note

If necessary, modify the https://api./mgmt/api/v1/mcp endpoint to correspond to your Coralogix domain using the domain selector at the top of the page.

Connecting with Codex

Configure the MCP server using the Codex CLI.

Selecting MCP server v2 with Codex

codex mcp add can't set custom request headers, so the commands below don't select a server version on their own. After registering, add the mcp-version header to the coralogix-server entry in ~/.codex/config.toml:

[mcp_servers.coralogix-server]
http_headers = { "mcp-version" = "v2" }

Without this header, Codex uses v1.

OAuth (recommended)

Register the MCP server:

codex mcp add coralogix-server --url "https://api./mgmt/api/v1/mcp"

Authenticate:
```
codex mcp login coralogix-server
```
A browser window will open — log in to Coralogix and click Authorize to complete the connection.

Codex handles authentication via OAuth 2.1 with OpenID Connect (OIDC). For more details, see Authorize MCP with OAuth 2.1.

API key

Set your API key as an environment variable:
```
export CORALOGIX_API_KEY="<YOUR-API-KEY>"
```
Replace <YOUR-API-KEY> with a personal Coralogix API key. The MCP server inherits the permissions associated with the user's personal API key. Find out more in Permissions.

Register the MCP server:

codex mcp add coralogix-server \
  --url "https://api./mgmt/api/v1/mcp" \
  --bearer-token-env-var CORALOGIX_API_KEY

Verify the configuration:

codex mcp list
codex mcp get coralogix-server

Note

If necessary, modify the https://api./mgmt/api/v1/mcp endpoint to correspond to your Coralogix domain using the domain selector at the top of the page.

Using a proxy for outbound connections

If your network requires a proxy for outbound connections, set the standard HTTP_PROXY / HTTPS_PROXY environment variables before running your CLI client. The MCP client picks up your system proxy settings automatically.

export HTTPS_PROXY="https://your-proxy:port"

Starting a session

Start a conversation by entering a prompt such as:

Show me the most frequent errors for service XYZ in the past week.

The assistant locates relevant log entries and identifies problematic functions.

Requesting a fix for agent-based IDEs

After identifying the issue, for agent-based IDEs such as Cursor, instruct the assistant to fix it by saying:

Now, fix the issue.

You can also ask:

When did the issue start?

Additional resources


Coralogix Endpoints	Coralogix Endpoints

Next steps

Configure and enable your MCP server to connect to Coralogix using OAuth.

Need help? Contact Support.

What's new? Find out here.

LLM? Read llms.txt.

Previous Overview

Next OAuth