Cursor

Connect Causely to Cursor to investigate incidents and check service health inline while you code.

Prerequisites

• Active Causely account
• Cursor with MCP support (1.0+)

Installation

Option 1: Cursor plugin (recommended)

Install the Causely plugin from cursor.directory/plugins/causely in one click. It configures the MCP server and installs all seven skills automatically, no manual steps required.

After installing, open Settings → MCP and confirm causely appears with a green status indicator.

Option 2: Manual setup

MCP server

Create or update .cursor/mcp.json at the root of your project:

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

Scope	Path
User (all projects)	~/.cursor/mcp.json, open via Settings → MCP → Edit Config
Project	.cursor/mcp.json at the project root

Add Skills

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

Cursor skills are project-scoped; there is no personal skills directory. Run these commands at the root of each project where you want skills available.

Restart

After saving the config, open Settings → MCP, causely should appear with a green status indicator. If it does not, use Cmd/Ctrl+Shift+P → MCP: Restart MCP Server or restart Cursor entirely.

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

Cursor caches MCP tool descriptions at session start. If you update the server config or Causely releases new tools, the previous tool list persists until you explicitly restart the MCP server or restart Cursor. See Advanced Authentication if you need to add machine credentials.