MeetBetr for developers

MeetBetr finds the times a group of friends is actually free and turns them into plans they answer in one tap. The MeetBetr connector lets an AI assistant do the same for a person who connects their account.

It's an MCP server with three tools: find free times, propose a plan and check a plan. It is consent-first. An assistant sees only the free windows a person's friends already share with that person, never calendar entries, and nothing is sent until the person confirms.

Connecting

An unauthenticated request gets 401 with a WWW-Authenticate header pointing to the resource metadata, so MCP clients discover everything on their own.

Sign-in (OAuth)

• Clients: register dynamically, or use a Client ID Metadata Document (an HTTPS client_id). Public clients use token_endpoint_auth_method: none; client_secret_post and client_secret_basic also work. Partners who prefer a pre-registered client can email us.
• Redirect URIs: HTTPS, loopback HTTP (localhost, 127.0.0.1) or an app's own scheme; matched exactly.
• PKCE: required, S256 only. state is returned unchanged, with iss (RFC 9207).
• Resource indicator (RFC 8707): https://mcp.meetbetr.com.
• Tokens: access tokens last one hour; refresh tokens last 90 days and rotate on every use. Reusing an authorization code ends that connection.
• What the person sees: /authorize sends them to meetbetr.com/connect. They sign in with their phone number and texted code, then allow each permission with its own switch.

Scopes

People see and disconnect their connected assistants at meetbetr.com/connect. Access also ends if they delete their MeetBetr account.

Tools

Times come back in the person's own time zone as ISO 8601 with offsets, plus a readable when. Friends are named the way they appear in the person's MeetBetr ("Nate", "Lindsay K"), or by a saved crew ("soccer team"). Phone numbers are never accepted or returned.

find_free_times read-only

When the person and some of their friends are all free. It uses only the free windows those friends share with this person. Friends who don't share come back as not_sharing, and assistants must not guess for them. It returns up to 5 windows, spread across different days. If nothing works for everyone, it returns the best windows missing one person, marked missing. With days, it looks for whole free days in a row, up to a year out, for trips and weekends away.

// "When are Nate and Lindsay free for dinner next week?"
{ "friends": ["Nate", "Lindsay"], "part_of_day": "evening", "from": "2026-09-28", "to": "2026-10-04" }
→ { "time_zone": "America/Los_Angeles",
    "windows": [ { "start": "2026-09-29T18:30:00-07:00", "end": "2026-09-29T22:00:00-07:00",
                   "when": "Tue, Sep 29, 6:30 PM – 10:00 PM", "free": ["You", "Nate", "Lindsay"] }, … ],
    "friends": [ { "name": "Nate", "status": "shares_free_times" }, … ], "notes": [] }

propose_plan sends, after confirmation

Always two calls. The first, with the plan, returns a draft and sends nothing. The assistant shows the person exactly what will go out, and only after they say yes calls again with { "draft_id": "…", "confirm": true }. Invitees on MeetBetr get a notification. The result also carries a link and a ready-to-send text for anyone who isn't on MeetBetr, which the person sends themselves. Sending the same draft twice returns the same plan.

{ "title": "Tacos at Guisados", "times": [{ "start": "2026-10-02T19:00", "duration_minutes": 120 }],
  "invitees": ["Nate", "Lindsay"], "place": "Guisados" }
→ { "status": "draft", "draft_id": "…", "summary": "\"Tacos at Guisados\" at Guisados, Fri, Oct 2, 7:00 PM – 9:00 PM. To Nate and Lindsay…",
    "warnings": [], "next_step": "Nothing has been sent. …" }

{ "draft_id": "…", "confirm": true }
→ { "status": "sent", "plan_id": "…", "link": "https://meetbetr.com/p/…", "share_text": "…" }

If a proposed time stopped working between the two calls (a calendar changed), the send is refused with conflict and the next best times. A plan for 8 or more people needs an Event Pass or MeetBetr Plus. Without one it returns needs_pass, and the person finishes it in the app. Assistants never buy anything.

check_plan read-only

How a plan is going: collecting, locked or cancelled, who's in, who can't make it, who hasn't replied (for the plan's host), votes per time, the leading time, and the locked time and place. Pass a plan link, its id, or words from its title. Without plan, it lists the person's current plans.

// "Did everyone reply to taco night?"
{ "plan": "taco night" }
→ { "title": "Taco night", "status": "collecting", "going": ["Marcus", "Tyler"], "cant_make_it": ["Sofia"],
    "waiting_on": ["Kevin"], "leading_time": "Sat, Oct 3, 7:00 PM – 9:00 PM", … }

Errors

Tool failures come back as a normal result with isError: true, a code, and a plain sentence the assistant can say out loud.

An expired or revoked access token gets HTTP 401; refresh it, or connect again.

Limits

• 60 tool calls an hour per person, across all their assistants
• 10 plans a day sent through assistants
• 20 invitees per plan
• No one gets more than 2 plans a day from the same person through an assistant

Privacy

• What an assistant can see: free windows (start, end, who's free) for friends who share them with the person, only for the range asked about; the person's own plans and replies; friends' names as MeetBetr shows them to the person.
• What never leaves MeetBetr: calendar entries and their titles, busy times, phone numbers, plan chats, starting areas, purchases.
• Friends stay in control: free times come only from friends who already share with this person in MeetBetr, under the same rules the app enforces.
• Nothing is sent without the person: propose_plan needs a confirmed second call.
• Kept by MeetBetr: a log of each call (who, which tool, when) for 90 days, never a copy of what was returned.

See the full privacy policy and terms.

Support

Questions, a pre-registered client, or a test account for review: support@meetbetr.com.