AI Assistants (MCP)
Run your Diem workspace from Claude, ChatGPT, or any assistant that speaks the Model Context Protocol — tickets, sales, audience, and payouts by conversation.
On this page
Your workspace, by conversation
The Diem MCP server lets an AI assistant operate your Diem workspace directly: check ticket sales while you're on the floor, pull last weekend's revenue, create a listing, look up a purchase by confirmation code, or export your audience — by asking in plain language. It works with any client that supports the Model Context Protocol, including ChatGPT, Claude (web, desktop, and Claude Code), and Cursor.
Connect your assistant
Pick the assistant you use and follow only its steps. Every option talks to the same public endpoint, https://api.startdiem.com/mcp, with no API key, OAuth client, or bearer token; Diem signs you in from the chat afterward.
Anthropic setup · Claude web & desktop
Connect Diem to Claude
In Claude, Diem is a custom connector: a remote MCP server you add once in settings, switch on inside a chat, and then sign in to with your Diem email. The steps are the same at claude.ai and in the Claude desktop app, and the connector follows your Claude account across both.
Setup verified September 14, 2026 against the official Claude custom-connector guide.
Open Connectors
In Claude, click Customize in the left sidebar, open the Connectors tab, then click the plus button labelled Add custom connector.
Enter the Diem connector details
Use the exact values below: name it Diem, paste the hosted endpoint into Remote MCP server URL, leave Advanced settings untouched, and click Add.
Turn Diem on in a chat
Start a new chat, click the + button in the message box, choose Connectors, and switch Diem on. The Diem tools are now available in that conversation.
Sign in with your Diem email
Say “Log me into Diem, my email is …”, click the single-use link Diem emails you, then tell Claude you clicked it. Claude confirms the workspace you are signed into.
| Field | Enter or select |
|---|---|
| Name | Diem |
| Remote MCP server URL | https://api.startdiem.com/mcp |
| Advanced settings | Leave collapsed. The OAuth Client ID and OAuth Client Secret fields stay blank. |
| Add | Saves the connector. No sign-in prompt appears yet; Diem signs you in from the chat. |
Claude Code
Claude Code connects from the terminal with one command. Use --scope userso Diem is available in every project, then start a new session and ask it to log you in. Run /mcp inside Claude Code to confirm the connection.
claude mcp add --transport http diem --scope user https://api.startdiem.com/mcpOpenAI setup
Connect Diem to ChatGPT
OpenAI currently presents custom MCP servers as developer-mode pluginsor MCP connections. Some accounts still show the earlier Apps and custom app labels while the interface rolls out.
Setup verified September 14, 2026 against the official OpenAI setup guide.
Turn on Developer mode
In ChatGPT on the web, open Settings → Security and login, then turn on Developer mode.
Add a new MCP connection
Open ChatGPT Plugins, choose the plus button, then select the option to add an MCP server or create a custom app.
Enter the Diem connection details
Use the exact values below. Diem uses Streamable HTTP and does not need a transport-level API key or OAuth connection.
Create and enable Diem
Create the connection, review the tools ChatGPT discovers, start a new conversation, and select Diem from the tools or plugins menu.
| Field | Enter or select |
|---|---|
| Name | Diem |
| Description | Run your Diem workspace from ChatGPT |
| Connection | Public endpoint (Streamable HTTP) |
| MCP server URL | https://api.startdiem.com/mcp |
| Authentication | No authentication or None. If this field is not shown, continue without adding credentials. |
Codex CLI, IDE extension, and desktop app
Codex reads MCP servers from ~/.codex/config.toml, and the ChatGPT desktop app, Codex CLI, and IDE extension share that file. Add Diem once with the command below or by pasting the config, then restart Codex and run codex mcp list to confirm. Do not set bearer_token_env_var or custom headers.
codex mcp add diem --url https://api.startdiem.com/mcp[mcp_servers.diem]
url = "https://api.startdiem.com/mcp"Any MCP client
Connect Diem to Cursor or another MCP client
Every client uses the same public Streamable HTTP endpoint. Add it wherever your client configures remote MCP servers, with no OAuth client, bearer token, API key, or custom header, then say “Log me into Diem” and give it your email.
https://api.startdiem.com/mcp| Client | How to connect |
|---|---|
| Cursor | Add the URL-only entry below to ~/.cursor/mcp.json for all projects or .cursor/mcp.json for one project. Restart Cursor, then enable Diem under Customize → MCPs. |
| Any other MCP client | Look for “remote MCP server”, “MCP connection”, or “custom connector” in the client's settings and paste the endpoint above. Choose the Streamable HTTP transport if asked, and leave every authentication field empty. |
{
"mcpServers": {
"diem": {
"url": "https://api.startdiem.com/mcp"
}
}
}Sign in with a Diem magic link
After the Diem tools are enabled, authentication happens inside the conversation. The assistant never sees a password or the magic-link token, and the MCP connection only receives a Diem session after you approve the email link.
Log me into Diem with the email YOUR@EMAIL.COM.
1. Call the Diem "login" tool with that email and keep the returned session_id.
2. Tell me when Diem has sent the single-use magic link. I will click it in my email — I will not paste the link here.
3. When I say I clicked it, call "check_login_status" with the same session_id. If it is still pending, retry with that same ID.
4. Confirm the Diem workspace that is now active.Ask your assistant to log you in
Say “Log me into Diem. My email is me@example.com.” ChatGPT or Claude calls
login(email), and Diem returns asession_id.Click the newest Diem email
Open the single-use magic link in the email from Diem. Keep the link private; you never need to copy it into the conversation.
Return to the same conversation
Say “I clicked it. Check my login status.” The assistant calls
check_login_status(session_id)with the same ID. If the result is still pending, it can retry that call.Confirm the active workspace
Diem binds the MCP session to your account, loads your available workspaces, selects the first one, and returns the active workspace to the assistant.
| Say | What happens |
|---|---|
| “Log me into Diem. My email is …” | login sends a single-use link and returns the pending session ID. |
| “I clicked it. Check my login status.” | check_login_status confirms the link and reports the active workspace. If it is still pending, retry with the same session ID. |
| “Switch account” | Pick a different workspace if you manage more than one. |
| “Log out of Diem” | Revokes the session immediately. |
Available tools
| Category | What the assistant can do |
|---|---|
| Tickets & purchases | List tickets, per-event sales stats, refunds, purchase lookups by confirmation code. |
| Listings | Create and manage links, media folders, and donation listings. |
| Payments | Stripe balance, transfers, and payout dashboard access for the connected account. |
| Metrics & audience | Dashboard analytics, RSVPs, revenue, audience segments, growth, exports. |
| Automations & Instagram | Keywords with account targeting, Flow Builder automations (create, edit, publish), DM triggers, Instagram media. |
| Inbox & messaging | Read DM conversations, send replies and listings as the workspace account, contact lookup, notification opt-ins. |
| Team & accounts | Workspaces, members, invites, account switching. |
| Display rules | Draft, preview, and publish how tickets and listings display across every surface. See Display Rules. |
| Link Page | Read and edit the diem.me page end to end: display name, bio, images, colors, fonts, button style, socials, sections and links, username, and publishing. |
Security model
The assistant acts as the signed-in user with exactly that user's permissions — every call goes through the same authorization checks as the Diem dashboard. Sign-in links are single-use, sessions expire on their own, and telling the assistant to log out revokes the session immediately.