For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/event-temple
Skill page: https://www.mcpbundles.com/skills/event-temple
Tools: 62
Live probe refreshed Nov 17, 2026 · Endpoint host mcp.mcpbundles.com
AI Skill
SKILL.md
Domain knowledge for Event Temple — workflow patterns, data models, and gotchas for your AI agent.
Event Temple
Sales and catering CRM for hotel groups and independent properties. Connect with your Event Temple API key only; the platform discovers which properties your key can access.
Every CRM read/write (except get_organizations) requires organization_id — the numeric property id from get_organizations. There is no default property; pick the hotel for each call.
Hierarchy
Organization (property) → Accounts & contacts → Bookings (deal) → Events & groups (room blocks) → Line items, invoices, payments.
Bookings move through statuses: lead, tentative, definite, lost. Groups can be created from PMS room-block data. Invoices start as drafts until finalized; void applies to sent or finalized invoices.
Pattern: combined get_* tools
Read tools accept an optional id:
Omit id — cursor-paginated list (page[size], page[after] from meta.after_cursor, include, filter[default_search], filter[updated_at][gt]).
With id — single JSON:API resource fetch.
Pattern: upsert_* tools
Omit id to create (POST). Pass id to patch. Supply attributes and relationships as JSON:API objects matching the upstream type (accounts, contacts, bookings, etc.).
Operational order
Run get_organizations when you need property ids or to refresh the cached property list after access changes.
Resolve account and contact before deep booking work — search contacts or accounts with filter[default_search] when you only have a name.
Pull booking with include for account, contact, group, stage when answering pipeline questions.
Use change booking status (POST change_status) and change booking dates (POST change_date with start_at/end_at UTC) for lifecycle moves — not generic booking upsert.
Multi-resource booking creation uses create full booking; catalog packages onto a deal use create booking package from package — not generic booking_packages upsert.
For invoice state changes, use finalize and void actions rather than guessing editable fields on draft vs sent invoices.
Gotchas
Cursor pagination uses page[after] / page[before], not page numbers.
Room block creation from PMS uses the dedicated create group from PMS action with booking_id and pms_record_id.
Space availability requires local_start_time, local_end_time, and attendees — it is not cursor-paginated.
Booking packages: list, get, and delete only; create through create booking package from package.
Contact email is unique per property. Omit the contact id to upsert by email: one existing match is updated, and no match creates the contact. If several contacts share the email, pass the contact id.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
Event Temple
Add to your AI client, then sign in once when you connect.
Event Temple is a hotel sales and events CRM. Manage accounts, contacts, bookings, groups, events, catering line items, invoices, and property inventory through the Event Temple JSON:API.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Event Temple Bp From Package — Event Temple booking package: POST create_from_package — materialize catalog package onto a booking with expected/guaranteed counts and date range.
Event Temple Change Booking Dates — Event Temple booking: POST change_date with start_at and end_at (UTC date-time). Optional all_day, shift_event_dates, shift_serving_times. Does not shift room blocks.
Event Temple Change Booking Status — Event Temple booking: POST change_status with status and optional status_at (ISO-8601). Updates tentative_at, definite_at, or lost_at per upstream rules.
Event Temple Create Full Booking — Event Temple booking: POST create_full — one booking with nested events, line items, optional booking_package block, and contacts per upstream create-full schema.
Event Temple Create Group From Pms — Event Temple group: POST create_from_pms — room blocks and rates from PMS (booking_id + pms_record_id).
Event Temple is a hotel sales and events CRM. Manage accounts, contacts, bookings, groups, events, catering line items, invoices, and property inventory through the Event Temple JSON:API. It provides 62 tools that AI agents can use through the Model Context Protocol (MCP).
How do I connect Event Temple to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/event-temple. Authentication is handled automatically.
Event Temple Get Accounts — Event Temple account: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Account Types — Event Temple account type: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Booking Packages — Event Temple booking package: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Bookings — Event Temple booking: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Booking Types — Event Temple booking type: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Contacts — Event Temple contact: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Custom Fields — Event Temple custom field: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Event Temple Get Deletion Logs — Event Temple deletion log: omit id to list with cursor pagination (page[size], page[after], include, filters); pass id to fetch one record.
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does Event Temple provide?
Event Temple provides 62 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
What authentication does Event Temple require?
Event Temple uses API Key. Event Temple requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in customer relation
Other MCP servers in this category from the directory index