Frequently asked

Questions, answered.

What meet_ is, how it differs from Calendly, what it costs, what data it accesses, and how to get set up. Can't find what you're looking for? Book 15 min with Harry.

What is meet_?

What is meet_?

meet_ is an agent-native scheduling platform. Your AI agent looks after your calendar — protecting focus blocks, lunch and evenings, holding tier-based access so the right people get through and strangers get a polite refusal, and merging your work, personal and family calendars into one view. Humans can still book via a grid; agents book via API or MCP.

How is meet_ different from Calendly?

Calendly and similar tools optimise booking — sharing a link, picking a slot. meet_ optimises your week. It defends focus, lunch and evenings by default, gates access by contact tier, merges multiple calendars into one decision, and exposes the same scheduling primitives to your AI agent via API and MCP. You can still share getmeet.ai/your-namelike a Calendly link — the difference is what's behind it.

Is meet_ for me?

Today: yes if you (a) use Google Calendar, and (b) use Claude — Claude Code, claude.ai, Cursor, or another MCP-capable agent. Claude Desktop works too but needs a manual MCP config (one-click install coming). Outlook, Apple, ChatGPT and other agents are on the roadmap. If none of that describes you, join the waitlist and we'll let you know when we're ready.

Can I use meet_ on my phone?

Today: the getmeet.ai web dashboard works on mobile, but there's no native app yet. Coming soon: a Telegram bot — chat with your meet_ agent, get briefs and decline notifications pushed to your phone, and manage bookings without opening a browser. WhatsApp, iMessage and SMS surfaces are on the longer roadmap. Want the Telegram beta when it lands? Tick Telegram on the messaging-apps question when you join the waitlist.

Is meet_ available now?

meet_is in closed alpha. We onboard small cohorts so each user's agent has time to learn how they work. Claim your handle at getmeet.ai to join the next cohort.

Pricing

What does meet_ cost?

meet_ is free during the alpha cohort. When personal pricing arrives, alpha users get a lifetime 50% discounton personal plans — a thank-you for showing up early. Teams pricing to follow. We're small and lean, and so are our prices.

Setup & onboarding

What do I need to use meet_?

Three things:
  1. A Google Calendar account (Outlook and Apple are on the roadmap)
  2. An AI agent that can connect via Model Context Protocol (MCP) — Claude Code, Cursor, or similar (Claude Desktop works with manual config)
  3. A meet_ handle — claim yours at getmeet.ai/your-name

How long does setup take?

About 5 minutes if you have the prerequisites. Run npx getmeetonce Claude Code is installed and you've signed in at getmeet.ai. The agent walks you through the rest — schedule, profile, first week review. Full guide at /get-set-up.

I don't have Claude Code yet — what do I do?

Install Claude Code from claude.ai/code first (it's free, takes 2 minutes). Then come back to getmeet.ai/get-set-up and run npx getmeet.

Can I use meet_ with Claude Desktop?

Yes — at the protocol level. meet_'s MCP server is HTTP-based and Claude Desktop supports remote MCP servers via its mcp.jsonconfig. Today that's a power-user manual setup (add the server URL + your API key). A one-click npx getmeet --desktopinstall for Claude Desktop is on the near-term roadmap. Email us if you're using Desktop and we'll send the manual config recipe.

I don't use Google Calendar — when can I use meet_?

Outlook (Microsoft 365 / Exchange) and Apple Calendar are on the roadmap. Best signal of when: join the waitlist and pick your calendar — that's how we prioritise the next integration.

Privacy & security

What data does meet_ access?

Your Google Calendar events — read and write — for the calendars you choose to connect. We see times, durations, attendees, and event IDs. We do not store event titles or descriptions on our servers; we only fetch them at request time when the agent needs to reason about a specific meeting.

Who can see my calendar?

Only you, your authorised agents (using your meet_ API key), and bookers who have your booking link see anything. Bookers see availability slots — not your events, not your other calendars. Other meet_ users see nothing about your calendar by default; if both you and another meet_user opt in to mutual-availability, the system can find a slot that works for both without either of you seeing the other's events.

Can I revoke access?

Yes, at any time:
  • Disconnect your Google Calendar from getmeet.ai/dashboard/settings
  • Revoke your API key from getmeet.ai/dashboard/settings (this immediately stops any agent or integration using it)
  • Revoke meet_'s Google access from your Google account settings
  • Delete your meet_ account — clears all stored data within 30 days

Using meet_

Can I undo something my agent did?

Yes. Every booking, reschedule and cancellation made via meet_is fully reversible from your dashboard. The agent never deletes events you created manually — only ones it created on your behalf. If you find an action you didn't expect, hit Undo and tell the agent what happened — it learns.

What happens if my agent makes a mistake?

Two safeguards:
  1. The agent operates within your stated rules (focus blocks, working hours, tier access). It can't book against those rules.
  2. Anything it does is auditable in the dashboard activity feed and reversible.
If something still goes wrong, email support or book 15 min with Harry.

Can other people use meet_ to book me without my permission?

No. Your booking page only goes live once you choose to share getmeet.ai/your-name. Even then, tier-based access (rolling out shortly) means only contacts you've classified can book — strangers see a polite refusal and a request-to-be-added link.

Does my agent run all the time, or only when I'm chatting to it?

meet_'s rules — focus blocks, working hours, tier access, calendar merging — are enforced 24/7 by the platform itself, not by an LLM. Your booking page applies them automatically whether you're online or not. The agent-driven bits (chat with meet_via Claude Code, the forthcoming Telegram bot, briefs and decline notifications) need an MCP-capable AI to be running. Bottom line: your calendar is protected even when you're asleep.

For developers & agent builders

Does meet_ have an MCP server?

Yes. After running npx getmeet, the meet_ MCP server is auto-registered with Claude Code. 15 tools available — schedule, book, propose meetings, check availability, find time, look up contacts. Run /meet help in Claude Code for the full list.

Can my own LLM (not Claude) use meet_?

Yes — anything that supports either MCP or REST API tool calling. The API is provider-neutral. Direct OpenAI / Gemini / Ollama integration is on the roadmap as native one-click installs; today it's a few minutes of wiring.