Events integration
The Events Calendar MCP
The Events Calendar stores each event as a tribe_events custom post type with its schedule in underscore-prefixed _Event* postmeta (_EventStartDate, _EventEndDate, _EventVenueID, and so on). Those keys are protected meta that WP MCP's generic get-post tool deliberately hides, so this integration adds a curated, TEC-aware read: list events, and read one event's schedule as clean named fields (dates, all-day, venue and organizer ids, cost, URL). Creating and editing events is available through the general content tools, since tribe_events is an ordinary post type, with every write snapshotted first.
In practice
How The Events Calendar work goes with an agent.
The Events Calendar stores an event's local start and end, a UTC start, an optional external URL and a cost string, all as _Event* postmeta on a tribe_events post. The detail that matters for scheduling questions is time zones. get-event returns the local start and end plus start_date_utc, though not a UTC end, so an agent comparing events across zones should use the UTC field. list-events only carries the local start and end, and sorts by post date, so it is a finder, not a calendar. The read is for answering questions, with no writes of its own.
Which events start in the next seven days? Use UTC.
Runs tec-read list-events for a page of events, then get-event on the candidates to read start_date_utc. List rows carry the local start and end only, so the UTC comparison needs the per-event read.
Which of our events have an external link, and which are free?
Runs tec-read get-event per event and reads the url and cost fields as TEC stored them. Read only.
Show me the events that are still drafts.
Runs tec-read list-events with status set to draft. Only events the current user may read are returned, and the total reflects the same rule.
What venue and organizer does the Gala have?
Runs tec-read get-event for the Gala and returns venue_id and organizer_id as numeric ids. This operation does not look them up, so it does not return names.
What your AI can do
Real The Events Calendar operations, every write reversible.
- List events with titles and start/end dates
- Read one event's curated schedule, including the underscore-prefixed fields
- Answer scheduling questions without knowing TEC's meta keys
- Create or edit events through the content tools (snapshotted)
Example prompts
Example The Events Calendar prompts.
What are the next few events and their dates?
Read the Gala event: start and end time, venue, and cost.
List events happening in September.
Under the hood
The The Events Calendar calls, under the hood.
tec-read({ operation: "list-events" }), events with dates
tec-read({ operation: "get-event", args: { event_id: 42 } }), surfaces _Event* meta as named fields
Safety and access
What can be undone on The Events Calendar, and what costs what.
Recoverable on The Events Calendar
- Both tec-read operations only read, so there is nothing to undo.
- Event edits made through WP MCP's general content tools are snapshotted by those tools and rolled back there.
The Events Calendar limits and opt-ins
- No write operation: the pack cannot change an event's dates, venue or cost.
- list-events orders by post date, not event date, and its rows carry the local start and end only.
- Venue and organizer come back as ids, not names.
- Ticket and RSVP data is not read.
- Only the events the current user may read are returned.
Free or Pro: Both operations, list-events and get-event on the tec-read pair, are part of the free plugin. Nothing is gated to Pro, and no opt-in filter is involved, because the pack only reads. The integration switches on whenever the tribe_events post type exists. WP MCP Pro adds nothing to this pack.
In the free plugin
The The Events Calendar integration is in the free plugin.
The core The Events Calendar tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.
Frequently asked
The Events Calendar MCP: questions, answered.
Why a dedicated integration instead of the content tools?
The Events Calendar keeps event details in _Event* postmeta, which is underscore-prefixed protected meta that WP MCP's general get-post tool hides. The tec-read surface reads those keys directly and returns them as clean named fields. Creating and editing events still works through the content tools, snapshotted.
Do I need The Events Calendar Pro or Event Tickets?
No. The integration switches on when the tribe_events post type exists and reads event meta from it. It does not read ticket, RSVP or attendee data, so those add-ons neither help nor get in the way. The fields it returns are the schedule, venue and organizer ids, cost and URL.
Why does get-event show start_date_utc?
TEC stores a UTC copy of the start alongside the local start. Returning it lets an agent compare events across time zones without guessing the site's offset. There is no UTC end in the curated read, so end times are in the site's local time.
Are venues and organizers returned by name?
No, by id. get-event returns venue_id and organizer_id as stored in the event's meta. An agent can tell that two events share a venue, but the name is not part of this read, so ask for it elsewhere or look it up in TEC.
Is the list sorted by when events happen?
No. list-events returns newest first by post date. Each row includes the local start_date and end_date, so the agent sorts or filters them itself. For a long calendar, page_size goes up to 100 and page walks through the rest.
Related integrations
More integrations for the same agent.
MCP for Modern Events Calendar
FreeEvents, 3 tools.
MCP for Amelia
ProEvents, 2 tools.
MCP for Elementor
ProPage builders, 14 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
MCP for Bricks
ProPage builders, 3 tools.
MCP for Divi (4 and 5)
ProPage builders, 3 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.