Model Context Protocol | Aroundtime Docs

Aroundtime exposes a remote, authenticated MCP server at:

https://aroundtime.co/mcp

The server uses Streamable HTTP and OAuth 2.1. Dynamic Client Registration remains available for compatible MCP clients.

Connect a client

Use the remote server URL in an MCP client that supports HTTP transport and OAuth. The client discovers authorization metadata from Aroundtime, registers when necessary, and opens a browser consent flow.

The user signs in to Aroundtime and approves the requested permissions. Aroundtime issues an MCP-specific token; the client never receives Google access tokens or a Better Auth session token.

Scopes

Scope	Access
`meetings:read`	List meeting types, read availability, and list upcoming bookings.
`meetings:write`	Create a meeting through an available meeting type.

Write tools reject tokens without meetings:write.

Available tools

list_meeting_types
get_availability
schedule_meeting
list_upcoming_bookings

Scheduling uses the same availability and conflict checks as the public booking page. Clients must provide an idempotency key when creating a meeting.

OAuth endpoints

Authorization metadata: https://aroundtime.co/.well-known/oauth-authorization-server
Authorization:          https://aroundtime.co/authorize
Token:                  https://aroundtime.co/oauth/token
Client registration:    https://aroundtime.co/oauth/register