Docs › MCP & AI

MCP & AI

HoldAlarms has a read-only MCP server at https://api.holdalarms.com/mcp. An AI assistant that supports remote MCP servers can use it to look up your destinations, recent alerts, failed alerts and heartbeats. It cannot change anything.

1. Create a token

  1. Sign in to the dashboard and open the "AI access (MCP)" panel.
  2. Click "Create read-only token". The token is shown once; copy it then.
  3. Tokens expire after 7 days. You can revoke a token at any time in the same panel. Up to 5 tokens can be active at once.

We store only a hash of the token. A token can only read your own account's data.

2. Connect your assistant

Add a remote MCP server with the URL https://api.holdalarms.com/mcp and the header Authorization: Bearer <your token>. Many clients accept a config like this:

{
  "mcpServers": {
    "holdalarms": {
      "url": "https://api.holdalarms.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

The server speaks MCP over HTTP POST with JSON replies.

3. Tools

ToolWhat it returns
list_destinationsEach destination's name (its label, its host, or "Hosted inbox"), whether it is on, your plan's limit, and its latest delivery status.
recent_alertsYour latest alerts (up to 50) with their delivery status, attempts, HTTP status and times.
dead_letter_queueAlerts in the dead-letter queue (up to 50) with the destination, the HTTP status and the error your endpoint returned.
heartbeat_statusEach heartbeat's name, interval, state (waiting for first beat, OK, late, paused) and last beat time.

Times are returned in UTC (ISO 8601).

What it does not do

  • There are no write tools: it cannot add or change destinations, send alerts, or send failed alerts again.
  • It does not return alert message bodies, full destination URLs, your webhook URL or heartbeat URLs.
  • It does not place trades or give trading advice.

← API

HoldAlarms is not affiliated with TradingView. TradingView is a trademark of TradingView, Inc.