The most useful AI surface for an operations lead is often not a chat box inside the product — it is the assistant they already work in, given real hands. EventfullyManaged publishes a Model Context Protocol server for exactly that: a small shell over the platform's shared MCP library that mounts the event domain alongside the platform modules for auth, files, conversations, notifications, scheduling, tags, RBAC and the rest.
The event module exposes sixty-seven tools spanning the whole product: events, sessions and speakers; venues and floor plans; ticket types, promo codes, registrations and attendees; check-in stations and check-in records; sponsors, exhibitors and leads; networking profiles, matches and meetings; plus a dashboard summary. Four read-only resources let a client pull the schema, the dashboard, the event list and the venue list without a tool call, and two guided prompts encode the workflows an organizer actually runs — one that walks standing up a new event end to end, and one that runs a live event day from KPIs through check-in, lead capture and networking.
Authorization is not delegated to the agent. The server authenticates through the platform's identity provider with a dedicated client identity and talks to the same public API gateways as the web console, so every tool call is subject to the same field-level access rules, the same workspace scoping and the same audit trail as a human clicking the equivalent button. An agent cannot reach data its operator cannot reach, and it cannot bypass the gateway to talk to the service directly.
The honest gap is confirmation. Twelve of those tools delete things — events, venues, sponsors, ticket types, promo codes, check-in stations and records, exhibitors, leads, networking profiles, matches, meetings — and today they carry no destructive-action annotation, which means a client is not obliged to ask before calling them. Access control stops an agent doing what its operator may not do; it does not stop an agent doing something its operator would not have chosen. That gate is the next piece of work here, and until it lands this surface is best pointed at read and create paths.
Two event-specific capabilities are also still missing from the tool set: generating networking matches and fetching an attendee's suggested connections are available in the product API but not yet exposed as MCP tools, so an agent can read and edit matches but cannot yet ask the engine to produce them.
Illustrative scenario. The MCP server, its tools, resources and prompts are implemented; the destructive-action confirmation gate is not.
Ready to make this your story?
