MCP

Endpoint:

https://api.hookmyapp.com/mcp

Authentication

Choose the auth option your MCP client supports, in this order:

HookMyApp CLI: hookmyapp agent setup configures the server in every coding agent installed on your machine: Claude Code, Codex, and Cursor.
Sign in from your MCP client: add the server by URL and sign in when prompted (for example /mcp in Claude Code). No API key needed.
API key: create an API key in HookMyApp and pass it as a header. Best for CI and headless environments.

Accepted API key headers:

Authorization: Bearer hmok_...

X-API-Key: hmok_...

Use Authorization: Bearer for bearer-token clients. Use X-API-Key when your MCP client lets you configure custom headers.

Connect

HookMyApp CLI

hookmyapp agent setup
hookmyapp doctor

Configures Claude Code, Codex, and Cursor, and installs the HookMyApp agent skills. Needs CLI 0.14.19 or newer. Add --client claude, --client codex, or --client cursor to set up only one of them. The credential is written into each entry, so no client needs a separate sign-in. Setup prints one line per client naming the restart it needs. MCP tools load when a session starts, so restart your agent after running this. Until then, every operation works through the hookmyapp CLI.

claude mcp add --transport http hookmyapp https://api.hookmyapp.com/mcp

Run /mcp, pick hookmyapp, and approve the sign-in in your browser. Codex and Cursor support the same flow with their own commands.

API key

Set your HookMyApp API key:

export HOOKMYAPP_API_KEY="hmok_..."

codex mcp add hookmyapp --url https://api.hookmyapp.com/mcp --bearer-token-env-var HOOKMYAPP_API_KEY

claude mcp add --transport http hookmyapp https://api.hookmyapp.com/mcp \
  --header "Authorization: Bearer $HOOKMYAPP_API_KEY"

{
  "mcpServers": {
    "hookmyapp": {
      "url": "https://api.hookmyapp.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:HOOKMYAPP_API_KEY}"
      }
    }
  }
}

Use X-API-Key instead

Codex CLI has no --header flag, so X-API-Key goes in ~/.codex/config.toml. For Cursor and Claude Code, swap the header.

[mcp_servers.hookmyapp]
url = "https://api.hookmyapp.com/mcp"
env_http_headers = { "X-API-Key" = "HOOKMYAPP_API_KEY" }

claude mcp add --transport http hookmyapp https://api.hookmyapp.com/mcp \
  --header "X-API-Key: $HOOKMYAPP_API_KEY"

{
  "mcpServers": {
    "hookmyapp": {
      "url": "https://api.hookmyapp.com/mcp",
      "headers": {
        "X-API-Key": "${env:HOOKMYAPP_API_KEY}"
      }
    }
  }
}

Tools

Tool	Use it for
`status`	Check auth, organization, scopes, and next steps. Also returns unacknowledged `notifications[]`
`acknowledge_notification`	Mark a notification from `status` `notifications[]` as seen, after relaying it to a human. Idempotent
`list_workspaces`	List workspaces and customers
`create_workspace`	Create a workspace
`delete_workspace`	Delete a workspace (org admin; team and customer alike). Deletes it outright when it has no channels and no usage history; otherwise deprecates it, disconnecting its channels and keeping history for stats and billing. Refuses the organization’s last workspace
`list_customers`	List customers in the organization
`create_customer`	Create a customer
`list_channels`	List WhatsApp channels in a workspace
`get_channel`	Read channel details
`send_message`	Send a WhatsApp message
`get_webhook_config`	Read a channel webhook destination
`get_hmac_secret`	Read a channel’s current webhook signing secret without rotating it
`set_webhook_destination`	Set a channel webhook destination
`clear_webhook_destination`	Clear a channel webhook destination
`rotate_hmac`	Rotate a channel webhook signing secret
`set_forwarding`	Enable or disable forwarding
`list_deliveries`	List delivery logs for a channel
`get_delivery`	Read one delivery log by channel + its `wd_` ID from `list_deliveries`
`start_sandbox_session`	Get your sandbox bind code and a `wa.me` link. Send that code to the sandbox number from the phone you want to test with
`list_sandbox_sessions`	List the sandbox testing sessions in a workspace
`get_sandbox_logs`	Read inbound and forwarded messages for a sandbox session
`set_sandbox_destination`	Point a sandbox session at your webhook URL
`send_sandbox_message`	Reply to the phone bound to a sandbox session
`get_org_usage`	Check the actions your organization has used and has left this quota period
`get_alert_phone_status`	Check your alert phone and what it receives
`set_alert_phone`	Set your alert phone. Sends a 6-digit code to confirm it
`verify_alert_phone`	Confirm your alert phone with the code
`remove_alert_phone`	Remove your alert phone
`list_onboarding_links`	List customer onboarding links
`create_onboarding_link`	Create a customer onboarding link
`revoke_onboarding_link`	Revoke a customer onboarding link so it can no longer be used
`set_org_destination`	Set the default destination for customer channels
`apply_org_destination_to_channels`	Apply or clear the organization destination in bulk

Sandbox sessions are not channels. They have their own ssn_ ID, so they never appear in list_channels, get_channel, list_deliveries, or the channelCount in status. Use the sandbox tools above for anything you are testing through the shared sandbox number, and the channel tools for numbers connected to your own WhatsApp Business account. status reports sandboxSessionCount so you can tell the two apart before answering someone that nothing is connected.

Examples

Ask your agent to check setup:

Use HookMyApp MCP to check my organization status and tell me the next action.

Ask your agent to inspect channels:

Use HookMyApp MCP to list my workspaces, then list the WhatsApp channels in the active workspace.

Ask your agent to set up a test number without a Meta app:

Use HookMyApp MCP to start a sandbox session, then send me the WhatsApp link so
I can bind my phone. Once it is active, point it at https://example.com/hook.

Ask your agent to answer a message that arrived in the sandbox:

Use HookMyApp MCP to read my sandbox logs, then reply to the last message.

Ask your agent to send a message:

Use HookMyApp MCP to send "Hello from HookMyApp" from channel ch_xxxxxxxx.

Project MCP vs docs MCP

Server	Endpoint	Use it for
Project MCP	`https://api.hookmyapp.com/mcp`	Operating HookMyApp with the CLI-configured credential or an API key
Docs MCP	Not published yet	Documentation lookup only

Use the CLI when your agent has terminal access. Use MCP when your agent supports MCP and should operate HookMyApp directly.

Getting started

Sending & receiving

Tools

Self-managed setup

FAQs

API Reference

Authentication

Connect

HookMyApp CLI

API key

Use X-API-Key instead

Tools

Examples

Project MCP vs docs MCP

​Authentication

​Connect

​HookMyApp CLI

​Sign in from your client

​API key

​Use X-API-Key instead

​Tools

​Examples

​Project MCP vs docs MCP

Authentication

Connect

HookMyApp CLI

Sign in from your client

API key

Use X-API-Key instead

Tools

Examples

Project MCP vs docs MCP