Causely

app.causelyPublished by causely.appOfficial publisherv1.0.1Updated Oct 24, 2026

Causal reasoning for reliability: root cause, blast radius, and service health for agents.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure Security & Monitoring

Server details

Identifier: app.causely/causely
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to causely.app, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/app.causely%2Fcausely.svg)](https://sourceweft.com/mcp/app.causely%2Fcausely?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted Causely MCP server that lets an assistant query a causal model for root cause, blast radius and service health during reliability investigations.

What you can do: Query Causely's causal model for deterministic root cause analysis of incidents
Inspect blast radius and service health as structured tool results
Support investigation sequences such as alert triage, change impact, health reporting, Kubernetes investigation, correlated incidents and postmortems
Route work across Causely's tools via packaged skills and starter configs for common MCP clients
When to use it: Useful when an assistant needs to investigate production incidents or reliability questions against Causely's causal model instead of scanning raw telemetry, and when you already use Causely for observability.
Requirements: Remote MCP endpoint hosted by Causely; no local package or runtime. A Causely account is required: the client opens a browser for OAuth sign-in on first connect. No API keys or custom headers are needed for the hosted server.

Before you install

Connecting grants the assistant access to your Causely account data, including service health and incident context, which is sent to the hosted Causely service. Sign-in happens through an OAuth browser flow, so confirm the account and organization you authorize. The repository also ships a Kubernetes install CLI and API scripts that change cluster state; those are separate from the MCP server.

Installation

In SourceWeft

Open Causely in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.causely%2Fcausely/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

Causely Agent Integrations — MCP Skills, Plugins & CLI

These are the tools that let AI agents query Causely's causal model directly, instead of scanning raw telemetry and guessing. This repository bundles client-side resources for working with Causely: agent integrations (MCP), a Kubernetes install CLI, and a shell toolkit for the Causely GraphQL API.

The Causely MCP server is hosted at https://api.causely.app/mcp. Point any MCP-compatible client at it and sign in with your Causely account on first connect (OAuth, no API keys). It exposes Causely's causal model, deterministic root cause, blast radius, and service health, as structured tools your agent can call directly.

Area	Path	What it is
MCP skills & plugins	`mcp/`	Claude (and compatible) skills that route work across Causely's MCP tools, plus starter configs for Cursor, Claude, Codex, VS Code Copilot, and OpenCode.
Kubernetes CLI	`cli/`	Go CLI that wraps Helm to install and manage the Causely agent in-cluster.
API shell client	`api/`	Bash libraries and scripts for snapshots, comparisons, and CI workflows against the Causely API.

Product documentation lives at docs.causely.ai. For MCP authentication, headers, and troubleshooting, start with MCP Server Integration.

MCP (`mcp/`)

Point any MCP-compatible client directly at the hosted server:

On first connect, your client opens a browser to sign in to Causely (OAuth). No API keys or custom headers are required for the hosted server.

Or install the pre-built skills below for Claude Code, Claude Desktop, and Cursor, so your agent gets the right investigation sequence without hand-writing tool-selection logic.

mcp/README.md — Overview of the seven packaged skills (alert triage, change impact, health reporting, K8s investigation, correlated incidents, postmortems, and the master MCP router).
mcp/plugins/README.md — How to wire the hosted MCP server into Claude, Cursor, Codex, GitHub Copilot, OpenCode, and related tools, including optional custom headers.
Leaf skills — six drop-in folders under mcp/skills/, each with SKILL.md and references/complete-investigation.md (symlink to the shared mcp/complete-investigation.md in this repo).
Master router skill — mcp/SKILL.md (same causely-mcp role as in the skills overview) plus mcp/complete-investigation.md at the mcp/ root for full tool routing and investigation patterns.

Curious why causal context matters for agent accuracy? See the benchmark results — 100% fault scenario accuracy and 48% fewer tokens per investigation across 72 experiments.

CLI (`cli/`)

Install and operate the Causely agent from the terminal. See cli/README.md for the install script, causely agent install, auth, and Helm-oriented flags. Official install guide: CLI Installation.

API client (`api/`)

Shell-based GraphQL client: snapshots, diffing, GitHub Actions examples, and numbered docs. See api/README.md and api/docs/.

Contributing

See CONTRIBUTING.md for project layout, development setup, and how to submit changes.

The Go module for the CLI is declared in go.mod at the repository root (github.com/Causely/causely-api-client).

Source: README.md at commit f8b9664

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts