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+)
Configuration
Create or update .cursor/mcp.json at the root of your project:
{
"mcpServers": {
"causely": {
"url": "https://api.causely.app/mcp"
}
}
}
Config file location
| Scope | Path |
|---|---|
| Project | .cursor/mcp.json at the repository root |
| User | Settings → MCP → Edit Config |
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.
Try It Now
- "List my clusters."
- "Are there any active symptoms right now?"
- "What services are currently degraded?"
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.