Eventflare MCP

What is Eventflare MCP?

Eventflare MCP is a Model Context Protocol server that makes Eventflare’s production venue data—8,000+ corporate event venues across 40+ cities—queryable by AI assistants such as Claude, ChatGPT, Perplexity, and Cursor. It is designed to let LLMs cite Eventflare URLs in their answers and to enable end‑to‑end lead attribution.

How to use Eventflare MCP?

Install with npm install, copy .env.example to .env, fill in the required EVENTFLARE_API_TOKEN, run npm run build, then start with npm start (stdio) or TRANSPORT=http PORT=3001 npm start (HTTP). Connect to Claude Desktop via claude_desktop_config.json or to Claude Code with claude mcp add. Seven tools are exposed: search_venues, get_venue_details, get_city_info, list_cities, get_pricing_guide, find_expert_advice, and request_quote.

Key features of Eventflare MCP?

• 8,000+ corporate venues across 40+ cities
• Seven read‑only tools optimized for LLM responses
• JWT authentication and PII redaction on all API calls
• UTM‑tagged outbound URLs for measurable lead attribution
• Per‑IP rate limiting (60 req/min on HTTP transport)
• Local dashboard and optional analytics sink (OpenPanel/webhook)

Use cases of Eventflare MCP?

• An event planner asks an AI assistant to find venues in London for a 200‑person conference, then requests a quote.
• A data team tracks how many leads from AI‑assisted venue searches convert via UTM tags in GA4 or Mixpanel.
• An analyst surfaces Eventflare’s editorial articles on city‑specific expert advice through the find_expert_advice tool.
• A developer integrates HTTP‑mode Eventflare MCP into a custom agent to list cities and their venue counts.

FAQ from Eventflare MCP?

What authentication does Eventflare MCP use?

JWT authentication is required; the server sends an Authorization: Bearer header with the EVENTFLARE_API_TOKEN on every outbound request. The token uses a read‑only role.

Is Eventflare MCP read‑only?

Yes. All tools perform only GET requests against the Eventflare API. The server is confirmed against 123 endpoints, all GET. No POST/PUT/DELETE operations exist.

How are PII and user privacy handled?

PII fields (jobPhone, venueEmail, commission, spaceNotes) are never fetched via API field allowlists. A redaction allowlist drops any data that slips through. No user identity or message content is logged; analytics only record tool, city, capacity, event type, category, result count, session id, client class, and budget band.

What transport options are available?

Two modes: stdio (default, used by Claude Desktop, Claude Code, Cursor) and HTTP (for remote MCP, set TRANSPORT=http and optionally PORT).

Where does the data come from and how is attribution tracked?

Data comes from Eventflare’s production content API. Every outbound URL is tagged with utm_source=mcp, utm_medium=ai, utm_campaign={tool_name}, utm_content={client_class}, and a mcp_session parameter, allowing lead attribution in GA4, Mixpanel, or