Eventbrite MCP Server

Created By
joshuachestanga year ago
Model Context Protocol server for Eventbrite API integration. Create and manage events using natural language through AI agents like Claude Desktop and Cursor IDE.
Overview

What is Eventbrite MCP Server?

Eventbrite MCP Server is a Model Context Protocol server that allows users to interact with the Eventbrite API using natural language, enabling the creation and management of events through AI agents.

How to use Eventbrite MCP Server?

To use the server, set up your Eventbrite API credentials, configure the environment variables, and run the server in development or production mode. You can then connect it to an MCP client for natural language commands.

Key features of Eventbrite MCP Server?

  • Create, list, update, publish, and cancel events using natural language.
  • Manage venues and browse Eventbrite categories.
  • Comprehensive error handling for various scenarios.

Use cases of Eventbrite MCP Server?

  1. Creating events through conversational commands.
  2. Managing event details and statuses easily.
  3. Integrating with AI tools for enhanced event management.

FAQ from Eventbrite MCP Server?

  • Can I create events in any category?

Yes, you can browse and use various Eventbrite categories.

  • Is there a cost to use the Eventbrite MCP Server?

The server is free to use, but you need an Eventbrite account for API access.

  • What programming language is used?

The server is built using TypeScript and Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
joshuachestang
Star
1
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago