# Claude iMessage: AI Texting with Beam

Canonical: https://www.claudeimessage.com/claude-imessage
Beam page: https://www.claudeimessage.com/claude-imessage
Updated: 2026-09-26

Beam works with Claude agents through MCP. Not an Anthropic or Apple product.
Real blue-bubble iMessage for eligible recipients and supported lines, RCS where supported, and SMS fallback. Beam is messaging software.

## How do I send an iMessage from Claude?

Connect a compatible Claude client to Beam through MCP using a workspace connection token. Grant sending permission and use an active assigned line. Your agent can read conversations and send messages through Beam. Beam selects iMessage when the recipient is eligible and the selected line supports it. An accepted send is not proof of delivery.

## How do I send iMessage from GoHighLevel?

Connect Beam to the correct GoHighLevel location, then add a Custom Webhook workflow step using the documented Beam workflow endpoint. Use a workspace token with sending permission and an active assigned line. Validate with a test contact before enabling the workflow. The regular GoHighLevel Send SMS action continues to use your default SMS provider.

## Is there an iMessage API for AI agents?

Yes. Beam provides a messaging API and MCP tools for AI agents to read conversations and send messages within an authorized workspace. This is Beam software, not an official Apple iMessage API. Pause the built-in assistant before an external agent takes over replies, grant sending permission explicitly, and check delivery status in Beam.

## Can I connect Claude Code or a desktop MCP client?

Beam documents a Claude Code connection using HTTP with a Bearer authorization header. Desktop clients that support stdio can use the downloadable Beam bridge with Node.js 20 or newer. Keep your workspace token in private client configuration. Hosted connectors that require OAuth-only login are not supported, so check your client’s supported connection method before setup.

## Can an agency connect separate client workspaces?

Yes. Agency owners can select a directly managed client in Developer access before creating a connection token. Create a separate connection for each client because a token cannot switch workspaces. Client owners can also create and revoke their own connections. Access stops if the client leaves the agency, and live sending requires explicit permission.

## Will Beam retry a webhook if my endpoint is unavailable?

Message event webhooks are pushed once, with no automatic retries in this version. Verify webhook signatures against the raw request body before processing events. For conversations your workflow cannot afford to miss, reconcile activity with message history on a schedule. Your integration should account for missed events instead of assuming every notification will arrive.

## What is Claude iMessage?

Claude iMessage means connecting Claude to Beam so an AI agent can work with business text conversations. Beam provides the messaging connection; Claude provides the AI. Beam works with Claude agents through MCP and is not an Anthropic or Apple product. Channel availability depends on the selected line and the recipient.

## Does it work with ChatGPT and other agents?

You can build a ChatGPT or other AI agent integration using Beam’s API, or use a compatible MCP client. Beam MCP supports HTTP with a Bearer authorization header and a local stdio bridge. Hosted connectors that require OAuth-only login are not supported yet. Each connection is restricted to its authorized workspace.

## Do I need A2P 10DLC registration?

Beam’s iMessage and RCS channels avoid the carrier A2P 10DLC registration process. SMS fallback remains subject to applicable carrier A2P requirements. Consent and opt-out obligations still apply to your messaging workflows. Channel availability does not remove those obligations, and live sending still requires an active assigned line and appropriate workspace permissions.

## What happens on Android?

Beam uses RCS when the Android recipient’s phone and carrier support it, with SMS fallback otherwise. Beam sends from Apple and Android devices. Sender capability and recipient reachability still matter. For eligible iPhone recipients, Beam selects iMessage when the chosen line supports it. Test the message and reply path before relying on a workflow.

## Does delivered mean read?

No. Delivery status and recipient read status are different signals. An accepted or queued message is not proof of delivery. Beam shows recipient read status only when a channel supplies a real read event; read receipts depend on the channel and recipient settings. GoHighLevel receives pending, delivered or failed states, without invented open or read status.

![Example illustration: Claude calls Beam MCP message_send to send a blue iMessage bubble, with pending, delivered and failed states.](https://www.claudeimessage.com/claude-imessage-flow.svg)

Example workflow, not a customer conversation. Accepted does not mean delivered. Read status requires a real channel read event.

## Developer setup

For desktop clients that support stdio, download the Beam bridge and run it with Node.js 20 or newer. Replace the absolute path with your local download path and YOUR_TOKEN with your workspace connection token. Keep the configuration private.

```json
{
  "mcpServers": {
    "beam": {
      "command": "node",
      "args": ["/absolute/path/beam-mcp.mjs"],
      "env": { "BEAM_TOKEN": "YOUR_TOKEN" }
    }
  }
}
```

- [MCP setup and permissions](https://beamtexting.com/docs/developer-access)
- [Beam bridge](https://beamtexting.com/docs/beam-mcp.mjs)
- [Signed event webhooks](https://beamtexting.com/docs/api-events)
- [GoHighLevel workflow setup](https://beamtexting.com/docs/ghl-workflows)

Verify webhook signatures against the raw body. Events have no automatic retries; reconcile important activity with message history. Pause the built-in assistant before an external agent manages replies.

## Workflows to build

Agency lead conversations, follow-up texts after calls, CRM-timed appointment reminders and AI drafts for team review. Beam also supports FaceTime Audio. These are workflow examples, not performance promises. A free Claude skill for working with Beam is coming soon.

## Try Beam

[Text our team to try it](https://www.claudeimessage.com/claude-imessage#interactive-demo), or [read the MCP docs](https://beamtexting.com/docs/developer-access).