ReachOwl MCP server
reachowl.com, reach-owl.mintlify.site
Yes. ReachOwl publishes an official MCP server at https://reachowl.com/mcp. It's hosted. It offers 84 tools. We last checked it on 22 Nov 2026.
Official: answers MCP requests at reachowl.com, on ReachOwl's own domain reachowl.com. Checked 22 Nov 2026. Maintained by Stuart Brameld.
Key facts
As of 22 Nov 2026, ReachOwl's official MCP server scores 55/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 84 tools.
How the Agent Readiness Index works · Wrong? Suggest a correction
ReachOwl MCP server review
55/100
ReachOwl's MCP server scores 55/100 on MartechDB's Agent Readiness Index: usable by AI agents, with gaps.
The good
Hosted by ReachOwl: connect by URL, with nothing to install
Answered 100% of our checks in the last 90 days
The bad
Nothing we've found.
Not checked yet: how you sign in; a docs page listing its tools; what agent access costs. Anything not checked scores nothing.
Official MCP server
ReachOwl MCP server
- Address
- https://reachowl.com/mcp
- Runs
- Hosted
- Sign-in
- Official MCP Registry
- Not listed
- How we know it's official
-
- Answers MCP requests at reachowl.com, on ReachOwl's own domain reachowl.com.
- Tools
- 84 tools · listed 22 Nov 2026
- First seen
- 1 Oct 2026
- Last checked
-
Reachable ·
16 Nov 2026: reachable17 Nov 2026: reachable18 Nov 2026: reachable19 Nov 2026: reachable20 Nov 2026: reachable21 Nov 2026: reachable22 Nov 2026: reachable
- Uptime
- 100% · 55 of 55 checks reachable since 1 Oct 2026
ReachOwl MCP server tools (84)
As the server lists them. Names and descriptions are the vendor's own.
-
set_tokenPrimary auth path when the token is not already on the connector: store the user's ReachOwl Sanctum token (shape 1|…). Returns auth_session_id — web AI hosts (ChatGPT, Claude, Muse, …) are often stateless, so pass auth_session_id on later tool calls. Then auth_status + get_user.
-
authenticateFallback only: mint a Sanctum token via POST /api/v1/authenticate with email and password, then store it. Returns auth_session_id for web AI hosts (pass on later tool calls). Prefer set_token instead.
-
clear_tokenClear the ReachOwl Sanctum token from this MCP session / auth_session_id store.
-
auth_statusCheck whether a ReachOwl Sanctum token is available (has_token). Does not call the API or return the token. Desktop with Bearer in mcp.json needs no extra args. After set_token on web AIs, pass auth_session_id. Then call get_user.
-
get_userGET /api/v1/user — validates the stored Sanctum token and returns the current user, default team_id, and teams. Desktop with Bearer in mcp.json needs no extra args. On web AIs pass auth_session_id from set_token.
-
list_campaignsGET /api/v1/campaigns — list campaigns (facebook|instagram|whatsapp). Prefer omit team_id.
-
get_campaignGET /api/v1/campaigns/{id}
-
create_campaignPOST /api/v1/campaigns — create a NEW campaign using the same fields as Start Campaign in reachowl-ext. IMPORTANT: Do NOT use this tool to upload contacts into an existing campaign. If the user already has a campaign id (e.g. "upload to campaign 18312"), use add_campaign_contacts instead. ## Wizard steps (mirror these when building body) 1) Audience — set platform + audience_type together 2) Source — post_url / group_id / audience_source_id OR urls_file for file_upload (skipped for pending_friend_requests & suggestions) 3) Purpose — action_type (+ optional filter_only/campaign_mode/quick_flow for unfriend/unfollow) 4) Info — name (required), executor_ids (required, from list_app_states), limit, filters, friend_msg_sequence, events, turn_off, skip_duplicate 5) Messages — required when action_type=messages OR friend_msg_sequence>=1; omit/empty when friend_request with friend_msg_sequence=0 ## Required for a valid start - name (non-empty) - platform: facebook | instagram | whatsapp - aud…
-
update_campaignPATCH /api/v1/campaigns/{id} — partial update (same fields as create_campaign / Start Campaign wizard). Toggle with { status: 0|1 }. Send only fields to change. Does NOT change audience_type when adding contacts — use add_campaign_contacts for lists on existing campaigns.
-
delete_campaignDELETE /api/v1/campaigns/{id}
-
add_campaign_contactsPOST /api/v1/campaigns/{id}/contacts — save audience rows on an EXISTING campaign. Delegates to AudienceController::create (same as extension POST /api/audiences/create). Body shape: { audience: [{ name, member_id, profile_url, ... }] } Aliases contacts / audiences → audience. CSV: multipart urls_file (uploadingCampaignFile). Do NOT create a new campaign — pass the existing campaign_id. WhatsApp rows need member_id like "[email protected]" and profile_url "https://wa.me/923001234567" (or pass phone / phone_number / whatsapp and the tool will map them). FB/IG rows need member_id and/or profile_url. Example: { "campaign_id": 18312, "audience": [ { "name": "Ali Khan", "member_id": "[email protected]", "profile_url": "https://wa.me/923001234567", "variables": { "area": "DHA Lahore", "rent": "25000" } } ] }
-
list_contactsGET /api/v1/contacts — list campaign contacts/audiences. Pass campaign_id to filter one campaign.
-
get_contactGET /api/v1/contacts/{id} — contact detail including notes.
-
add_contact_notePOST /api/v1/contacts/{id}/notes — add or update a note.
-
delete_noteDELETE /api/v1/notes/{id}
-
lookup_queuesGET /api/v1/queues — look up queues for confirmation. Require campaign_id plus one of audience_id, member_id, or profile_url.
-
update_queuePATCH /api/v1/queues — update/retry a queue. Prefer { id, retry: true } after lookup_queues.
-
list_groupsGET /api/v1/groups — synced Facebook groups (read-only). For WhatsApp groups use list_whatsapp_groups.
-
list_whatsapp_groupsGET /api/v1/whatsapp-groups — synced WhatsApp groups for the activated WA account (read-only). Use group_id as post_url + audience_source_id when create_campaign with platform=whatsapp, audience_type=group. Sync happens from the Chrome extension after Activate WhatsApp on Browsers (or when the campaign wizard lists groups). Empty list → ask user to open WhatsApp Web / Activate / open the WA group picker once.
-
list_mentionsGET /api/v1/mentions — keyword monitors.
-
get_mentionGET /api/v1/mentions/{id}
-
create_or_update_mentionPOST /api/v1/mentions — create (no id) or update (with id) a keyword monitor.
-
delete_mentionDELETE /api/v1/mentions/{id}
-
list_mention_postsGET /api/v1/mentions/posts?mention_id= — posts found by a keyword monitor.
-
delete_mention_postDELETE /api/v1/mentions/posts/{id}
-
list_post_schedulersGET /api/v1/post-scheduler — Facebook group or account-timeline (profile) schedules. Response includes post_to_profile, profile_accounts / profile_account_ids, groups, and post_queues with destination_type group|profile. Optional post_to_profile=true|false filter; app_state_id matches scheduler or any profile queue executor.
-
get_post_schedulerGET /api/v1/post-scheduler/{id} — includes queues (destination_type, profile_fb_id, executor, post_url) and profile_accounts when posting to account timelines.
-
create_post_schedulerPOST /api/v1/post-scheduler — schedule Facebook posts to Groups OR Account timelines (profiles). Mirrors SavePostScheduler.vue in reachowl-ext. ## Destination (pick ONE — never both) 1) **Account timeline / Profile** — post to a Facebook account's own timeline/feed - Set: executor_id: <app_state_id>, post_to_profile: 1, profile_account_ids: "<app_state_id>" (or [<app_state_id>]), group_ids: "" - Multi-account OK (one queue per account) - Do NOT pass group_urls / non-empty group_ids 2) **Groups** — one executor posts into selected Facebook groups - Set: executor_id: <app_state_id>, post_to_profile: 0, profile_account_ids: "", group_urls (preferred) or group_ids ## Schedule (IMPORTANT) - **Relative / interval timing** (e.g. "today after 10 minutes", "in 10 minutes", "every 30 minutes"): Use `schedule_type: "interval"`, `interval: 10`, `time: null`, `calendar_items: ""`. Do NOT ask for a calendar clock time when the user specifies "after N minutes" — interval mode automatically schedules…
-
update_post_schedulerPATCH /api/v1/post-scheduler/{id} — status, schedule, delete_queue_ids, or full posts update. Same destination fields as create (Groups vs Account timeline). Toggle with { status: 0|1 }.
-
delete_post_schedulerDELETE /api/v1/post-scheduler/{id}
-
list_profile_growthGET /api/v1/profile-growth — Instagram profile growth plans (type=instagram).
-
get_profile_growthGET /api/v1/profile-growth/{id}
-
create_profile_growthPOST /api/v1/profile-growth — create IG growth plan (instagram only).
-
update_profile_growthPATCH /api/v1/profile-growth/{id} — e.g. { status: "running"|"paused" }.
-
delete_profile_growthDELETE /api/v1/profile-growth/{id}
-
list_stagesGET /api/v1/stages
-
get_stageGET /api/v1/stages/{id}
-
create_or_update_stagePOST /api/v1/stages — create or update one stage ({ name, id?, order? }).
-
reorder_stagesPUT /api/v1/stages — reorder stages with an array of { id, order }.
-
delete_stageDELETE /api/v1/stages/{id}
-
list_message_templatesGET /api/v1/message-templates
-
upsert_message_templatePOST /api/v1/message-templates — create/update ({ message, stage_id, image?, id? }).
-
delete_message_templateDELETE /api/v1/message-templates/{id}
-
list_browsersGET /api/v1/browsers — connected browsers (read-only).
-
get_browserGET /api/v1/browsers/{id}
-
list_app_statesGET /api/v1/app-states — connected social accounts. Use ids as executor_id / executor_ids.
-
get_app_stateGET /api/v1/app-states/{id}
-
list_teamsGET /api/v1/teams — team_id + teams.
-
list_team_membersGET /api/v1/team/members
-
add_team_memberPOST /api/v1/team/add — invite by email.
-
update_team_memberPOST /api/v1/team/members/store — update member ({ id, user_id, status, role }).
-
delete_team_memberDELETE /api/v1/team/members/{id}
-
list_eventsGET /api/v1/events — webhook event catalog (ids/keys for create_webhook).
-
list_webhooksGET /api/v1/webhooks
-
create_webhookPOST /api/v1/webhooks — subscribe a callback URL. Events from list_events (ids or slugs). keyword-monitor-found-a-post ignores campaign_id and sends at most 2 new posts per store.
-
update_webhookPUT /api/v1/webhooks/{id}
-
delete_webhookDELETE /api/v1/webhooks/{id}
-
list_comment_automationsGET /api/v1/comment-automations — Facebook/Instagram comment reply automations.
-
get_comment_automationGET /api/v1/comment-automations/{id}
-
create_comment_automationPOST /api/v1/comment-automations — create a comment automation. Requires name, executor_id, keywords[], posts[{post_url}], public_reply_message, private_dm_message. Optional type facebook|instagram, status active|paused.
-
update_comment_automationPATCH /api/v1/comment-automations/{id} — partial update. Pause/resume with { status: "active"|"paused" }. Replace posts with posts[{post_url}].
-
delete_comment_automationDELETE /api/v1/comment-automations/{id}
-
list_comment_automation_executionsGET /api/v1/comment-automations/{id}/executions — reply/DM activity for one automation.
-
get_page_scraper_statusGET /api/v1/page-scrapers/status — aggregate active/paused/completed counts for Facebook page scrapers.
-
start_all_page_scrapersPOST /api/v1/page-scrapers/start-all — start/resume scraping for all incomplete Facebook page scraper jobs (sets status to active).
-
stop_all_page_scrapersPOST /api/v1/page-scrapers/stop-all — pause all incomplete Facebook page scraper jobs (sets status to paused).
-
rerun_all_page_scrapersPOST /api/v1/page-scrapers/rerun-all — reset all Facebook page scraper jobs (including completed) to start from the beginning and mark them active.
-
list_page_scrapersGET /api/v1/page-scrapers — list Facebook page scraper jobs (location + keyword).
-
get_page_scraperGET /api/v1/page-scrapers/{id} — one scraper job + pages_count.
-
create_page_scrapersPOST /api/v1/page-scrapers — create location×keyword scraper jobs. Accepts either { locations: [{ label, value }], keywords: string[], ... } directly or nested under { body }. Scraping still needs a connected Facebook browser + extension.
-
update_page_scraperPATCH /api/v1/page-scrapers/{id} — partial update. Pause/resume with { status: "active"|"paused" }. Re-run with { rerun: true }. Optional location_id, location_name, keyword, reset, whatsapp_verification_enabled.
-
delete_page_scraperDELETE /api/v1/page-scrapers/{id} — delete scraper job and its scraped pages.
-
list_page_scraper_pagesGET /api/v1/page-scrapers/{id}/pages — scraped Facebook business pages for one scraper job.
-
list_facebook_business_pagesGET /api/v1/facebook-business-pages — list scraped pages (optional facebook_page_search_id, location_id, keyword, search).
-
get_facebook_business_pageGET /api/v1/facebook-business-pages/{id}
-
update_facebook_business_pagePATCH /api/v1/facebook-business-pages/{id} — update scraped page fields (name, phone, email, whatsapp, address, category, url, …).
-
delete_facebook_business_pageDELETE /api/v1/facebook-business-pages/{id}
-
delete_multiple_facebook_business_pagesPOST /api/v1/facebook-business-pages/delete-multiple — bulk delete scraped Facebook business pages by their IDs.
-
get_whatsapp_verification_summaryGET /api/v1/facebook-business-pages/verify-whatsapp/summary — get WhatsApp verification status summary (total, pending, verified, invalid, failed, unverified counts).
-
get_whatsapp_verification_pendingGET /api/v1/facebook-business-pages/verify-whatsapp/pending — get pages currently pending WhatsApp verification and the remaining queue count.
-
start_whatsapp_verificationPOST /api/v1/facebook-business-pages/verify-whatsapp/start — queue scraped Facebook business pages for WhatsApp verification. Provide facebook_page_search_id and/or specific page ids.
-
stop_whatsapp_verificationPOST /api/v1/facebook-business-pages/verify-whatsapp/stop — stop and cancel pending WhatsApp verification queue.
-
export_whatsapp_csvGET /api/v1/facebook-business-pages/export-whatsapp-csv — export verified WhatsApp business pages as a CSV spreadsheet.
-
api_requestRaw authenticated call to /api/v1/*. Prefer named tools when possible. Path must start with /api/v1/.
Connect your AI to ReachOwl
Add the official ReachOwl MCP server to Claude, ChatGPT or your editor.
Connect ReachOwl MCP to Claude
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it ReachOwl, paste the address below and click Add.
Connect ReachOwl MCP to ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it ReachOwl and paste the address below.
ChatGPT usually only connects to servers with self-serve sign-in or none.
Connect ReachOwl MCP to Cursor
Opens Cursor if it's installed. If nothing happens, use the JSON below.
Connect ReachOwl MCP to VS Code
Opens VS Code if it's installed. Otherwise add the JSON settings from the Cursor tab to your .vscode/mcp.json.
ReachOwl MCP server questions
Does ReachOwl have an official MCP server?
Yes. ReachOwl publishes its MCP server itself. Its address is on ReachOwl's own domain (reachowl.com). MartechDB only lists servers a vendor publishes, never community copies.
What is the ReachOwl MCP server URL?
The address is https://reachowl.com/mcp.
How do I connect ReachOwl MCP to Claude, ChatGPT or Cursor?
In Claude, add https://reachowl.com/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http reachowl https://reachowl.com/mcp
What can the ReachOwl MCP server do?
It offers 84 tools, including set_token, authenticate, clear_token, auth_status and get_user (as listed on 22 Nov 2026).
Is the ReachOwl MCP server in the official MCP Registry?
No. ReachOwl hasn't published it to the official MCP Registry.
Is the ReachOwl MCP server working?
Yes. It answered our most recent check. We last checked it on 22 Nov 2026.
What are the alternatives to ReachOwl's MCP server?
In Social media management, the most agent-friendly alternatives with an official MCP server are ContentStudio (100/100), SocialChamp (98/100), Buffer (95/100), Taplio (95/100) and Brandwise (95/100). ReachOwl scores 55/100 on the same index.
Alternatives to ReachOwl's MCP server
Vendors in Social media management with an official MCP server, the most agent-friendly first. ReachOwl scores 55/100.
ContentStudio
contentstudio.io
SocialChamp
socialchamp.com
Buffer
buffer.com
Taplio
taplio.com
Brandwise
brandwise.ai
Change history
What we've seen change for ReachOwl, newest first.
-
ReachOwl: ReachOwl MCP server: 21 tools added (now 84)
-
ReachOwl: ReachOwl MCP server: 1 tool added (now 63)
Use with AI
Connect your AI to MartechDB
Then ask it about ReachOwl, or any of the 1,851 marketing tools with an official MCP server. Free, no sign-in.
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it MartechDB, paste the address below and click Add. There's no sign-in.
The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.
Claude Code
Run this in your terminal:
ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it MartechDB, paste the address below and choose No authentication.
Developer mode is on Plus and Pro plans, and on Business, Enterprise and Edu if an admin allows it.
API
The same data as JSON, with no sign-in. See the OpenAPI description for every endpoint and field.
CLI
Search the directory and print the command to connect a vendor's server, from your terminal. Needs Node 18 or later. View on npm
Show that your MCP server is verified
If you work at ReachOwl, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.
Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.