Authentication
Choose the auth option your MCP client supports, in this order:- HookMyApp CLI:
hookmyapp agent setupconfigures 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
/mcpin 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.
Authorization: Bearer for bearer-token clients. Use X-API-Key when your MCP client lets you configure custom headers.
Connect
HookMyApp CLI
--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.
Sign in from your client
/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: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
Facebook Page tools. Every tool takeschannelId, the ch_ id of a Facebook channel.
Shared tools that understand Facebook channels:
The Instagram tools (
publish_instagram_media, list_instagram_comments, get_instagram_insights and the rest) work on an Instagram channel connected through a Page too. See Instagram MCP.
If a tool asks you to reconnect the channel, reconnect once from the dashboard.
Examples
Ask your agent to check setup: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.