Modus MCP Connector
Last Updated: September 19, 2026Modus is the sales system for gyms, studios and athletic-training businesses. The connector lets an AI assistant work with a business's Modus workspace to acquire new prospects, convert leads into customers and understand what's driving sales. The assistant does the reasoning; Modus supplies the data and the actions.
Understand
Headline numbers, the sales funnel, which lead sources and ad campaigns produce customers, and who the best customers are.
Convert
Who to follow up with today, who went quiet, unconfirmed appointments and open times. Texts are drafted and sent only after the owner approves them; assessments can be booked, moved and cancelled once the user confirms.
Acquire
Search the athletes a business already has by school, sport and grade, and find new youth-athlete prospects in its area.
Connecting
| MCP endpoint | https://connect.himodus.com/mcp (Streamable HTTP) |
|---|---|
| Protocol versions | 2026-07-28, plus 2025-11-25, 2025-06-18 and 2025-03-26 for clients that open with initialize. Stateless: no sessions, no server-initiated requests; every response is a single JSON object. |
| Authorization | OAuth 2.1 authorization code with PKCE (S256 only), discovered through WWW-Authenticate on a 401 response. |
| Resource metadata | /.well-known/oauth-protected-resource/mcp (RFC 9728) |
| Authorization server metadata | /.well-known/oauth-authorization-server (RFC 8414) |
| Client registration | Client ID Metadata Documents (preferred), Dynamic Client Registration at /oauth/register (RFC 7591), or a pre-registered client ID on request. |
| Tokens | Opaque bearer tokens bound to the MCP resource (RFC 8707). Access tokens last 1 hour. Refresh tokens (for clients registered for them) last 30 days and rotate on every use; a reused refresh token revokes the whole grant. Every grant ends 90 days after sign-in. Revocation is at /oauth/revoke (RFC 7009). |
| Scopes | modus.read: reports, leads, appointments and conversations, plus drafting messages.modus.act: send owner-approved text messages. Requested separately, only granted to verified apps, and step-up is supported (HTTP 403 insufficient_scope). |
The user signs in with their Modus username and password. Owner/admin accounts can connect; staff accounts can't by default. Each connection only sees the workspace of the person who signed in.
Tools
| Tool | What it does |
|---|---|
| get_workspace_overview | The business, its programs, how much data it holds and which capabilities are on for this connection. A good first call when planning a multi-step goal. |
| get_business_snapshot | Leads, bookings, sales and estimated recurring revenue for a period, with booking and close rates, compared with the previous period (like-for-like while a period is still in progress). |
| get_funnel | Lead → contacted → booked → attended → bought, with the conversion at each step and the weakest step called out. Can be split by source, program, trainer or ad campaign. |
| get_lead_source_performance | Which sources, Facebook campaigns and ad sets turn leads into customers and revenue, not just leads. |
| get_best_customer_profile | How buyers differ from everyone who enquires (sport, grade, school, source, program), and how long a sale takes. |
| get_follow_up_priorities | A ranked list of people most worth contacting now, each with the reason (for example, replied and waiting, assessed but not bought, missed an appointment, went quiet). |
| find_leads | Search the pipeline by follow-up situation, stage, source, program and dates. |
| get_lead | One person's stage, bookings and recent conversation. Lead-written text is marked as untrusted content. |
| list_upcoming_appointments | Assessments in the next N days, flagged by whether the person has replied since booking. |
| get_open_assessment_slots | Open assessment days and times from the business's booking calendar. |
| draft_follow_upwrites a draft only | Prepares personalised texts for up to 25 people and checks each against the contact rules. Sends nothing. Returns the exact messages and, where sending is on, a link for the owner to approve them in Modus. |
| send_follow_upmodus.act | Sends a batch the owner approved in Modus, exactly as approved, once. Only available where sending is turned on for the workspace. |
| book_appointmentmodus.act | Books a first appointment (assessment / consultation) for one person at a time the user has approved. Where the workspace has a booking calendar, it books there and starts the business's usual reminder texts, exactly as booking by hand in Modus does. |
| move_appointmentmodus.act | Moves someone's upcoming assessment to another open time, after the user confirms. |
| cancel_appointmentmodus.act | Cancels someone's upcoming assessment after the user confirms. The person isn't told automatically; the assistant offers to draft them a message. |
| search_athletes | Searches the athletes already in the business's Modus database by school (loosely matched), sport, grade, position or name, and shows who has already been contacted, booked or signed up. |
| find_prospectsif enabled | Finds high-school athletes for a sport on public school rosters in the business's area, for the user to review. Adds no one to the pipeline and contacts no one. |
Example requests
- “How are we doing this month?” / “What changed versus last month?”
- “Why are we getting plenty of leads but not enough sales?” / “Where are we losing people in our funnel?”
- “Which lead sources, and which Facebook campaigns, are actually producing customers?”
- “Who are the best leads for me to follow up with today?”
- “Follow up with everyone who showed interest but never booked.”
- “Which upcoming appointments haven't confirmed yet? Follow up with them.”
- “Show me all the football players we have from Anderson HS.”
- “Find 25 new prospects for our youth basketball program.”
- “We need 10 more customers this month. Figure out what we should do.”
Messaging safeguards
Only one tool, send_follow_up, can reach a person. It works only when all of these are true:
- Modus has enabled sending for the business's workspace, and the user granted the separate
modus.actpermission. Apps Modus hasn't verified are never offered that permission. - The business owner approves the batch inside Modus.
draft_follow_upreturns an approval link to a Modus page that shows the exact messages. The owner, signed in with their own Modus login, approves or rejects them. The assistant can't approve on anyone's behalf. - The assistant then passes
confirm: true. The text sent is exactly the text approved, and each batch can be sent only once. - Each recipient passes the contact rules at the moment of sending: people who opted out, are on the do-not-contact list, are already customers, are being handled by a staff member, were messaged in the last 12 hours, or have an automated message due within 24 hours are skipped.
- It is between 9am and 8pm in the business's timezone and not a holiday pause day. Per-person (48 hours) and per-workspace daily limits are enforced atomically, and sending stops if the limit store is unavailable.
Drafted messages can't contain links, web or email addresses, or phone numbers. The assistant never sees or supplies phone numbers; recipients are identified by Modus IDs. Opt-outs apply per person, across every conversation with that number. See the SMS section of our Privacy Policy.
Calendar safeguards
Booking, moving and cancelling appointments work the same way as messaging: the assistant must show the user the person and the exact time, then pass confirm: true. Beyond that:
- Times must be genuinely open on the business's calendar, on its open days (Monday–Thursday for DKA), never same-day, and no more than 90 days out.
- A person with an upcoming appointment can't be double-booked; the assistant is told to move it instead.
- Customers, lost leads and people who opted out are refused.
- Only workspaces Modus has enabled can write to a real booking calendar. Workspaces without one — including the demo workspace reviewers use — record appointments in Modus only: nothing external is touched and no texts are triggered.
- Every call is written to the audit log with who asked, which app, and the outcome.
Data & security
- Least data. Tool results never include phone numbers or email addresses. Conversation text is included only when the assistant asks for one person's details, and athletes' social handles only when explicitly requested.
- Isolation. Every query is scoped to the signed-in user's workspace, using the tenant bound to the access token, never a tool argument.
- Credentials. Authorization codes, access and refresh tokens and client secrets are 256-bit random values stored only as SHA-256 hashes. Connector tokens can't be used against the Modus app, and app sessions can't be used here.
- Sign-in. Modus's own password checks apply: scrypt hashes, account lockout, per-IP throttling and a sign-in audit trail. The consent page can't be framed and has CSRF protection.
- Audit. Every tool call is logged with who, which app, which tool and the outcome. Every message sent through the connector is recorded against the batch it came from.
- Limits. 60 tool calls per minute per connection and 120 per workspace, plus rate limits on sign-in, registration, token and revocation endpoints.
- Transport. HTTPS only. Browser
Originheaders are rejected unless allow-listed, which prevents DNS rebinding.
How Modus collects, uses and protects personal data is described in our Privacy Policy; use of Modus is governed by our Terms & Conditions.
Access requirements
- An active Modus workspace. Businesses without one can request access; Modus sets up each workspace with the business.
- An owner or admin Modus login.
- United States businesses. Messaging uses the business's own registered US texting number.
- Sending messages and prospect search are optional features Modus switches on per workspace. Reporting, lead lookup and drafting are always available.
Disconnecting
Disconnect Modus in the assistant, or ask Modus to revoke every connection for a workspace. Resetting a Modus password ends every connection that person made, and deactivating a staff member cuts off their connections on the very next request.
Contact
Questions, access requests or security reports: hello@himodus.com.