About Nevent
Nevent is an MCP server for live-event promoters who manage marketing through Nevent's CRM. It exposes tools for analytics, campaigns, audience segments, paid media and related workflows through hosted OAuth 2.1 or local stdio.
Key features
- 01Analytics and registration queries
- 02Campaign and template management
- 03Audience segmentation
- 04Paid media and short URL tools
- 05Hosted OAuth 2.1 or local stdio
Use cases
- 01Review registration and campaign performance
- 02Create attendee segments from purchase and engagement data
- 03Schedule event marketing campaigns
MCP support
Exposes 63 tools in 10 groups to MCP clients, including analytics, segmentation, campaigns, templates, deliverability, paid media, short URLs and media library. Connections use hosted OAuth 2.1 or local stdio.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.nevent.ai/claude mcp add --transport http nevent-dev-mcp-nevent https://mcp.nevent.ai/{"mcpServers":{"nevent-dev-mcp-nevent":{"type":"http","url":"https://mcp.nevent.ai/"}}}Open in Cursor{"servers":{"nevent-dev-mcp-nevent":{"type":"http","url":"https://mcp.nevent.ai/"}}}Open in VS Code{"mcpServers":{"nevent-dev-mcp-nevent":{"type":"http","url":"https://mcp.nevent.ai/"}}}{"mcpServers":{"nevent-dev-mcp-nevent":{"serverUrl":"https://mcp.nevent.ai/"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
55| Parameter | Type | Required | Description |
|---|---|---|---|
| collection | string | Yes | Collection name, e.g. "purchases", "tickets", "campaigns" |
| dimensions | array | No | Fields to group by (SELECT dimensions). Omit for aggregate-only queries. |
| metrics | array | No | Aggregated metrics to compute (SUM, COUNT, etc.) |
| timeRange | object | No | Time range filter with optional granularity for trend analysis |
| timeRange.start | string | Yes | Start date in ISO 8601 format, e.g. "2024-01-01" |
| timeRange.end | string | Yes | End date in ISO 8601 format, e.g. "2024-12-31" |
| timeRange.granularity | string | No | Time bucket granularity (deprecated: use top-level timeGranularity) |
| filters | array | No | WHERE clause filters to apply before aggregation |
| having | array | No | HAVING clause filters to apply after aggregation |
| sort | any | No | Sort the result rows. Accepts a single { field, order } object or an array for multi-field sorting. |
| limit | number | No | Maximum rows to return (max 1000, default 100) |
| compareDimensions | object | No | Comparative dimension analysis configuration |
| compareDimensions.active | boolean | Yes | Enable comparative analysis |
| compareDimensions.dimensions | array | Yes | Dimension values to compare against each other |
| distinct | boolean | No | Add SELECT DISTINCT to deduplicate result rows (v3.19.0+) |
| dryRun | boolean | No | Dry-run mode: estimate query cost without executing (v3.19.0+). Response includes estimatedBytes in metadata. |
| timeGranularity | string | No | Time granularity for bucketing (v3.19.0+). Known values: day | week | month | quarter | year | hour | minute | fiscalQuarter | fiscalYear |
| groupBy | array | No | Calendar-based group-by fields (v3.19.0+). Known values: dayOfWeek | weekOfYear | hourOfDay | minuteOfHour | month | quarter | year |
| comparePeriods | object | No | Period-over-period comparison (YoY, MoM, etc.) — v3.19.0+ |
| comparePeriods.active | boolean | Yes | Enable period-over-period comparison |
| comparePeriods.current | object | Yes | The reference (current) time period |
| comparePeriods.current.start | string | Yes | ISO 8601 start date, e.g. "2024-01-01" |
| comparePeriods.current.end | string | Yes | ISO 8601 end date, e.g. "2024-12-31" |
| comparePeriods.previous | object | Yes | The baseline (previous) time period to compare against |
| comparePeriods.previous.start | any | Yes | |
| comparePeriods.previous.end | any | Yes | |
| ctes | array | No | CTE (Common Table Expression) sub-queries — v3.19.0+ |
| sourceTable | string | No | CTE name to use as source instead of a raw collection — v3.19.0+ |
Details
From the project READMENevent MCP
Talk to your live-events CRM (campaigns, analytics, paid ads, segments, short URLs) in Claude and ChatGPT.
Official MCP server for Nevent — the marketing platform for live event promoters. 63 tools across 10 groups (analytics, segmentation, campaigns, templates, deliverability, paid media, short URLs, media library, multi-tenant, and help/discovery) over OAuth 2.1 (hosted) or stdio (local).
📚 Full documentation: https://help.nevent.ai/en/nevent-ai/
Install
Hosted (recommended — no install needed)
Add https://mcp.nevent.ai/ as a remote MCP server in your client. Works with Claude.ai, ChatGPT, Cursor, Cline, Continue and any compatible MCP client.
→ Step-by-step with screenshots: Connect with Claude · Connect with ChatGPT
Local (stdio via npm)
npx mcp-nevent
Required env: NEVENT_JWT_TOKEN. Optional: NEVENT_OPERATION_MODE (READ_ONLY | STANDARD | FULL).
→ Full local setup: Local installation
Quick add
Claude.ai · ChatGPT (hosted, no setup)
Settings → Integrations / Connectors → Add custom MCP → URL https://mcp.nevent.ai/. Authorize with your Nevent admin account.
Claude Code
# Hosted (OAuth)
claude mcp add --transport http nevent https://mcp.nevent.ai/
# Or local (stdio)
claude mcp add nevent -- node /path/to/mcp-nevent/dist/index.js
export NEVENT_JWT_TOKEN=your_token
→ Full guide: Claude Code
Claude Desktop
Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):
{
"mcpServers": {
"nevent": {
"command": "node",
"args": ["/path/to/mcp-nevent/dist/index.js"],
"env": {
"NEVENT_JWT_TOKEN": "your_nevent_jwt_token"
}
}
}
}
→ Full guide: Claude Desktop
Cursor · Cline · Continue · VS Code
→ Per-client setup: Cursor, Cline, Continue, VS Code
What you can ask
"Show me registrations for EventX broken down by ticket type"
"Which campaigns sent last month had an open rate above 30%?"
"Create a segment of attendees who bought a VIP ticket in 2025
but haven't opened any email in the last 90 days"
"Schedule the 'Summer Gala' campaign for next Monday at 10:00 CET"
"Compare ROAS across our Meta ad campaigns for March"
"Create per-user tracking links for the Summer Gala campaign
and show me which users clicked"
→ More patterns: Ready-to-use prompts · Use cases
Documentation
| Topic | Link |
|---|---|
| What Nevent AI is and how it works | https://help.nevent.ai/en/nevent-ai/ |
| Capabilities by area (analytics, campaigns, audience, paid media…) | https://help.nevent.ai/en/nevent-ai/what-you-can-do/ |
| End-to-end use cases | https://help.nevent.ai/en/nevent-ai/use-cases/ |
| Permissions and security | https://help.nevent.ai/en/nevent-ai/permissions-and-security/ |
| FAQ | https://help.nevent.ai/en/nevent-ai/faq/ |
For developers
| Topic | Link |
|---|---|
| Overview, transports and architecture | https://help.nevent.ai/en/nevent-ai/developers/ |
| Local installation and env vars | https://help.nevent.ai/en/nevent-ai/developers/local-installation/ |
| Multi-tenant model | https://help.nevent.ai/en/nevent-ai/developers/multi-tenant/ |
| Reference of all 63 tools | https://help.nevent.ai/en/nevent-ai/developers/tools/ |
| Troubleshooting and error codes | https://help.nevent.ai/en/nevent-ai/developers/troubleshooting/ |
How it works
LLM (Claude / ChatGPT / Cursor / …)
|
| MCP (Streamable HTTP or stdio)
v
┌─────────────────┐
│ Nevent MCP │ mcp.nevent.ai (hosted) or local
└─────────────────┘
|
| REST + JWT
v
Nevent APIs (analytics, campaigns, segments, paid media, short URLs)
Hosted mode uses OAuth 2.1: the MCP server issues short-lived JWT tokens after validating your Nevent credentials. Each session is isolated — no shared service accounts.
Restricting OAuth clients (self-hosted HTTP)
Optional environment variables for the HTTP server:
| Variable | Default | Purpose |
|---|---|---|
MCP_READONLY_REDIRECT_PREFIXES | unset | Comma-separated redirect_uri prefixes. A client that registered a matching redirect URI only gets read-only tools. Every prefix must end with /, for example https://support.nevent.ai/helpbot/. |
MCP_READONLY_CLIENT_IDS | unset | Comma-separated client_id values restricted the same way. |
MCP_REFRESH_REVALIDATE | restricted | restricted, all or off: which clients are revalidated against nev-api (GET /auth/me) when they refresh a token. |
MCP_REFRESH_MAX_LIFETIME_DAYS | 90 | Maximum total lifetime of a refresh-token chain, counted from the original login. |
See CHANGELOG.md for the exact behaviour.
Privacy
The Nevent MCP server processes tenant data on Nevent's own infrastructure (AWS, eu-west-1). Data does not leave Nevent's infrastructure and is not used for model training.
For details on data collection, retention, third-party sharing, and contact information, see the full privacy policy: https://nevent.ai/en/privacy/
Security disclosure: see SECURITY.md.
Contributing
See CONTRIBUTING.md, CODE_OF_CONDUCT.md and SECURITY.md.
License
MIT © Nevent
Support
- Help Center: https://help.nevent.ai
- Issues: https://github.com/nevent-dev/mcp-nevent/issues
- Email: [email protected]
- Product: https://nevent.ai/en
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.