Coralogix MCP server

What the model can do

Coralogix observability: cases (title, status, priority, category, impacted services, labels, when acknowledged and resolved) and their timeline, incidents (severity, state, status, application and labels), and SLOs with their targets; when you ask, can comment on cases, acknowledge or unacknowledge them, assign or unassign them, set or clear a priority override, rename them, resolve or close them, and acknowledge, assign, resolve or close incidents by id.

Reads

• coralogix_list_casesCoralogix cases: readable id, title, status (active, acknowledged, resolved, closed), priority P1 to P5, category, whether assigned…
• coralogix_get_caseOne Coralogix case by its UUID or readable id (CASE-123): status, priority (and whether overridden), category, impacted services, labels…
• coralogix_case_timelineWhat happened on a Coralogix case, in order: each event's kind (comment, status change, assignment, priority change…), when, and what kind of actor…
• coralogix_list_incidentsCoralogix incidents: name, description, severity, state (triggered or resolved), status (triggered, acknowledged, resolved), muted, whether assigned…
• coralogix_get_incidentOne Coralogix incident by id: severity, state, status, muted, timings, number of events and labels.
• coralogix_list_slosCoralogix SLOs: name, description, target percentage, time frame, type (request- or window-based), labels, created and updated.

Acts, when you ask

These change something in Coralogix. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• coralogix_comment_on_caseAdds a comment to a Coralogix case, shown on its timeline to everyone who can see the case (and to any integration the case is synced with).
• coralogix_acknowledge_caseAcknowledges a Coralogix case (marks that someone is on it), or with undo removes the acknowledgement.
• coralogix_assign_caseAssigns a Coralogix case to the user id given (a UUID), or with unassign removes the assignee.
• coralogix_set_case_priorityOverrides a Coralogix case's computed priority with P1 to P5, or with clear removes the override so the computed priority applies again.
• coralogix_update_caseChanges a Coralogix case's title or resolution reason; only the fields passed change.
• coralogix_resolve_caseMarks a Coralogix case resolved, with an optional reason.
• coralogix_close_caseCloses a Coralogix case that no longer needs action; it leaves the open queue.
• coralogix_acknowledge_incidentsAcknowledges the Coralogix incidents with the ids given (at most 50).
• coralogix_assign_incidentsAssigns the Coralogix incidents with the ids given (at most 50) to the user id given.
• coralogix_resolve_incidentsMarks the Coralogix incidents with the ids given (at most 50) resolved.
• coralogix_close_incidentsCloses the Coralogix incidents with the ids given (at most 50; never "all").

Connect it

First connect Coralogix on Dashboard → Connections, then add Memtro to your client once. The Coralogix tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Coralogix connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which P1 cases are still unacknowledged?
• › What happened on CASE-123 since it opened?
• › Which incidents are triggered for the payments application?
• › What is the target on our checkout latency SLO?
• › Acknowledge CASE-123 and assign it to me.

Questions

Is this an official Coralogix MCP server?

No. It is Memtro's MCP server with Memtro's Coralogix connector behind it: the connector reads Coralogix through its API with the credentials you connect on Dashboard → Connections, and Coralogix publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Coralogix?

Only when you ask, and only what it has been granted: comment on a case; acknowledge or unacknowledge a case; assign or unassign a case; set or clear a case's priority override; rename a case or change its resolution reason; resolve a case; close a case; acknowledge incidents by id; assign incidents by id to a user; resolve incidents by id; close incidents by id. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server