User manual — Xabia Modern Events Calendar (MEC add-on)

Addon: Xabia MEC v1.0.3 · Core required: ≥ 1.0.166 (recommended)

Quick Installation Guide

1. Install and activate Xabia Agent Core ( v1.0.166 or higher recommended).
2. Install and activate the Xabia MEC ZIP ( xabia-mec-1.0.3.zip ) from Plugins → Add new → Upload plugin .
3. In Xabia Agent → Addons , activate or synchronize the xabia-mec subscription until you see Hub Polar: active .
4. If the events are on the same WordPress site, also activate Modern Events Calendar and publish mec-events .
5. If the events are on another website, a local MEC is not needed: fill in the remote SQL credentials in the agent and use Information Source → Native Addon → MEC .
6. Click Connect and Map , review the column preset, and save the agent.
7. Click Sync Data and, if using vector search, Train AI .
8. Try asking questions like “what events are happening this weekend?” in Playground before publishing the shortcode.

CPT Assistant (≥ Core 1.0.162): with MEC addon source, lists only mec-events (validates in remote SQL if a host exists). Hybrid Remote (≥ 1.0.163): if you configure a SQL host, the catalog is treated as remote even if MEC is installed locally (avoids mixing IDs). Deep schema includes mec_available_slots and mec_* tags.

Part 1 — What it is and what it is for

1.1 Brief definition

Xabia MEC is a standalone plugin that is installed alongside Xabia Agent Core . It connects your assistant (for example, Izar or another configured agent) with Modern Events Calendar (MEC) to:

• Synchronize the site’s event calendar to the agent’s knowledge base (text and, if configured, vectors for semantic search).
• Respond with dates, locations, prices, categories, and texts taken from the published events.
• Show available slots when MEC has defined capacity and registered reservations (calculated field mec_available_slots ).
• Offer booking buttons ( [ACTION:BOOK] ) that take the visitor to the event page with a booking anchor ( #book ) when the event has booking/tickets set up in MEC.
• Optionally expose a REST feed for federation (Xabia Central or other nodes) with published events and knowledge-aligned metadata.

It does not replace the MEC panel or the legal settings for pricing, cancellations, or payment gateways; it is a layer of conversation and information about the data you already have in WordPress.

1.2 What problem does it solve?

Without this add-on, an assistant can only make up dates or copy static text.

With Xabia MEC , responses can be based on SQL queries coordinated to mec-events posts and regular MEC metadata, and on context rules that help AI interpret questions like “what’s happening this weekend?” or “are there any places left?”.

1.3 Product identification (useful reference)

• Checkout Polar (subscription): https://buy.polar.sh/polar_cl_wEzwnqMvZIrPelny1I5HNIsdcVjGs1UO12Roj3zzxIm
• Polar Product ID (UUID): 8078756b-c566-4557-a55d-3712d8e47c44 — you can request it from support if you manage billing or webhook in the Hub.

1.4 Essential requirements

Part 2 — Step-by-step installation

2.1 Before starting

1. Have the ZIP files : Xabia Agent Core and Xabia MEC (and MEC from the official Webnus repository if you don’t already have it).
2. Confirm that your hosting allows REST API ( /wp-json/ ) if you will be using federation or cloud integrations.

2.2 Recommended activation order

1. Xabia Agent Core → Activate.
2. Modern Events Calendar → Activate.
3. Xabia MEC → Activate after Core.

If you activate Xabia MEC without the Core, you will see a warning on the desktop: you must first activate Xabia Agent Core .

2.3 Install Xabia MEC from ZIP

1. Log in as administrator .
2. Plugins → Add new → Upload plugin .
3. Choose the Xabia MEC ZIP file.
4. Install now → Activate plugin .

2.4 Verify that WordPress recognizes the plugin

Xabia MEC should appear in Plugins . In Xabia Agent → Addons , the “Xabia — Modern Events Calendar” card should display the WordPress status (active / installed / not installed) next to the xabia-mec/xabia-mec.php file.

Part 3 — “Addons” screen: Polar subscription and license

Open Xabia Agent → Addons .

There you can manage all the commercial options of the MEC add-on.

3.1 General screen texts

• Title “Addons” and subtitle: explain that the Hub Polar badges are the valid subscription on the Xabia server, independent of whether the plugin is active in WordPress.
• “Sync licenses with the hub” button (Polar area top bar): Forces the Hub to re-verify all subscription cards. Use this after paying in Polar or pasting a new key.
• “Open WordPress plugins” : Quick access to plugins in case you need to activate Xabia MEC .

3.2 “Xabia — Modern Events Calendar” card — each item

3.3 After buying from Polar

1. Copy the license key that Polar gives you.
2. In Addons , paste it onto the MEC card and press Activate / Update subscription .
3. Click Sync License or Sync Licenses with the global hub .
4. Wait a few minutes if the Hub applies delayed activation and reload the Addons page.

Part 4 — Agent Configuration (source «Addon MEC»)

Enter Xabia Agent , create or edit the agent that should know about the events.

4.1 Select font type

In «Source of information» ( source_type ):

• Choose “Native Addons (External Connector)” only if your Core installation detects active native connectors (includes Xabia MEC when the Hub and MEC license in WordPress are correct).
• If you don’t see the option enabled, check that Xabia MEC is active and that Addons shows Hub Polar: active for MEC.

4.2 Addon selector ( addon_slug )

In the section that appears when you choose Addon , expand the list and select the entry named MEC — Modern Events Calendar (internal slug mec ). This is the connector registered by the Xabia MEC plugin.

4.3 Informative notice below the selector

When MEC is selected, you will see the text with the icon:

MEC Add-on active: Reservation and availability fields are automatically synchronized.

It serves as a reminder that you don’t have to manually invent columns of “places” if you use the standard preset.

4.4 “Connect and Map” Button

1. Press “Connect and Map” .
2. The system executes a test query with the connector’s SQL (up to one row) to list actual columns .
3. If the Hub license is not active for MEC, you will see an error indicating that the subscription is required; you will not be able to prefix the mapping until it is activated.
4. If all goes well, it receives columns and, for MEC, a preset of mapping rows ( fields ) that it can apply to the attribute table.

4.5 Mapping preset fields (official catalog)

Each row in the mapping has: a CSV/SQL column , a readable label , a visual role , an ENTITY (checkbox), and a statement . The logical order of the connector is:

You can add extra columns with CPT Wizard or other Core tools, but the preset covers the standard flow.

4.6 Remote database connection (host, SQL)

Xabia MEC follows the same pattern as Xabia Woo: the agent can use native Addon → MEC even if the events are on another website.

Use this mode when:

• The site where the chat is located has Xabia Agent Core and Xabia MEC active.
• The actual events are in a remote WordPress database, for example bilbaobizkaiapride.com .
• It wants to preserve the semantic rules of the MEC addon (dates, places, categories, qualitative availability), but read the data by remote SQL.

Steps:

1. In Information Source , select Native Addon (automatic connector) .
2. In the drop-down menu, choose Modern Events Calendar (MEC) .
3. Fill in Host , DB , User , Password and, if applicable, Prefix ( wp_ , wpdb_ , etc.).
4. Press Connect and Map .
5. Save the agent, synchronize data, and train if using vectors.

If the Prefix field is left empty, the Core attempts to detect the active prefix of the remote database and uses wp_ as a fallback.

4.6.1 Alternative: remote MEC preset from pure SQL

If you are not going to install Xabia MEC on the chat site, you can use the Core directly:

1. Choose External Database (Remote SQL) .
2. Press Use remote MEC preset .
3. Fill in remote SQL credentials and test the query.
4. Save, sync, and train.

This alternative creates an event catalog via SQL ( sql_preset = mec_remote ) and automatic mapping, but it doesn’t load all the capabilities of the MEC add-on. For commercial installations with an active license, the recommended workflow is Native Add-on → MEC .

4.7 Save the agent

Press “Save Agent” (or the equivalent button on your screen) to persist source_type , addon_slug , mapping, and SQL credentials.

Part 5 — Agent Sidebar: Memory, Synchronization, and Playground

When you edit an existing agent (not an empty “new” agent), you’ll see the memory sidebar. Each control does the following:

Part 6 — How Modern Events Calendar Should Be Set Up in WordPress

The add-on reads what MEC already stores, so that reservations and available spaces make sense.

1. In ME Calendar → Settings → Bookings , activate the booking module if you use the MEC booking function (according to Webnus documentation / your Lite or Pro edition).
2. For each event , configure entry/ticket limits if you want there to be a calculable capacity .
3. Publish or schedule events ( publish / future ); the connector SQL filters dates from today and root events ( post_parent = 0 ) to avoid duplicating child occurrences in the index.

If an event does not have online booking, the system may omit the [ACTION:BOOK] button even if the AI suggests informational text.

Part 7 — Visitor Experience in Chat

7.1 Questions that the MEC context helps to interpret

Thanks to the search rules injected into the router, the model tends to use well:

• Dates and expressions like “this weekend” (the system suggests filtering by the Date column).
• Slots when there is a numeric mec_available_slots .
• Place ( Lugar / mec_location ).
• Categories and tags joined in Categories_Tags .

7.2 Booking button

When the project uses the MEC booking engine and the event has booking enabled, the response can include a link or button that opens the event page (with a default booking anchor).

In remote MEC catalogs without a local MEC in the WordPress chat, Xabia does not generate local booking buttons ( [ACTION:BOOK:ID] ) from Core ≥ 1.0.202 : the assistant always sends a link to the Link field of the remote event ( [ACTION:URL:Link] ). If the event has a booking on the source website, that remote record will manage the process.

7.3 Privacy

The visitor only sees what the chat plugin displays. Messages are processed according to the Core configuration (AI provider, Hub, etc.).

Please refer to your site’s privacy policy and the Core Manual .

Part 8 — MEC Federation Bridge (menu «MEC Bridge»)

When Xabia MEC is active, “MEC Bridge” appears in the Xabia menu (submenu under agent settings).

8.1 What the screen shows

8.2 GET Parameters (API)

• per_page (1–200, default 100).
• page (pagination).

Only mec-events with status published or scheduled , root ( post_parent = 0 ), ordered by mec_start_date .

Part 9 — Recurrence and one row per series

The connector is designed to index a root event per series with the next date in MEC metadata (it does not expand dozens of rows for each repetition if MEC represents them as children). If your case uses only child events, consult with support or an integrator to adjust SQL via custom maintenance.

Part 10 — Common problems and checklist

Quick checklist: Core ≥ 1.0.24 → MEC active → Xabia MEC active → Hub active → Source addon + mec → Connect and Map → Save → Sync data → Train (if applicable) → Test in Playground .

Part 11 — Good practices

• Keep MEC updated and review canceled events to avoid offering outdated dates until the next synchronization.
• Use clear categories so that the agent can filter properly from Categorias_Tags .
• Always test real booking in a private window after changing the event template.
• Document internally who has the Polar key and who can press Sync License .

Part 12 — Support

• Xabia / Digixop (installation, Core and MEC addon licenses, Hub): usual contact help@xabia.ai .
• Polar Billing : Use the customer portal linked from Addons when the subscription is active.
• MEC calendar issues (Webnus plugin bugs, styles, shortcodes): Webnus/MEC support .

For main license, tokens and wallet , open the Core Manual .