INDIVIDUAL MCP TOOL

how_to_connect

Explain how to connect AlertRelay to this account so the agent can set up monitoring.

usealertrelay.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://usealertrelay.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for how_to_connect and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.alertrelay]
url = "https://usealertrelay.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "alertrelay": {
      "type": "http",
      "url": "https://usealertrelay.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: alertrelay
Remote MCP URL: https://usealertrelay.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "alertrelay": {
      "url": "https://usealertrelay.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "alertrelay": {
      "type": "http",
      "url": "https://usealertrelay.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "alertrelay",
  "transport": "streamable-http",
  "url": "https://usealertrelay.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

get_integration_guide — Full plain-text guide: the ingest API, the event schema, the standard security event types (failed_login, signup, error, blocked, …), heartbeats, and copy-paste snippets.