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).
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3547 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 60 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 38% of peers
- This listing 436 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/usama/reachowl/mcpcurl -X POST https://server.smithery.ai/usama/reachowl/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'