Agent Abilities
GitHubGet it free
Features
Abilities
Browse all abilities

WordPress core

ContentTaxonomies & TermsCommentsUsersMediaSite settingsPluginsThemes & stylesBlocksMenusSearch

Integrations

WooCommerceAdvanced Custom FieldsRank Math SEOYoast SEOAll in One SEOSlim SEOThe Events CalendarEvent TicketsAvadaGeoDirectory
Integrations
All integrationsWooCommerce52Advanced Custom Fields7Rank Math SEO5Yoast SEO3All in One SEO3Slim SEO2The Events Calendar13Event Tickets3Avada2GeoDirectory4
Bridge
Bridge overviewPlugin directory196

Most installed

Elementor Website BuilderYoast SEOWooCommerceAkismet Anti-spamWPFormsRank Math SEOWP Mail SMTPWPCode
AI clients
All clientsChatGPTClaude.aiClaude DesktopManusClaude CodeCursorVS CodeWindsurfGemini CLI
Resources
DocsChangelogPrompt LibraryBlogComparisonsSupport
GitHubGet it free

Governed ability

Create event

aafm/tec-create-eventGuarded write

Create event is a governed The Events Calendar ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.

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

How it is governed

The same model as every ability in the plugin, stated for this one.

  • Off until you enable it

    Like every ability, Create event ships switched off. You turn it on one at a time, and an update never widens access on its own.

  • Guarded write

    Writes stay conservative, and the plugin re-checks the capability before the call runs.

  • Capability gated

    A connection only sees Create event if the user you connected can run it, and the plugin checks that capability again before it executes.

  • Every call audited

    The call is written to the log in your own database, denials included, with the argument keys and the identifiers it touched, never free-text content.

Create event is one of the 13 governed The Events Calendar abilities. See the full The Events Calendar MCP integration.

See it in action

An illustrative run. Your real calls and data stay on your own site.

agent-abilities · auditGoverned
YouCreate event on this site.
RunRunning aafm/tec-create-event
GateAllowedcapability re-checked before running
Auditaafm/tec-create-event · principal: editor · args: event_id
ResultApplies the change, then writes the call to the audit log.

Try it with a prompt

Example requests you could paste to your agent.

  1. Create a draft event called Spring Product Clinic for the 14th of April.
  2. Add a new event to the calendar with a start time, an end time, and a venue.
  3. Set up next month's community meetup as an unpublished event so I can review it.

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.

Frequently asked

Short answers for Create event.

Can it publish the event straight away?

Only with the right capability. Creating an event requires edit_tribe_events, and a publicly visible status additionally requires publish_tribe_events.

How is the event created?

Through The Events Calendar's own ORM, the same path the calendar itself writes through, rather than a direct database insert.

What controls it?

Create event is a guarded write, off until an administrator enables it, capability gated, and recorded in the audit log with the acting user.

Related abilities

More in The Events Calendar.

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

Back to all abilities

Governed by default, from the first call.

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

Get it on WordPress.orgRead the docs

Every ability off until you enable it, capability-gated on every call.