Installation

AlertD ships a Model Context Protocol (MCP) server that connects Claude Code directly to your AlertD workspace. Once installed, you can ask Claude natural-language questions about your AWS infrastructure and it will query AlertD on your behalf — see Calling AlertD from Claude.

The integration is distributed as a Claude Code plugin that registers a remote (HTTP) MCP server pointed at your AlertD domain.

Prerequisites

Claude Code installed and working (installation guide ).
An AlertD account and your AlertD domain — the host you use to reach AlertD, e.g. alertd.mycompany.com. You’ll authenticate in the browser during setup, so you also need access to a browser on the same machine.

Install the plugin

You can install in one command, or do it manually inside Claude Code.

Option 1 — Quick install (recommended)

Run this in your terminal:


curl -H 'Cache-Control: no-cache' \
  https://raw.githubusercontent.com/alert-d/alertd-claude/main/install.sh | sh

The script adds the AlertD plugin marketplace, installs the alertd plugin at user scope, prompts you for your AlertD domain, and runs the setup command for you.

Option 2 — Manual install

Inside Claude Code, run the slash commands:


/plugin marketplace add alert-d/alertd-claude
/plugin install alertd

Then configure your domain (next section).

Configure your domain

The plugin needs to know which AlertD domain to talk to. Run the setup command inside Claude Code:


/alertd:setup

You’ll be asked for your AlertD domain (e.g. alertd.mycompany.com). Setup writes an .mcp.json file in your project root that registers the AlertD MCP server:


{
  "mcpServers": {
    "alertd": {
      "type": "http",
      "url": "https://alertd.mycompany.com/mcp"
    }
  }
}

.mcp.json lives in the root of the project/folder you open Claude Code in. If you use AlertD across several projects, run /alertd:setup in each one (the plugin itself only needs to be installed once, at user scope). If an .mcp.json already exists, setup merges the alertd entry in rather than overwriting your other MCP servers.

Authenticate and verify

Restart Claude Code so it picks up the new .mcp.json.
Run /mcp and select alertd. Claude Code opens your browser to sign in to AlertD and authorize the connection (OAuth). After approving, return to the terminal.
Run /mcp again — alertd should show as connected, with the aws_discovery tool available.

Once connected, head to Calling AlertD from Claude to start asking questions.

Reconfiguring the domain

If you entered the wrong domain (typo, wrong subdomain, or you’ve moved workspaces), the connection will fail to authenticate or won’t appear under /mcp. Fix it either way:

Option A — Re-run setup

The simplest fix. Run setup again with the correct domain:


/alertd:setup

Enter the corrected domain when prompted. Setup overwrites the alertd entry’s url in .mcp.json in place.

Option B — Edit `.mcp.json` directly

Open the .mcp.json in your project root and correct the url so it points at the right domain, keeping the /mcp path:


{
  "mcpServers": {
    "alertd": {
      "type": "http",
      "url": "https://alertd.mycompany.com/mcp"
    }
  }
}

After changing the domain

Restart Claude Code so the change takes effect.
Run /mcp, select alertd, and authenticate again — the old session was tied to the previous domain, so you’ll need a fresh sign-in.
Confirm alertd shows as connected.

Always include the scheme and the /mcp path: the URL must be https://<your-domain>/mcp. A bare domain or a missing /mcp will cause the connection to fail.

Optional: the AlertD CLI

The same integration is also available as a standalone command-line tool, if you’d rather query AlertD from your shell without Claude Code:


curl -fsSL -H 'Cache-Control: no-cache' \
  https://raw.githubusercontent.com/alert-d/alertd-claude/main/install-cli.sh | sh

This installs an alertd binary, authenticates you in the browser, and lets you run queries directly:


alertd login
alertd "what is in my aws"

The CLI is independent of the Claude Code plugin — you can use either or both.