Connect Your AI Agent to Dexter

Dexter serves an MCP server at https://<DEXTER_HOST>/mcp, so you can work with incidents from your own AI agent instead of the Dexter web app. It has four tools:

  • search_incidents finds incidents by title and symptoms.

  • get_incident returns an incident’s context, questions, findings, and root cause analysis.

  • share_with_investigation sends information or a question to an open investigation and returns Dexter’s reply.

  • create_incident opens an incident and starts an investigation.

Step 1: Create a Service Token

  1. In Dexter, go to Admin > Access > Service tokens.

  2. Under Create a token, enter an ID and a display name, and click Create token.

  3. Copy the token. It starts with dxs_ and is shown only once.

  4. Grant the token a role:

    • Viewer (the default) can search and read incidents.

    • Responder can also share with investigations and create incidents.

Incidents and shares made through the token are attributed to its display name.

Step 2: Add Dexter to Your AI Client

Add the Dexter URL and the token to your client’s MCP configuration. For example, in Claude Code’s .mcp.json:

{
  "mcpServers": {
    "dexter": {
      "type": "http",
      "url": "https://<DEXTER_HOST>/mcp",
      "headers": {
        "Authorization": "Bearer <DEXTER_SERVICE_TOKEN>"
      }
    }
  }
}
json

Replace <DEXTER_HOST> with your Dexter address and <DEXTER_SERVICE_TOKEN> with the token from step 1.

Other clients take the same URL and header. For a client that cannot send headers, use the mcp-remote proxy as shown in Using mcp-remote Proxy.