Skip to main content

Claude Code

Connect Causely to Claude Code to run incident triage, service health checks, and reliability reports without leaving the terminal.

Prerequisites​

Configuration​

Run once to register Causely across all your projects:

claude mcp add --scope user --transport http causely https://api.causely.app/mcp

This writes to ~/.claude.json automatically. No file editing required.

Team-shared config (optional)

To register Causely for everyone who clones a specific repo, create .mcp.json at the repository root instead:

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

Only use this if authentication is handled separately, never commit credentials. See Advanced Authentication.

Begin a new Claude Code session (claude) after any config change. Run /mcp to confirm causely appears as a connected server.

Adding Skills​

Seven skills activate automatically once installed: one master router (causely-mcp) plus six specialists. See the Skills page for the full list, trigger phrases, and override options.

Install

git clone https://github.com/Causely/development-environment
mkdir -p ~/.claude/skills
cp -r development-environment/skills/* ~/.claude/skills/

This installs to personal scope (~/.claude/skills/) so skills are available across all your projects. To commit skills to a single repo instead, replace ~/.claude/skills/ with .claude/skills/ in each path above.

Restart

Begin a new Claude Code session (claude) after installing.

Verify

Try: "What's broken right now?" The causely-health-reporting skill should activate.

Try It Now​

  • "List my clusters."
  • "Are there any active symptoms right now?"
  • "What services are currently degraded?"
  • "Draft a postmortem for the most recent incident."

Known Gotcha​

Project .mcp.json is committed to source control. Never add credentials directly to this file. Use --scope user when registering Causely so auth stays out of the repository. See Advanced Authentication.