MCP tool reference

BreakPass is a hosted MCP server. Your agent reaches you by WhatsApp, SMS or phone call through eight tools. Each verified number carries the person's name, set in Settings > Phone numbers, which your agent uses instead of the number. Agents never receive your phone number.

The tool contract of the BreakPass MCP server. Example values are illustrative; amounts in cents are placeholders (0), not prices. Not designed or guaranteed for emergencies or life-safety use.

Machine-readable copies: tools.json and tools.md. Plans are on Pricing. Per-alert prices are shown in your BreakPass account. The page for people is MCP.

Connect

Endpoint

https://mcp.breakpass.ai/mcp

Add it to Claude Code

claude mcp add --transport http breakpass https://mcp.breakpass.ai/mcp

Test it with the MCP Inspector

npx @modelcontextprotocol/inspector --server-url https://mcp.breakpass.ai/mcp

Server instructions

BreakPass alerts the account owner, and people they invited who confirmed their number with a code, by WhatsApp, SMS or phone call. It can only reach those verified numbers, by the person's name; it can't call, text or message anyone else. Send only what the user asked to be told about. BreakPass reaches the user by WhatsApp, SMS or phone call. get_setup_status reports whether the account can send yet and what is left to set up. list_workflows returns the saved workflows and when each fits; a workflow_id is one of those. start_workflow runs a saved workflow when the user may need follow-up: Inform for no reply, Acknowledge when receipt matters, Escalate when the user must know or act before returning. send_whatsapp, send_sms and make_call send one message or place one call. start_workflow takes an idempotency_key. An acknowledgement means the user saw the alert; it is not approval to act. A recipient is a person's name from get_setup_status (owner means the user), not a phone number. Messages are for what the user asked to be told about. BreakPass sends alerts only to the account owner's verified numbers. It can't contact emergency services, and delivery isn't guaranteed, so it isn't designed for emergency or life-safety use.

Authentication

Scopes

Tools

Eight tools. Three read, five act. The four that send (send_whatsapp, send_sms, make_call, start_workflow) share the fields message, recipient, agent_name, use_case, event_reference and idempotency_key. Their descriptions say that they spend the owner's balance and contact a real person.

get_setup_status

Reports where the account is in setup: readiness states, blockers, the people on the account by name (never phone numbers) with their channels, balance and the next setup link. Call it first and follow its next steps. It sends nothing and costs nothing.

Input

No input.

Output

Errors

ACCOUNT_SUSPENDED ("This BreakPass account is closed.") for a closed account. Authentication failures are HTTP 401 or 403, never tool errors.

Example

Request

{
  "name": "get_setup_status",
  "arguments": {}
}

Response (structuredContent)

{
  "account_state": "ready",
  "readiness": {
    "account_connected": true,
    "delivery_ready": true,
    "agent_guidance_configured": false
  },
  "onboarding_complete": true,
  "blockers": [],
  "recipients": [
    {
      "name": "Sam",
      "is_owner": true,
      "verified": true,
      "channels": {
        "whatsapp": "yes",
        "sms": "coming_soon",
        "call": "available"
      },
      "price_cents": {
        "whatsapp": 0,
        "sms": null,
        "call": 0
      },
      "max_chars": {
        "whatsapp": 600,
        "sms": null,
        "sms_confirm_link": null,
        "call": 150
      }
    }
  ],
  "default_recipient": "Sam",
  "owner_name": "Sam",
  "balance_cents": 2400,
  "reserved_cents": 0,
  "spent_today_cents": 0,
  "workflows_version": 1,
  "setup_url": "https://app.breakpass.ai/start"
}

list_workflows

Lists the saved alert workflows (Inform, Acknowledge, Escalate) with their ids, readable steps, limits and version. It reads the current configuration on every call, so changes the owner makes in the BreakPass app show up on the next read. It sends nothing and costs nothing.

Input

Output

Errors

See Errors for the causes and retry rules.

RECIPIENT_NOT_FOUND RECIPIENT_AMBIGUOUS

Example

Request

{
  "name": "list_workflows",
  "arguments": {
    "recipient": "owner"
  }
}

Response (structuredContent)

{
  "version": 1,
  "updated_at": "2026-10-03T09:00:00Z",
  "recipient": "owner",
  "workflows": [
    {
      "workflow_id": "inform",
      "name": "Inform",
      "summary": "Message at minute 0. No acknowledgement. One SMS if a WhatsApp message can't be delivered.",
      "use_when": "The user only needs to know. One message, no reply needed.",
      "version": 1,
      "steps": [
        {
          "offset_min": 0,
          "kind": "message",
          "channel": "whatsapp"
        }
      ],
      "ack_required_default": false,
      "requires_acknowledgement": false,
      "sms_fallback": true,
      "max_attempts": 2,
      "deadline_min": 75,
      "max_cost_cents": 0,
      "available": true,
      "editable_in": "portal"
    },
    {
      "workflow_id": "acknowledge",
      "name": "Acknowledge",
      "summary": "Messages at minutes 0, 10 and 30, then it stops; an acknowledgement stops it sooner. One SMS if a WhatsApp message can't be delivered.",
      "use_when": "It matters that the user saw it. Up to 3 messages, at 0, 10 and 30 minutes, until acknowledged.",
      "version": 1,
      "steps": [
        {
          "offset_min": 0,
          "kind": "message",
          "channel": "whatsapp"
        },
        {
          "offset_min": 10,
          "kind": "message",
          "channel": "whatsapp"
        },
        {
          "offset_min": 30,
          "kind": "message",
          "channel": "whatsapp"
        }
      ],
      "ack_required_default": true,
      "requires_acknowledgement": true,
      "sms_fallback": true,
      "max_attempts": 4,
      "deadline_min": 40,
      "max_cost_cents": 0,
      "available": true,
      "editable_in": "portal"
    },
    {
      "workflow_id": "escalate",
      "name": "Escalate",
      "summary": "Message at minute 0; calls at minutes 0, 1 and 2, then it stops; an acknowledgement stops it sooner. One SMS if a WhatsApp message can't be delivered.",
      "use_when": "The user must know or act before returning. A message and a call at once, then calls at 1 and 2 minutes; 3 calls in all.",
      "version": 1,
      "steps": [
        {
          "offset_min": 0,
          "kind": "message",
          "channel": "whatsapp"
        },
        {
          "offset_min": 0,
          "kind": "call",
          "channel": "call"
        },
        {
          "offset_min": 1,
          "kind": "call",
          "channel": "call"
        },
        {
          "offset_min": 2,
          "kind": "call",
          "channel": "call"
        }
      ],
      "ack_required_default": true,
      "requires_acknowledgement": true,
      "sms_fallback": true,
      "max_attempts": 5,
      "deadline_min": 12,
      "max_cost_cents": 0,
      "available": true,
      "editable_in": "portal"
    }
  ],
  "decision_model": null
}

send_whatsapp

Sends one WhatsApp message to a verified number. This spends the owner's balance and contacts a real person. One attempt: no retries and no follow-up. For repeated attempts use start_workflow.

Input

Output

Errors

See Errors for the causes and retry rules.

SETUP_INCOMPLETE INSUFFICIENT_BALANCE RATE_LIMITED RECIPIENT_NOT_FOUND RECIPIENT_AMBIGUOUS RECIPIENT_NOT_VERIFIED RECIPIENT_OPTED_OUT CHANNEL_UNAVAILABLE CONTENT_REJECTED IDEMPOTENCY_CONFLICT ACCOUNT_SUSPENDED PROVIDER_ERROR SERVICE_PAUSED TEMPLATE_MISMATCH

Example

Request

{
  "name": "send_whatsapp",
  "arguments": {
    "message": "Checkout is failing.",
    "recipient": "owner",
    "agent_name": "Checkout monitor",
    "use_case": "checkout",
    "require_ack": false,
    "idempotency_key": "checkout-failing-2026-10-03-1"
  }
}

Response (structuredContent)

{
  "alert_id": "A-7K3Q9X",
  "status": "queued",
  "channel": "whatsapp",
  "recipient": "owner",
  "estimated_cost_cents": 0,
  "require_ack": false,
  "deadline_at": null,
  "idempotent_replay": false
}

send_sms

Sends one SMS to a verified number. This spends the owner's balance and contacts a real person. One attempt: no retries and no follow-up. The text is never cut: a message that does not fit one SMS is refused (see message). Outside the US and Canada an SMS carries no link: a message with a link is refused there ("Carriers outside the US and Canada block texts with links. Send it by WhatsApp, or remove the link."). SMS is not offered in every country; where it is not, the tool returns CHANNEL_UNAVAILABLE.

Input

Output

Errors

See Errors for the causes and retry rules.

SETUP_INCOMPLETE INSUFFICIENT_BALANCE RATE_LIMITED RECIPIENT_NOT_FOUND RECIPIENT_AMBIGUOUS RECIPIENT_NOT_VERIFIED RECIPIENT_OPTED_OUT CHANNEL_UNAVAILABLE CONTENT_REJECTED IDEMPOTENCY_CONFLICT ACCOUNT_SUSPENDED PROVIDER_ERROR SERVICE_PAUSED

Example

Request

{
  "name": "send_sms",
  "arguments": {
    "message": "A refund over $200 waits for your OK.",
    "recipient": "owner",
    "use_case": "refunds",
    "require_ack": true
  }
}

Response (structuredContent)

{
  "alert_id": "A-4M8TQ2",
  "status": "queued",
  "channel": "sms",
  "recipient": "owner",
  "estimated_cost_cents": 0,
  "require_ack": true,
  "deadline_at": "2026-10-03T20:05:00Z",
  "idempotent_replay": false
}

make_call

Phones a verified number and reads the message out loud (at most 150 characters; a call is cut off 55 seconds after it is answered). This spends the owner's balance and contacts a real person. One attempt: no redial and no follow-up. Machine detection is off, so a voicemail that picks up hears the message and the call counts as answered (charged as answered). For repeated calls use start_workflow.

Input

Output

Errors

See Errors for the causes and retry rules.

SETUP_INCOMPLETE INSUFFICIENT_BALANCE RATE_LIMITED RECIPIENT_NOT_FOUND RECIPIENT_AMBIGUOUS RECIPIENT_NOT_VERIFIED RECIPIENT_OPTED_OUT CHANNEL_UNAVAILABLE CONTENT_REJECTED IDEMPOTENCY_CONFLICT ACCOUNT_SUSPENDED PROVIDER_ERROR SERVICE_PAUSED

Example

Request

{
  "name": "make_call",
  "arguments": {
    "message": "Checkout is failing.",
    "recipient": "owner",
    "require_ack": true,
    "idempotency_key": "checkout-failing-call-1"
  }
}

Response (structuredContent)

{
  "alert_id": "A-2R6WZ5",
  "status": "queued",
  "channel": "call",
  "recipient": "owner",
  "estimated_cost_cents": 0,
  "require_ack": true,
  "deadline_at": "2026-10-03T20:05:00Z",
  "idempotent_replay": false
}

start_workflow

Starts a saved workflow on BreakPass servers. The timers run on our side until the owner acknowledges or a stop rule applies, so the alert keeps going if your agent restarts. This spends the owner's balance and contacts a real person. Retries are always limited. The alert snapshots the workflow version: edits affect new alerts only. Poll get_alert_status; do not call again.

Input

Output

Errors

See Errors for the causes and retry rules.

SETUP_INCOMPLETE INSUFFICIENT_BALANCE RATE_LIMITED RECIPIENT_NOT_FOUND RECIPIENT_AMBIGUOUS RECIPIENT_NOT_VERIFIED RECIPIENT_OPTED_OUT CHANNEL_UNAVAILABLE CONTENT_REJECTED IDEMPOTENCY_CONFLICT ACCOUNT_SUSPENDED PROVIDER_ERROR SERVICE_PAUSED WORKFLOW_NOT_FOUND TEMPLATE_MISMATCH

Example

Request

{
  "name": "start_workflow",
  "arguments": {
    "workflow_id": "escalate",
    "message": "Checkout is failing.",
    "recipient": "owner",
    "agent_name": "Checkout monitor",
    "use_case": "checkout",
    "idempotency_key": "checkout-failing-2026-10-03T19-00"
  }
}

Response (structuredContent)

{
  "alert_id": "A-9D5HX1",
  "status": "queued",
  "workflow": {
    "id": "escalate",
    "name": "Escalate",
    "version": 1
  },
  "steps": [
    {
      "offset_min": 0,
      "kind": "message",
      "channel": "whatsapp"
    },
    {
      "offset_min": 0,
      "kind": "call",
      "channel": "call"
    },
    {
      "offset_min": 1,
      "kind": "call",
      "channel": "call"
    },
    {
      "offset_min": 2,
      "kind": "call",
      "channel": "call"
    }
  ],
  "recipient": "owner",
  "require_ack": true,
  "requires_acknowledgement": true,
  "max_cost_cents": 0,
  "deadline_at": "2026-10-03T19:12:00Z",
  "idempotent_replay": false,
  "next_step": "Poll get_alert_status; do not call start_workflow again."
}

get_alert_status

Returns the status of alerts you started: delivered, acknowledged, failed, expired or cancelled, with every attempt. Delivered is not acknowledged, and silence is not a confirmed failure. It sends nothing and costs nothing.

Input

Output

Status values

Errors

See Errors for the causes and retry rules.

ALERT_NOT_FOUND (details: not_found), CONTENT_REJECTED (for example "Send alert_ids or event_reference, not both.")

Example

Request

{
  "name": "get_alert_status",
  "arguments": {
    "alert_ids": [
      "A-9D5HX1"
    ]
  }
}

Response (structuredContent)

{
  "alerts": [
    {
      "alert_id": "A-9D5HX1",
      "kind": "workflow",
      "workflow": {
        "id": "escalate",
        "version": 1
      },
      "recipient": "owner",
      "status": "acknowledged",
      "terminal": true,
      "awaiting_ack": false,
      "requires_acknowledgement": true,
      "outcome": "acknowledged",
      "outcome_text": "Acknowledged",
      "created_at": "2026-10-03T19:00:00Z",
      "deadline_at": "2026-10-03T19:12:00Z",
      "acknowledged_at": "2026-10-03T19:00:40Z",
      "ack_via": "dtmf",
      "charged_cents": 0,
      "attempts": [
        {
          "seq": 1,
          "offset_min": 0,
          "kind": "message",
          "channel": "whatsapp",
          "status": "delivered",
          "charged_cents": 0,
          "outcome": null
        },
        {
          "seq": 2,
          "offset_min": 0,
          "kind": "call",
          "channel": "call",
          "status": "answered",
          "charged_cents": 0,
          "outcome": null
        }
      ]
    }
  ],
  "not_found": []
}

cancel_alert

Stops all unsent steps of an alert and releases the unused reservation. Calling it again is safe. An attempt already in flight, such as a call that is ringing, may finish.

Input

Output

The final status of the alert, with the fields of one get_alert_status entry, not wrapped in a key.

Errors

See Errors for the causes and retry rules.

ALERT_NOT_FOUND CONTENT_REJECTED

Example

Request

{
  "name": "cancel_alert",
  "arguments": {
    "alert_id": "A-5F2VC8"
  }
}

Response (structuredContent)

{
  "alert_id": "A-5F2VC8",
  "status": "cancelled",
  "terminal": true,
  "cancelled_at": "2026-10-03T19:02:10Z",
  "cancelled_by": "agent"
}

Workflows

Every account starts with three editable workflows: Inform, Acknowledge and Escalate. The owner edits them in the BreakPass app, under How it works. All times are offsets from the first alert, not intervals between steps. These are the starting presets.

The SMS fallback happens only when delivery fails, never merely because acknowledgement is missing. Calls never redial. A call that voicemail picks up counts as answered; without an acknowledgement the next step proceeds on schedule. Edits apply to new alerts. Alerts already running keep the version they started with.

Delivery and acknowledgement

Delivered means a provider confirmed the message reached the phone, or the call was answered (machine detection is off, so a voicemail that picks up counts as answered). It does not mean seen or acknowledged.

Acknowledged means the holder explicitly confirmed receipt. It confirms receipt only. It never approves an agent action or a purchase, and it does not mean an issue is resolved.

Silence is not a confirmed failure. An alert moves from queued to delivered, then ends as acknowledged, expired, cancelled or failed. For Inform and for direct sends without require_ack, delivered is final. An acknowledgement after expired is recorded as late_ack_at and the status does not change.

• WhatsApp: the Acknowledge button on the message.
• Phone call: press 1 (calls that ask for acknowledgement say "Press 1 to acknowledge.").
• SMS: a link to a page where the holder presses a button. Opening the link changes nothing.
• In the app: the owner can acknowledge or cancel from the alert page.

Your agent learns about an acknowledgement by polling get_alert_status.

What a call says. Every call opens with "This is BreakPass by X Labs, with an alert from {agent_name}.", then the message (and "Press 1 to acknowledge." when acknowledgement is asked), a 3-second pause, then "To stop all BreakPass alerts to this number, press 9." On +1 numbers it adds "To reach us, call 3 3 2, 2 8 7, 9 2 0 0." (+1 332 287 9200). Key 9 counts only from that sentence to the end of the call; it stops all BreakPass alerts to the number from every account, and the call says "You will receive no more BreakPass alerts. Goodbye." Otherwise the call ends with "Goodbye." or "Acknowledged. Goodbye."

Idempotency and duplicates

• Same idempotency_key and same payload within 24 hours: the original alert is returned with idempotent_replay: true. No new send, no charge.
• Same key and a different payload: IDEMPOTENCY_CONFLICT.
• No key on a direct tool: the same recipient, channel and message within 60 seconds returns the original alert with idempotent_replay: true. Nothing is charged.
• start_workflow requires a key. Send one every time.

Limits

These are initial defaults. They can change.

Errors

A tool error returns isError: true and structuredContent.error with code, message, optional retry_after_s and optional details.

{
  "isError": true,
  "structuredContent": {
    "error": {
      "code": "RATE_LIMITED",
      "message": "Too many alerts to this recipient in the last hour (the limit is 20 an hour).",
      "retry_after_s": 1200,
      "details": { "reason": "holder_per_hour" }
    }
  }
}

RATE_LIMITED reasons

details.reason of a RATE_LIMITED error, with its message. A refusal without a message reads "Too many alerts. Wait before sending again."