AllMyMeetings Developer Resources

MCP Server

AllMyMeetings runs a remote MCP (Model Context Protocol) server with 21 tools and 4 resources for availability, conflict checks, event create/update/delete, calendar connections, sync pairs and scheduling links. Tool names are kebab-case, for example get-availability-tool and create-sync-pair-tool. Every plan can use it, including the free plan; plan limits apply to what an agent creates.

• MCP Setup Guide — Claude and ChatGPT connectors, plus token configs for other clients
• /llms-full.txt — full agent docs, with every tool name, description and resource URI generated from the live server
• /.well-known/mcp/server-card.json — machine-readable server card (SEP-1649)
• Calendar endpoint: https://staging.allmymeetings.com/mcp/calendar (OAuth 2.1 access token or personal access token, see Authentication)
• Signup endpoint: https://staging.allmymeetings.com/mcp/signup (public; create_account starts a new account and emails the user a confirmation link — no token is returned)
• Transport: Streamable HTTP (JSON-RPC over HTTP POST)
• Resources: amm://events/today, amm://events/week, amm://availability/today, amm://sync/status

OpenAPI Specification

AllMyMeetings publishes a machine-readable OpenAPI 3.1 spec covering the MCP and webhook surfaces. Import this into Postman, Insomnia, or any OpenAPI-compatible tool.

• /openapi.json — OpenAPI 3.1 specification (JSON)

Authentication

The MCP endpoint accepts two kinds of bearer token in the Authorization header.

OAuth 2.1 (connector-style clients)

Claude custom connectors (claude.ai and Claude Desktop), ChatGPT connectors and other OAuth-capable MCP clients discover the authorization server, register themselves and send the user through sign-in and consent. No token is copied by hand.

• /.well-known/oauth-protected-resource — protected resource metadata (RFC 9728)
• /.well-known/oauth-authorization-server — authorization server metadata (RFC 8414)
• POST https://staging.allmymeetings.com/oauth/register — dynamic client registration (RFC 7591)
• https://staging.allmymeetings.com/oauth/authorize and POST https://staging.allmymeetings.com/oauth/token — authorization code flow with PKCE

Personal access tokens (other clients and scripts)

• Token issuance: /settings/api (requires sign-in)
• Scopes: read-only or read-write. A read-only token doesn’t see tools that change data.
• Expiry: 30, 90 or 365 days
• Scheme: Authorization: Bearer <token>

Rate limits

MCP calls are limited per user per day by plan: 100 on Free, 1,000 on Pro (including the 14-day trial) and 10,000 on Business.

Webhooks

AllMyMeetings receives webhook notifications from calendar providers to keep sync pairs current. These endpoints are consumed by the platform; they are not general-purpose write APIs.

• POST https://staging.allmymeetings.com/api/webhooks/google — Google Calendar push notifications
• POST https://staging.allmymeetings.com/api/webhooks/microsoft — Microsoft Graph change notifications
• POST https://staging.allmymeetings.com/api/webhooks/stripe — Stripe billing events

Agent Discovery Metadata

We publish standard agent-readable discovery endpoints so AI clients can find our APIs, skills, and authentication flow automatically.

• /.well-known/api-catalog — RFC 9727 linkset describing all service endpoints
• /.well-known/mcp/server-card.json — MCP server card (SEP-1649)
• /.well-known/agent-skills/index.json — Agent Skills Discovery index

Content Negotiation for Agents

Send Accept: text/markdown to the homepage to get an LLM-friendly markdown summary of AllMyMeetings. The homepage also emits RFC 8288 Link response headers pointing to the resources above.

• /llms.txt — product summary in markdown, ready for LLM ingestion
• /llms-full.txt — full agent docs: MCP tools, resources, authentication and plans
• /sitemap.xml — XML sitemap of indexable pages

Quickstart

1. Create an account (the free plan works).
2. If your client supports OAuth, point it at https://staging.allmymeetings.com/mcp/calendar and sign in. Otherwise, create a personal access token at /settings/api and send it as a bearer token.
3. Call tools/list to discover the 21 tools, or read /llms-full.txt.
4. Use initiate-calendar-connection-tool to connect a provider (the user completes the Google or Microsoft sign-in), then create-sync-pair-tool or the event tools.

Support

Questions about the API, MCP tools or integration patterns? Email [email protected], or see the MCP server guide.