Question 1

What is meet_?

Accepted Answer

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.

Question 2

How is meet_ different from Calendly?

Accepted Answer

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-name like a Calendly link — the difference is what's behind it.

Question 3

Is meet_ for me?

Accepted Answer

Today: yes if you (a) use Google Calendar, and (b) use Claude — Claude Code, Claude Desktop, claude.ai, Cursor, or another MCP-capable agent. Outlook, Apple, ChatGPT and other agents are on the roadmap. If neither describes you, join the waitlist at getmeet.ai/join.

Question 4

Is meet_ available now?

Accepted Answer

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.

Question 5

What does meet_ cost?

Accepted Answer

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

Question 6

What do I need to use meet_?

Accepted Answer

Three things: a Google Calendar account (Outlook and Apple are on the roadmap), an AI agent that can connect via Model Context Protocol (MCP) such as Claude Code, Claude Desktop, or Cursor, and a meet_ handle claimed at getmeet.ai/your-name.

Question 7

How long does setup take?

Accepted Answer

About 5 minutes if you have the prerequisites. Run npx getmeet once Claude Code is installed and you've signed in at getmeet.ai. The agent walks you through the rest. Full guide at getmeet.ai/get-set-up.

Question 8

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

Accepted Answer

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.

Question 9

Can I use meet_ with Claude Desktop?

Accepted Answer

Yes — at the protocol level. meet_'s MCP server is HTTP-based and Claude Desktop supports remote MCP servers via its mcp.json config. Today that's a power-user manual setup (add the server URL plus your API key). A one-click 'npx getmeet --desktop' install for Claude Desktop is on the near-term roadmap.

Question 10

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

Accepted Answer

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

Question 11

Can I use meet_ on my phone?

Accepted Answer

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.

Question 12

What data does meet_ access?

Accepted Answer

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.

Question 13

Who can see my calendar?

Accepted Answer

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.

Question 14

Can I revoke access?

Accepted Answer

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

Question 15

Can I undo something my agent did?

Accepted Answer

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.

Question 16

What happens if my agent makes a mistake?

Accepted Answer

Two safeguards: (1) the agent operates within your stated rules (focus blocks, working hours, tier access) and 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@getmeet.ai or book 15 minutes with Harry.

Question 17

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

Accepted Answer

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.

Question 18

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

Accepted Answer

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.

Question 19

Does meet_ have an API?

Accepted Answer

Yes. Get an API key from getmeet.ai/dashboard/settings. The v1 API covers calendar read/write, bookings, availability, contacts and event types. Auth is Authorization: Bearer mk_...

Question 20

Does meet_ have an MCP server?

Accepted Answer

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.

Question 21

Can my own LLM (not Claude) use meet_?

Accepted Answer

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