The Events Calendar MCP — Manage Events with an AI Agent

What is The Events Calendar MCP?

The Events Calendar MCP means running your event listings by asking an AI assistant, instead of filling in the event editor field by field. Cowboy MCP gives an AI agent 13 tools over the Model Context Protocol for The Events Calendar — 11 that list, read, create, update and trash events and manage venues and organizers, plus 2 that appear when Events Calendar Pro is active and handle recurring series and cancelled dates.

MCP is the open standard an AI client uses to discover and call those tools. The same Cowboy MCP plugin that manages your posts, store and plugins detects The Events Calendar, works through the calendar's own event API and re-syncs its date tables after each change, so dates, time zones, venues and organizers are stored the way the calendar expects. The event tools light up on their own when The Events Calendar is active; there is nothing to switch on.

What can an AI agent do with The Events Calendar?

An agent can do the calendar chores that pile up: turn a list of dates in an email into draft events, move a workshop to a new venue, fix the price on next month's sessions, find every event that still has no organizer, or cancel one date of a weekly class without touching the rest of the series. Each tool maps to one real operation, and the names below are the real tool identifiers the agent sees.

Tool	What it does
wp_events_list	List events that overlap a date window (from now on by default), filtered by status, category, venue, organizer, search text or featured; a recurring event appears once, with its series and next date
wp_events_get	Read one event: start and end, time zone, all-day flag, venue, organizers, cost, categories, tags and image — plus, on Pro, the recurrence rule, excluded dates and number of occurrences
wp_events_create	Create an event — saved as a draft unless you ask for another status — with dates in the event's own time zone, venue, organizers, cost and currency, website, categories, tags and featured image
wp_events_update	Change only the fields you name on an event; on a recurring event the change applies to every date in the series
wp_events_delete	Move an event to the trash (undoable), or delete it permanently after an automatic database checkpoint
wp_events_list_venues · wp_events_create_venue · wp_events_update_venue	List venues with their address and number of events, and add or edit venues: address, city, state or province, postcode, country, phone, website, map
wp_events_list_organizers · wp_events_create_organizer · wp_events_update_organizer	List organizers with their contact details and number of events, and add or edit them: phone, website, email
wp_events_list_occurrences (Pro)	List the dates of a recurring event, or of every event in a series
wp_events_exclude_date (Pro)	Cancel one date of a recurring event, or restore a date that was cancelled

With Events Calendar Pro active, wp_events_create and wp_events_update also take a recurrence rule in the standard iCalendar format (RFC 5545) — for example every Tuesday for eight weeks — and can add an event to an existing series. Event categories are chosen from the ones you already have; a new category is created first with the general taxonomy tools.

Three real prompts, to make it concrete:

• "Here are the dates for the spring workshop series. Create a draft event for each one at the Riverside Hall venue, 6–8 pm Berlin time, €15, with Maria as organizer."
• "Which upcoming events have no venue or no organizer? List them, then fill in the ones you can work out from the description."
• "The yoga class on 24 December is off. Cancel just that date and leave the rest of the weekly series alone."

Doesn't The Events Calendar have its own MCP server?

It has one, and it works differently. The Events Calendar team publishes an open-source MCP server, @the-events-calendar/mcp-server, that runs as a Node.js program on your own computer and reaches your site through the REST API with an application password. It has three broad tools — create or update, read, and delete — covering events, venues, organizers and, with Event Tickets, tickets. Its setup guide (opens in new tab) asks for The Events Calendar 6.15+, Event Tickets 5.26+ and Node 20+; version 0.1.6, from 25 August 2025, was the latest on npm as of 7 November 2026.

Cowboy MCP runs inside WordPress instead: there is nothing to install on your computer, AI apps that cannot launch a local program (such as Claude on the web or ChatGPT) connect with a browser sign-in, and every write lands in the undo journal. It also covers Events Calendar Pro recurring series, which the official server's guide does not mention. The official server's advantage is tickets — if your agent needs to manage Event Tickets, it is the one that covers them.

How do event edits stay safe?

A wrong date on a published event reaches every visitor and every calendar feed, so event writes get the same guardrails as the rest of the site. The list and read tools never change anything.

• Drafts first — wp_events_create saves a draft unless you ask for something else, so new events can be checked on the calendar before they go live.
• Dry run — any write can report what it would change without saving, so a batch of new events can be previewed before the first one lands.
• Undo journal — creating or updating an event, venue or organizer, trashing an event and cancelling or restoring a recurring date are each captured with the previous values, so a mistake rolls back from the Activity tab, or by asking the agent to undo it.
• Checkpoint before a permanent delete — trashing is the default. A permanent delete takes a database checkpoint first and is refused if it cannot; a checkpoint restores the whole database to that moment, so it is the last resort, not the everyday undo.

Every call is also written to the audit log, and your MCP client asks you to approve each tool call, so a human stays in the loop at both layers. The full guardrail model lives on the security page, and the undo guide shows what rolling back looks like.

What are The Events Calendar MCP's limits?

The tools cover events, venues, organizers and, on Pro, recurring series — the core of a calendar. A few things stay in wp-admin. Editing a single date of a recurring event on its own, or "this and following events", is wp-admin only: an agent's update to a recurring event applies to the whole series, and cancelling one date is the per-date action it can take. Tickets and RSVPs from the separate Event Tickets plugin are not covered by these tools, and neither are the calendar's own settings — views, date formats and how the calendar page looks.

Recurring-event tools need Events Calendar Pro with its custom tables active; without Pro, the 11 core tools still work and every event is a single event. Venues and organizers are removed with the standard delete-post tool, which trashes them like any other post. Think of the agent as a fast, careful assistant for calendar data entry: it will enter a season of dates before lunch, but which events you run is still your call.

How do I set it up?

Setup takes about five minutes and needs no code. Install the Cowboy MCP plugin on a site that runs The Events Calendar, connect your AI assistant, and start with a read-only request such as listing next month's events.

1. Install the plugin. In wp-admin, go to Plugins → Add New, search for "Cowboy MCP", and click Install then Activate. It is free on the WordPress.org plugin directory (opens in new tab) and needs WordPress 6.2+ and PHP 8.0+.
2. Connect your AI. Open Settings → Cowboy MCP and follow the guided setup. See how to connect WordPress to Claude, how to connect WordPress to ChatGPT, or every supported AI app.
3. Ask for something real. Start read-only — "list every event in the next 30 days with its venue" — then let it create a few drafts and check them on the calendar before you publish.

FAQ