"calendar" matching MCP servers:

Enables AI assistants to read, create, update, move, and delete calendar events, list calendars, and query free/busy across multiple independent Google accounts through a single interface, with each account routed explicitly and gated by role-based access control. It also includes a built-in personal time-management assistant and stores each account's OAuth tokens in a local encrypted vault.

Lets an AI assistant check your availability by reading private ICS subscription feeds and returning merged busy intervals or open free slots, while keeping event titles, notes, attendees, and feed URLs entirely on the server. Access is read-only and protected by OAuth with a single-account allowlist.

Enables MCP clients to authenticate with Google OAuth and securely access Google Calendar's official MCP server without exposing the Google client secret.

Enables MCP-aware AI clients to call AgentDraft's per-agent inbox, conflict-free calendar booking, and tamper-evident audit trail as tools.

Local macOS MCP server for Calendar and Reminders that gives each AI agent its own token and access to only the calendars and reminder lists you choose, per action. Writes can require your approval in a panel that shows every field.

Enables secure enterprise AI agents to access internal tools like GitHub, Gmail, Calendar, file systems, databases, and knowledge bases through the Model Context Protocol, with built-in security, audit, and observability.

A single MCP gateway that lets every agent and login on your machines reach services like Notion, Sentry, Cloudflare, Gmail and Google Calendar after signing in once, with per-agent tokens. Calls that reach other people or can't be undone wait for approval first, and every call is logged.

Permission gateway that hands an AI agent a scoped MCP endpoint instead of an OAuth token: connect 27 services (Gmail, Google Calendar/Drive/Ads/Search Console, Slack, Notion, GitHub, Jira, Salesforce, HubSpot, Stripe, LinkedIn, X, Meta Ads and more), grant per-action permissions finer than native OAuth scopes, audit every call and revoke a key in one click. Self-hostable, MIT.

Enables MCP clients such as Claude to connect as a custom connector and read mail and calendar data from the doemefu homelab over a remote Streamable HTTP endpoint, authorized by OAuth tokens validated offline against the auth-service JWKS. Exposes read-only tools like list_accounts, with IMAP and CalDAV adapters planned.

Enables agents to read, create, and modify invitations for calendar events through a deny-by-default broker that validates OAuth bearer tokens and intersects server-owned per-subject, per-calendar grants with token scopes. Access is limited to a narrow, data-minimized calendar surface with idempotent writes and fail-closed authorization, rather than arbitrary service or network execution.

Enables authenticated, read-only access to mailbox folders, tags, message metadata, and message text via MCP, while preventing send, draft, delete, move, tag-change, contact/calendar changes, and attachment downloads.

Self-hosted MCP server that filters sensitive data from email and calendar before it reaches AI assistants, masking or withholding confidential content based on user policy.

Demonstrates OAuth 2.0 Dynamic Client Registration with Duo SSO, providing three MCP servers for calendar events, document management, and analytics dashboards.

Enables invited ChatGPT accounts to reach the Sense family calendar and reminder service through an OAuth-protected AWS gateway without exposing the underlying Sense API key. It exposes six read tools plus six optional write tools for events and reminders, with all destructive and administrative actions blocked.

Enables AI agents to read and send email, handle attachments and manage calendar invitations through their own IMAP/SMTP mailboxes, with per-mailbox sender and recipient allow lists and automatic HTML-to-Markdown conversion. It runs as a single self-hosted Docker container, exposing the same tools over MCP and REST.

Recued is a server you run yourself. It sits between AI agents and your accounts. Your mail, calendar, files, and CRM records stay on a machine you control. An agent gets in over MCP, through a contract that lists exactly what it may do. Every action it takes passes one gate. By default, anything that writes or deletes waits for your yes.

An MCP server that lets agents act as the person who added them, giving them identity, shared context (data, documents, goals, calendar, skills), and a place to publish apps and pages behind sign-in. It also brokers access to models, data APIs and other tools' MCP servers through one key, with consent prompts, per-person access checks and encrypted credentials as guardrails.

Provides a single OAuth-secured MCP endpoint that connects AI assistants to a company's CRM, helpdesk, read-only analytics database, knowledge base, calendar and sandboxed email, exposing only the tools each user's role permits and logging every call. Writes require explicit user confirmation with idempotency keys, while customer-authored text is marked as untrusted data so it cannot steer the assistant or leak addresses found only in that text.