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
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago