Use natural language in Cursor to work with your Coralogix telemetry and platform: logs, metrics, traces, RUM, alerts, dashboards, and more—through the remote Coralogix MCP server. No local MCP binary is required; the server runs in Coralogix and you connect over HTTPS.
Full setup, authentication options, and regional endpoints are documented here:
- Install the plugin from the Cursor Marketplace (or copy this repo to
~/.cursor/plugins/local/coralogix-mcp/for local testing — see Local development). - In Cursor chat, run
/cx-setup. It will ask which Coralogix region you use and which authentication method to use (OAuth — the default — or API key), then configure the MCP server for you. - Fully quit and reopen Cursor.
- For OAuth, complete the browser login when prompted.
To change the region, switch between OAuth and API key, or rotate an API key later, run /cx-config.
- A Coralogix account and the correct region / API endpoint for your team (account domain)
- Cursor with MCP enabled
The MCP server is fully remote—there is nothing to install on your machine beyond configuring Cursor (see Setup).
You typically authenticate in one of two ways:
| Method | Notes |
|---|---|
| OAuth (recommended) | Browser login to Coralogix and authorize the MCP client. Cursor uses OAuth 2.1 / OIDC (details). |
| API key | Personal Coralogix API key sent as Authorization: Bearer …. Choose it during /cx-setup, or run /cx-config to add or rotate one. Permissions follow that key (permissions). |
The MCP URL follows the pattern https://api.<your-domain>/mgmt/api/v1/mcp. The /cx-setup skill writes the right URL into the plugin's mcp.json based on your region choice:
| Domain | Region | Cloud |
|---|---|---|
eu1.coralogix.com |
EU1 | AWS eu-west-1 (Ireland) |
eu2.coralogix.com |
EU2 | AWS eu-north-1 (Stockholm) |
us1.coralogix.com |
US1 | AWS us-east-2 (Ohio) |
us2.coralogix.com |
US2 | AWS us-west-2 (Oregon) |
us3.coralogix.com |
US3 | GCP us-central1 (Iowa) |
ap1.coralogix.com |
AP1 | AWS ap-south-1 (Mumbai) |
ap2.coralogix.com |
AP2 | AWS ap-southeast-1 (Singapore) |
ap3.coralogix.com |
AP3 | AWS ap-southeast-3 (Jakarta) |
A fresh install uses ${CORALOGIX_DOMAIN} in the MCP URL; the server can connect if that variable is already set (shell or plugin settings). /cx-setup and /cx-config replace it with a literal hostname in the URL so region changes from chat are not overridden by your session. If you already registered the Coralogix MCP server manually in ~/.cursor/mcp.json, remove or rename that entry first to avoid connecting twice.
Once connected, ask the agent questions about your observability data or platform, for example:
Show me the most frequent errors for service XYZ in the past week.
When did this issue start?
Which alerts fired in the last hour?
After investigating an incident, you can continue with follow-ups such as summarizing impact or suggesting code fixes—the agent uses Coralogix tools when they are available.
| Skill | Purpose |
|---|---|
/cx-setup |
First-time setup. Asks which Coralogix region you use and whether to authenticate via OAuth or an API key, then writes the matching config into the plugin's mcp.json. |
/cx-config |
Change region later, switch between OAuth and API key, or rotate an API key. |
If outbound traffic must go through a proxy, set standard HTTP_PROXY / HTTPS_PROXY environment variables before starting Cursor; MCP clients typically honor them (see Setup).
To load the plugin directly into Cursor without publishing it, copy the repo into Cursor's local plugin folder (docs):
make devThis copies the repo to ~/.cursor/plugins/local/coralogix-mcp/. Then reload Cursor (Cmd+Shift+P → Developer: Reload Window) and run /cx-setup in chat.
To remove the local install: make unlink.
- Coralogix MCP: Setup, OAuth, Permissions
- Endpoints: Coralogix endpoints
- Security disclosures: SECURITY.md
- License: LICENSE