Summary
Drive Microsoft Bookings (Microsoft 365 scheduling product) via the Graph API: businesses, services, staff, appointments, customers. 8 tools, OAuth2 Bearer auth.
Guided setup
Connect Microsoft Bookings to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Microsoft Bookings in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Microsoft Bookings
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Microsoft Bookings, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Microsoft Bookings + Microsoft Copilot
Drive Microsoft Bookings (Microsoft 365 scheduling product) via the Graph API: businesses, services, staff, appointments, customers. 8 tools, OAuth2 Bearer auth.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
MICROSOFT_GRAPH_ACCESS_TOKEN
Step 1 — Get credentials
0 — Bookings endpoints (learn.microsoft.com/en-us/graph/api/resources/booking-api-overview).
Setup:
- Register an Azure AD app at https://portal.azure.com → App registrations → New registration.
- API permissions → Microsoft Graph → Delegated (or Application) → add:
Bookings.Read.All,BookingsAppointment.ReadWrite.All(write needs admin consent). - Run OAuth2 authorization-code (or client-credentials) flow against
login.microsoftonline.com/{tenant}/oauth2/v2.0/tokento get an access token. - Set
MICROSOFT_GRAPH_ACCESS_TOKEN.
Authentication: Authorization: Bearer ${MICROSOFT_GRAPH_ACCESS_TOKEN}.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Microsoft Bookingstools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
microsoft_bookings_list_businesses | List all Bookings Businesses (mailbox-style booking pages) on the tenant |
microsoft_bookings_get_business | Get a Booking Business by ID with its public profile |
microsoft_bookings_list_services | List services (offerings) of a Booking Business |
microsoft_bookings_list_staff_members | List staff members of a Booking Business |
microsoft_bookings_list_appointments | List appointments (bookings) in a Booking Business |
microsoft_bookings_get_appointment | Get one appointment by ID |
microsoft_bookings_create_appointment | Create a booked appointment |
microsoft_bookings_cancel_appointment | Cancel an appointment |
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?
