Presso Events - Guide

Add the connector

Cursor, Claude Code, Codex, Gemini.

Each CLI/editor client adds the Presso connector with one command or config block. Add it first with no token, then reconnect with the token Presso issues you once your organisation exists.

Cursor

Edit ~/.cursor/mcp.json (or a project's own .cursor/mcp.json):

{ "mcpServers": { "presso-events": { "url": "https://mcp.presso.events/mcp" } } }

Reconnecting with your token. Add a headers block:

{ "mcpServers": { "presso-events": { "url": "https://mcp.presso.events/mcp", "headers": { "Authorization": "Bearer pev_..." } } } }

Claude Code

claude mcp add --transport http presso-events https://mcp.presso.events/mcp

Reconnecting with your token. Re-run the same command with a --header flag:

claude mcp add --transport http presso-events https://mcp.presso.events/mcp --header "Authorization: Bearer pev_..."

Codex

codex mcp add presso-events https://mcp.presso.events/mcp

Reconnecting with your token. Codex supports the same --header flag at add time:

codex mcp add presso-events https://mcp.presso.events/mcp --header "Authorization: Bearer pev_..."

Gemini

gemini mcp add presso-events https://mcp.presso.events/mcp

Reconnecting with your token. Gemini's CLI also takes a --header flag (short form -H):

gemini mcp add presso-events https://mcp.presso.events/mcp --header "Authorization: Bearer pev_..."

← Back: Connect your AI