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

Integrations / Event Tickets

Governed integration

Event Tickets MCP abilities

3 governed Event Tickets abilities for AI agents. They appear on your WordPress MCP server only while Event Tickets 5.29.3.1 or newer is active, and stay off until you enable them. Read tickets and attendees for an event (read only, no purchase write).

3 governed abilities Requires Event Tickets 5.29.3.1 or newerRead only

Reaches real personal data

This set can read real customer or field data, so it sits behind a clear admin notice before you enable it. It stays off until you switch it on, runs only for the capabilities of the user you connected, and nothing is sent anywhere: your AI client reads the data it asked for, and the plugin makes no outbound calls of its own.

Needs Event Tickets 5.29.3.1 or newer

On an older Event Tickets these 3 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. Event Tickets also needs The Events Calendar alongside it.

  • Active only while Event Tickets 5.29.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 Event Tickets, then open the Agent Abilities for MCP screen and enable the Event Tickets 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 3 Event Tickets 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 tickets

Read only

List every ticket (RSVP and paid, across every provider) for one event. Requires edit access to that event.

View ability

Get ticket

Read only

Read a single ticket by ID. Requires edit access to its parent event.

View ability

Get attendees

Read only

List attendees/RSVPs for one event, across every provider. Requires edit access to that event.

View ability

Try it with a prompt

Example requests you could paste to your agent once Event Tickets abilities are on.

  1. List the tickets on event 512 and tell me which types are on sale.
  2. Read ticket 733 and show me its price and capacity.
  3. How many people have RSVPd or bought a ticket for event 512 so far?

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 Event Tickets, 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.

Get it on WordPress.orgRead the docs

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