Skip to main content
Endpoint:

Authentication

Choose the auth option your MCP client supports:
  • 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.
  • HookMyApp CLI (Claude Code): hookmyapp login configures the MCP server automatically, with no extra setup.
  • API key: create an API key in HookMyApp and pass it as a header.
Accepted API key headers:
Use Authorization: Bearer for bearer-token clients. Use X-API-Key when your MCP client lets you configure custom headers.

Connect

Sign in from your client

Run /mcp, pick hookmyapp, and approve the sign-in in your browser.

HookMyApp CLI (Claude Code)

If you use the HookMyApp CLI, MCP is already configured. hookmyapp login sets it up. To repair or re-run it:
MCP tools load when a session starts, so restart Claude Code after installing. Until then, every operation works through the hookmyapp CLI.

API key

Set your 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.

Tools

Examples

Ask your agent to check setup:
Ask your agent to inspect channels:
Ask your agent to send a message:

Project MCP vs docs MCP

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