Provides a multi-tenant interface to the Eventbrite API, enabling interaction with Eventbrite's event management and ticketing platform services.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Eventbrite MCP Serverlist my upcoming events for this month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Eventbrite MCP Server
Multi-tenant Eventbrite MCP server with Firebase authentication, wrapping @prmichaelsen/eventbrite-mcp.
Overview
This server provides a multi-tenant Model Context Protocol (MCP) interface to the Eventbrite API. It uses:
Firebase Authentication for user identity verification
Platform API for secure credential management
@prmichaelsen/mcp-auth for authentication wrapping
@prmichaelsen/eventbrite-mcp as the base MCP server
Architecture
Prerequisites
Node.js 20+
Firebase project with authentication enabled
Platform API that implements the credentials endpoint
Eventbrite OAuth tokens stored in your platform
Installation
Configuration
Copy .env.example to .env and configure:
Environment Variables
Variable | Required | Description |
| Yes | Firebase project ID for JWT validation |
| Yes | Base URL of your platform API |
| Yes | Service token for platform API authentication |
| No | Server port (default: 8080) |
| No | Environment (development/production) |
| No | Logging level (default: info) |
Development
Docker
Build
Run
Deployment
Google Cloud Run
API Endpoints
Health Check
MCP Message Endpoint
Testing
Local Testing
Production Testing
Platform API Requirements
Your platform must implement the credentials endpoint:
Project Structure
Features
✅ Multi-tenant architecture
✅ Firebase authentication
✅ Platform-managed credentials (secure)
✅ Stateless server (no database)
✅ Token caching for performance
✅ Rate limiting
✅ Health checks
✅ Docker support
✅ Cloud Run ready
Security
Firebase JWT tokens are validated on every request
Eventbrite tokens are never exposed to clients
Service token authenticates server-to-platform communication
All credentials are managed by the platform API
Rate limiting prevents abuse
Caching
The server implements two levels of caching:
Auth Cache: Firebase JWT validation results (TTL: 60s)
Token Cache: Eventbrite access tokens (TTL: 5min)
Caching improves performance and reduces external API calls.
Troubleshooting
TypeScript Errors
TypeScript errors about missing modules are expected before running npm install. Install dependencies to resolve.
Authentication Failures
Verify
FIREBASE_PROJECT_IDmatches your Firebase projectEnsure Firebase JWT is valid and not expired
Check that the JWT is sent in the
Authorization: Bearer <token>header
Token Resolution Failures
Verify
PLATFORM_URLis correctEnsure
PLATFORM_SERVICE_TOKENis validCheck that user has Eventbrite credentials in the platform
Review platform API logs for errors
License
MIT
Related Projects
@prmichaelsen/eventbrite-mcp - Base Eventbrite MCP server
@prmichaelsen/mcp-auth - MCP authentication wrapper
Bootstrap Pattern - Pattern documentation
Support
For issues or questions:
Base MCP server: @prmichaelsen/eventbrite-mcp issues
This wrapper: Create an issue in this repository