# Causely MCP server

> Query Causely's causal model for root causes, blast radius, SLOs and service health in Kubernetes environments.

- Listing: https://mcp.tc/i/causely
- Connect: use the server's own URL `https://api.causely.app/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Observability & Incidents](https://mcp.tc/c/observability)
- Vendor: Causely
- Homepage: <https://docs.causely.ai/agent-integration/mcp-server/>
- Repository: <https://github.com/causely-oss/causely-client>

## About

Connects an assistant to Causely, which provides causal intelligence for Kubernetes environments. It covers root cause analysis, symptom detection, topology, metrics, logs, SLOs and post-incident work, so the assistant can answer observability questions from structured data instead of raw telemetry.

Runs as a hosted streamable HTTP endpoint at https://api.causely.app/mcp. Users sign in with their Causely account through OAuth on first connect. No API keys or custom headers are needed. A Causely deployment monitoring your clusters is required for useful results.

## What it can do

- Find active root causes and cascading failures
- Check violated or at-risk SLOs by cluster or namespace
- Get service health summaries and error budget burn
- Read logs and slow SQL queries for named services
- Detect symptoms such as pod crashes, OOM kills and node pressure
- Track recent deployments and configuration changes
- Pull evidence details behind a diagnosis

## Example prompts

- "Which SLOs are currently violated in the production cluster?"
- "What are the active root causes right now?"
- "Show the health summary and error budget burn for the checkout service."
- "Which deployments changed in the last 2 hours?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http causely https://api.causely.app/mcp
```

2. Start Claude Code, type `/mcp`, pick **causely** and choose **Authenticate**. A browser window opens for the Causely sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Causely** and paste this URL:

```url
https://api.causely.app/mcp
```

3. Click **Add**, then **Connect**, and sign in when Causely asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Causely&connectorUrl=https%3A%2F%2Fapi.causely.app%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.causely.app/mcp` and click **Add**.

3. Click **Connect** and sign in when Causely asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://api.causely.app/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Causely to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=causely&config=eyJ1cmwiOiJodHRwczovL2FwaS5jYXVzZWx5LmFwcC9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "causely": {
      "url": "https://api.causely.app/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=causely&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.causely.app%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"causely","type":"http","url":"https://api.causely.app/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "causely": {
      "type": "http",
      "url": "https://api.causely.app/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "causely": {
      "serverUrl": "https://api.causely.app/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add causely --url https://api.causely.app/mcp
codex mcp login causely
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.causely]
url = "https://api.causely.app/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http causely https://api.causely.app/mcp
```

Then, inside Gemini CLI, run `/mcp auth causely` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "causely": {
      "type": "http",
      "url": "https://api.causely.app/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.causely.app/mcp`.

## Recent changes

- 2026-10-07 22:49 UTC: Tracking started: version 1.0.0. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/causely#history (Atom feed: https://mcp.tc/i/causely/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-05
- Updated: 2026-10-05

---
Source: https://mcp.tc/i/causely (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
