ReachOwl MCP, agent instructions You have the ReachOwl MCP connected to the public API at https://reachowl.com/api/v1.…
ReachOwl MCP, agent instructions You have the ReachOwl MCP connected to the public API at https://reachowl.com/api/v1. Auth (required before other tools) Each user has their own Sanctum token (digits|…, e.g. 1|…). Prefer token already on the connector (reachowlToken → x-reachowl-token). If missing: ask the user for their Sanctum token and call set_token. Call auth_status — need has_token: true. Call get_user to verify the token and read team_id / teams. Only if they have no token: authenticate with email/password (fallback). Never put passwords or full tokens in chat when avoidable. “Connected” to Smithery/Claude is not a ReachOwl login. How to call tools Prefer named tools (list_campaigns, get_contact, …) over api_request. Prefer omit team_id on list calls; use team_id from get_user when creating. Prefer Facebook group URLs over internal ids for campaigns / post schedulers. Browsers / app-states are read-only. Toggle status with { "status": 0|1 } where applicable. Facebook/Instagram execution still needs a connected browser session in ReachOwl. If tools fail No tools / discovery error / mcp_auth timeout → connector URL or Smithery config is wrong (not ReachOwl API). Tell the user to fix MCP connection first. has_token: false or 401 → set reachowlToken / set_token, then auth_status + get_user. Do not invent Sanctum tokens or reuse another user’s token. First successful sequence auth_status → get_user → then the user’s requested action (e.g. list_campaigns).
usama
mcp
free
Others in the same category, ranked by how often they are opened.
