Event MCP Server

Event MCP server exists for a simple reason — assistants are far more useful when they can act on Event directly instead of describing what you should do. AI-powered event planning ai MCP server for agents. Supports calculate venue capacity, plan ...

What you get

This MCP server is built with EU AI Act compliance built-in:

Setting it up

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Event is connected, these are the calls the assistant has available:

• Well — documented API
• Production-ready — Active maintenance
• Pro — ** $99/mo — Full MCP suite + EU AI Act tracking
• Enterprise — ** $499/mo — Custom dev + SLA + Dedicated support
• Domain — Purpose
• Tier — Price

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the event mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Event's toolset — Well, Production-ready, Pro and 3 more — is a fair guide to whether it matches your workflow. It is maintained by CSOAI-ORG; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.