Integrations / The Events Calendar

Governed integration

The Events Calendar MCP abilities

13 governed Events Calendar abilities for AI agents. They appear on your WordPress MCP server only while The Events Calendar 6.17.3.1 or newer is active, and stay off until you enable them. Events, venues, and organizers, through the calendar's own ORM.

13 governed abilities Requires The Events Calendar 6.17.3.1 or newerGuarded write

Governed exactly like core

These abilities are off until you enable them, capability-checked before every call, and written to the same audit log as everything else. There is no separate trust model for integrations.

Needs The Events Calendar 6.17.3.1 or newer

On an older The Events Calendar these 13 abilities do not register at all, so your agent is offered none of them rather than a reduced set. Below that version the abilities do not register at all. The calendar's ORM is what these are built on, so an older host would mean tools that load but cannot do the thing they promise.

  • Active only while The Events Calendar 6.17.3.1 or newer is installed and active
  • Off by default, enabled one ability at a time
  • Capability-gated on every call, discovery and execution separately
  • Logged like core, denials included, keys and identifiers, never free-text

How to turn it on

Activate The Events Calendar, then open the Agent Abilities for MCP screen and enable the The Events Calendar abilities you want. Connect your client to the endpoint on the Connection tab. The address below is illustrative; your real one shows there.

Illustrative endpoint (your real one shows on the Connection tab)https://your-site.com/wp-json/…/mcp

The 13 Events Calendar abilities

Each one is off until you enable it and capability-checked on every call. Open any card to see how it is governed.

Get events

Read only

List events via the Events Calendar ORM (tribe_events()), filtered by an optional free-text search term and an optional `status` input. Defaults to publish; draft/pending/future require edit access to events (scoped to the caller's own unless they can edit others' events); private requires read-private access.

View ability

Get event

Read only

Read a single event by ID, including its start/end dates, venue, and organizers.

View ability

Create event

Guarded write

Create an event via the Events Calendar ORM. Requires the edit_tribe_events capability; a publicly-visible status additionally requires publish_tribe_events.

View ability

Update event

Guarded write

Update an event by ID via the Events Calendar ORM. Requires edit access to that event. Status changes route through the same shared status-authority chokepoint as update-post; organizer_ids and all_day map onto the real ORM repository behavior (clearing with an empty array, and un-setting the all-day meta key rather than writing a falsy value).

View ability

Delete event

Guarded write

Trash an event by ID (goes to Trash, matching this plugin's trash-post convention, never a permanent delete). Requires delete access to that event.

View ability

Get venues

Read only

List venues via the Events Calendar ORM (tribe_venues()). Defaults to whatever the caller can already see (publish, plus private with read-private access); draft/pending/future require edit access to venues (scoped to the caller's own unless they can edit others' venues).

View ability

Get venue

Read only

Read a single venue by ID.

View ability

Create venue

Guarded write

Create a venue via the Events Calendar ORM. Requires the edit_tribe_venues capability. Defaults to draft; publish requires the publish_tribe_venues capability.

View ability

Update venue

Guarded write

Update a venue by ID via the Events Calendar ORM. Requires edit access to that venue. Setting status to publish requires the publish_tribe_venues capability.

View ability

Get organizers

Read only

List organizers via the Events Calendar ORM (tribe_organizers()). Defaults to whatever the caller can already see (publish, plus private with read-private access); draft/pending/future require edit access to organizers (scoped to the caller's own unless they can edit others' organizers).

View ability

Get organizer

Read only

Read a single organizer by ID.

View ability

Create organizer

Guarded write

Create an organizer via the Events Calendar ORM. Requires the edit_tribe_organizers capability. Defaults to draft; publish requires the publish_tribe_organizers capability.

View ability

Update organizer

Guarded write

Update an organizer by ID via the Events Calendar ORM. Requires edit access to that organizer. Setting status to publish requires the publish_tribe_organizers capability.

View ability

Try it with a prompt

Example requests you could paste to your agent once The Events Calendar abilities are on.

  1. List the published events coming up and tell me which ones have no venue set.
  2. Read event 512 and show me its start time, venue, and organizers.
  3. Draft a new event for the launch meetup next month and leave it unpublished so I can check it.
  4. Update the start time on event 512 and point it at the Riverside Hall venue.
  5. List our venues and organizers so I can see which ones are duplicates.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Back to all integrations

Add The Events Calendar, keep the same control.

Every integration ability is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Active only while its host plugin is on, and gated like core.