allmymeetings Developer Resources
Everything you need to integrate allmymeetings into agents, automation, or your own apps — MCP server, OpenAPI spec, webhooks, authentication, and agent discovery metadata.
MCP Server
allmymeetings ships a production MCP (Model Context Protocol) server that exposes 20 tools and 4 resources for calendar operations, sync pair management, scheduling links, and conflict detection. Agents can control your entire calendar stack through natural language.
- MCP Setup Guide — step-by-step configuration for Claude Desktop, Perplexity, and OpenClaw
/.well-known/mcp/server-card.json— machine-readable server card (SEP-1649)- Calendar endpoint:
https://allmymeetings.com/mcp/calendar(Sanctum bearer token required) - Provisioning endpoint:
https://allmymeetings.com/mcp/provisioning(partner API key required) - Transport: streamable-http (JSON-RPC over HTTP POST)
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
API access uses Laravel Sanctum personal access tokens (PATs). Sign into your account and visit the API settings page to mint a token. Pass it as Authorization: Bearer <token>.
- Token issuance:
/settings/api(requires sign-in) - Token scheme: Bearer, in the
AuthorizationHTTP header - Rate limits: 100–100,000 calls/day depending on plan tier
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://allmymeetings.com/api/webhooks/google— Google Calendar push notificationsPOST https://allmymeetings.com/api/webhooks/microsoft— Microsoft Graph change notificationsPOST https://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/oauth-protected-resource— RFC 9728 protected resource metadata/.well-known/oauth-authorization-server— RFC 8414 authorization server metadata/.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/sitemap.xml— XML sitemap of indexable pages
Quickstart
- Create an account (free tier available).
- Sign in and generate a Personal Access Token at
/settings/api. - Configure your MCP client — see the MCP Setup Guide for Claude Desktop, Perplexity, and OpenClaw snippets.
- Ask your agent to connect a calendar provider. It will run the OAuth flow and create sync pairs through MCP tools.
Support
Questions about the API, MCP tools, or integration patterns? Read the AI power users guide or review the MCP launch post on our blog.