Skip to main content

Coralogix MCP

The Coralogix Model Context Protocol (MCP) server lets external AI agents access and analyze Coralogix observability data—logs, metrics, and traces—via a remote streamable HTTP interface. Use it from Cequence AI Gateway to support AI-native troubleshooting and root cause analysis directly from your IDE or AI client.

1. Overview​

Coralogix MCP is a remote, vendor-hosted MCP server. You connect to it from Cequence AI Gateway; the server uses Streamable HTTP and can be reached at a region-specific endpoint.

  • Server URL (template): https://api.{region}.coralogix.com/mgmt/api/v1/mcp
  • Default region: us2. Other regions: us1, eu1, eu2, ap1, ap2, ap3, cx-ind-1 (see Coralogix domain).
  • Transport: HTTP (Streamable HTTP)
  • Hosted by: Coralogix

The server is fully remote and does not require local installation. It bridges your AI tooling and Coralogix telemetry so you can investigate issues and get fix suggestions without extra project configuration.

2. Supported authentication types​

TypeSupportedNotes
OAuth 2.0YesRecommended for Cequence AI Gateway. OAuth 2.0 with Dynamic Client Registration (DCR). You can also use OAuth 2.1 with OpenID Connect (OIDC) for MCP authorization.
API keyYesPersonal Coralogix API key in the Authorization: Bearer <key> header. Scoped per user (least-privilege). Useful for direct integration (e.g. Cursor) or when OAuth is not used.

When you add Coralogix MCP in Cequence AI Gateway, authentication is typically OAuth 2.0 with DCR. If you use API key instead, the MCP server inherits the permissions of that user’s personal API key. See MCP Permissions.

3. What can you do with this MCP server​

With the Coralogix MCP server, you can:

  • Query logs, metrics, and traces — Access and analyze observability data from your Coralogix account.
  • Execute DataPrime queries — Run DataPrime queries with formatting optimized for Cursor and similar tools.
  • Investigate issues from your IDE — Perform root cause analysis and explore telemetry without leaving your editor.
  • Receive AI-generated fix suggestions — Get fix suggestions based on your code and observability data (e.g. “Show me the most frequent errors for service XYZ in the past week” then “Now, fix the issue”).
  • Start sessions with natural language — Ask when an issue started, which functions are problematic, or for summaries of errors and logs.

Access is scoped per user, auditable, and designed to be safe and compliant. See Coralogix MCP Server Overview and Tools (logs, metrics, traces, reference) for full capabilities.

4. Prerequisites​

Before adding Coralogix MCP in Cequence AI Gateway, ensure you have:

  • Access to Cequence AI Gateway (e.g. beta.aigateway.cequence.ai)
  • A Coralogix account with the data you want to query (logs, metrics, traces)
  • Node.js installed if you use mcp-remote or other local proxy for clients that do not support remote MCP
  • For OAuth authentication: an auth app with client credentials in your vendor account, unless the server supports Dynamic Client Registration (DCR). Coralogix MCP supports DCR for OAuth.
  • For API key: a personal Coralogix API key with the permissions you need; the MCP server inherits that key’s permissions.

If your Coralogix deployment uses a specific region/domain (e.g. EU1, AP1), have that region value ready; you may need to set it when creating the MCP server in the gateway (e.g. eu1, us2).

5. Example workflows​

  • “Show me the most frequent errors for service XYZ in the past week.”
  • “When did the issue start?”
  • “Now, fix the issue.” (for agent-based IDEs like Cursor, after the assistant has identified the problem)
  • Run a DataPrime query to aggregate or filter logs, metrics, or traces from your Coralogix account.

6. Connecting MCP server from Cequence AI Gateway​

  1. Log in to Cequence AI Gateway.
  2. Choose your tenant.
  3. Go to App catalogue.
  4. Filter by Remote MCP server.
  5. Search for Coralogix MCP and then select it.
  6. Click Create MCP server.
  7. Choose auth method. If OAuth, you need an auth app with client credentials in your vendor account (see Prerequisites). If using API key, configure the Coralogix API key as required by the gateway.
  8. If prompted, set the region (e.g. us2, eu1) so the server URL matches your Coralogix domain.
  9. Complete the setup as prompted, select tools, and deploy.

Use the generated MCP server URL in your client as described in the Client Configuration docs. For detailed UI steps and screenshots, see Create a third-party MCP Server.

7. Additional information​