A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Meet.bot MCP is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
AI-native scheduling and booking: check availability, book meetings, share links.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http meet-bot-mcp https://mcp.meet.bot/
# 2 — ask your agent for something these tools do
# get_scheduling_pages, get_page_info, get_available_slots and 5 more
Meet.bot MCP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http meet-bot-mcp https://mcp.meet.bot/Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get all scheduling pages for the authenticated user
No parameter schema on file.
Get information about a specific scheduling page
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | string | yes | The URL of the scheduling page (e.g. https://meet.bot/your-page) |
Get available booking slots for a scheduling page
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | string | yes | The URL of the scheduling page (e.g. https://meet.bot/your-page) |
| count | number | no | Maximum number of slots to return (defaults to server limit) |
| start | string | no | Start date for the range in YYYY-MM-DD format |
| end | string | no | End date for the range in YYYY-MM-DD format |
| timezone | string | no | IANA timezone for slot times (e.g. America/New_York, Europe/London) |
| booking_link | boolean | no | If true, include shareable booking links in the response |
Book a new meeting slot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | string | yes | The URL of the scheduling page (e.g. https://meet.bot/your-page) |
| guest_email | string | yes | Email address of the guest (used for calendar invite and confirmation) |
| guest_name | string | yes | Full name of the guest |
| notes | string | no | Optional notes to include with the meeting (e.g. agenda, call details) |
| start | string | yes | Start time in ISO 8601 format (e.g. 2025-03-10T14:00:00Z); must be an available slot |
Check if the Meet.bot API client is healthy and the Bearer token is valid
No parameter schema on file.
List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled)
No parameter schema on file.
Create or update an outbound booking webhook. Omit id to create (webhook_url required); pass id to update. Meet.bot POSTs a JWT-signed (HS256) JSON payload to the URL on each booking event.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | no | Webhook id to update; omit to create a new one |
| webhook_url | string | no | HTTPS URL we POST booking events to (required when creating) |
| description | string | no | Optional label for the webhook |
| coverage | string | no | 'all' (default) fires for every page including ones created later; 'selected' only for the pages in pages |
| scope | string | no | 'self' (default) your own pages; 'team' (team admins only) also fires for teammates' bookings |
| pages | array | no | Page ids to cover when coverage='selected' |
| is_active | boolean | no | Whether the webhook is active (default true) |
Delete one of the authenticated user's webhooks by id
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | The webhook id to delete |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Meet.bot MCP or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Meet.bot MCP can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.