postmortem.so/Docs

MCP Setup

postmortem.so includes an MCP (Model Context Protocol) server with 25 tools. Connect it to your AI assistant to manage projects, incidents, and post-mortems without leaving your editor.

Supported clients

  • Claude Desktop
  • Cursor
  • Windsurf
  • Any MCP-compatible client

Your MCP server URL

Find your MCP server URL in the dashboard at Settings → MCP Integration:

https://postmortem.so/api/mcp

Setup: Claude Desktop

  1. Open Claude Desktop → Settings → MCP Servers
  2. Click “Add MCP Server”
  3. Enter the URL: https://postmortem.so/api/mcp
  4. Click Connect
  5. You'll be redirected to sign in to postmortem.so
  6. Authorize the connection
  7. Done — Claude can now manage your postmortem.so account

Setup: Cursor

  1. Open Cursor → Settings → MCP
  2. Add a new MCP server
  3. URL: https://postmortem.so/api/mcp
  4. Authenticate when prompted
  5. The 25 tools are now available in Cursor's AI chat

Setup: Windsurf

  1. Open Windsurf → Settings → MCP Servers
  2. Add server URL: https://postmortem.so/api/mcp
  3. Authenticate when prompted

Available tools (25)

Read operations — all plans including Free

  • list_projects — list your projects
  • get_status — check system health and endpoint uptime
  • list_incidents — view recent incidents
  • list_endpoints — see monitored endpoints
  • list_members — view team members
  • get_sla_config — check SLA configuration
  • list_audit_logs — view activity log (Team)
  • get_postmortem — retrieve a post-mortem
  • get_webhook_url — get the webhook ingestion URL for a project

Write operations — Pro and Team

  • create_project, update_project, delete_project
  • add_endpoint, update_endpoint, remove_endpoint
  • create_incident, update_incident, resolve_incident, delete_incident
  • add_incident_update — post timeline updates
  • generate_postmortem — create AI post-mortem
  • invite_member, remove_member
  • update_sla_config
  • configure_webhook — enable ingestion and manage webhook secret

Example usage

You: "Create an incident for our API — we're seeing 500 errors on /checkout"

Claude: Created incident "API 500 errors on /checkout" for your project.
        Status: investigating. Your team has been notified.

You: "The root cause was a database connection pool issue.
      Resolve it and generate a post-mortem."

Claude: Incident resolved. Post-mortem generated with summary, timeline,
        root cause, impact, and 4 action items.

Authentication

MCP uses OAuth 2.0 with PKCE. When you first connect, you'll be redirected to sign in. The token is stored by your MCP client and refreshed automatically.

Free plan users can use read-only MCP tools. Write operations require Pro or Team.