Model Context Protocol / OAuth 2.1

One connection. Every assistant. Nothing it shouldn't see.

Connect Claude, ChatGPT, or any AI assistant to your events, attendees, and check-in counts. It sees only what your staff role sees.

Connect an assistantRead the tool reference
POST https://api.enclavehq.com/api/mcp copy
Assistants Enclave
Claude
Claude Code
ChatGPT
Cursor
OpenCode
pi
Enclave MCPOAuth 2.1 / PKCE
Eventsevents:read / events:write
Registrationsregistrations:read
Check-in countsregistrations:read
Ticket typesevents:read
ClaudeClaude CodeChatGPTCursorOpenCodepiVS Code and any MCP client
What you can ask

Plain language in. Real changes out.

Questions never change data. Changes need your approval and go in your audit log.

List my upcoming events.
events_listread
Which private events do we have next month?
events_listread
How many people are checked in at the Late Session right now?
checkin_statsread
Create an online event called Onboarding Q&A next Tuesday at 18:00 for one hour.
events_createwrite
Change the capacity of the API Integrations workshop to 80.
events_updatewrite
Who is on the waitlist for the Founders Dinner?
registrations_listread
See it work

Watch a question become an answer.

Enclave checks your permissions, then answers in the same conversation.

ClaudeChatGPTCursorClaude Code
Which private events do we have next month?
events_list{ timeFilter: "upcoming", visibility: "private" }
Three private events in October:
  • Founders Dinner · 3 Oct · 24 of 30 going
  • Late Session · 11 Oct · 88 going, 12 waitlisted
  • Board Planning · 29 Oct · online
scope events:read · role adminaudit · source: mcp
What it reaches

Four areas. Clear edges. Nothing leaks past them.

Access to events does not include attendees. Some fields are never shared.

Events events:*

  • List and search
  • Full detail
  • Create and update
  • Cancel, after you confirm
Never: hard delete.

Registrations registrations:read

  • Name, ticket type, status, dates
  • Email and phone only with the manage permission
Never: check-in QR signatures, answers to registration questions.

Check-in counts registrations:read

  • Going, checked in, pending, waitlisted
  • Live during the event
Never: names, marking attendance, adding walk-ins.

Ticket types events:read

  • Price and currency
  • Sales window
  • Capacity
Never: member-tier pricing, admin fees.

Full tool reference at /tools.

How it works

Three steps. No keys to paste.

You sign in and approve the assistant in the Enclave console. No keys to copy.

+STEP 1

Add the server. Paste the server URL into your assistant.

Add custom connector
Name Enclave
URL https://api.enclavehq.com/api/mcp
Connect
STEP 2

Sign in and pick the organization. Sign in to the Enclave console. Choose the organization the assistant can work in.

Claude wants accessevents:read
Riverside Members Club
Harbour Society
DenyAllow
STEP 3

Ask. Ask questions. Before the first change, Enclave asks for your approval again.

Enclaveconnected
events_listevents_getcheckin_statsticket_types_list
Approval on first changeevents:write
Under your permissions

The assistant can do exactly what you can. Not more.

If you cannot do something in the console, the assistant cannot do it for you.

SCOPE

What you allowed. events:read, events:write, registrations:read. A missing scope is refused before any tool runs.

TOKEN

Who is asking. Bound to one user, one organization, one client. Expired, revoked, or no longer staff: refused.

ROLE

Your staff permission. The same permission the console uses, custom roles included.

log
Every write is in the audit logMarked as MCP, with the assistant's name.
org
Per-organization opt-inOff by default. The Enclave team turns it on on request.
off
Disconnect any timeConsole, Settings, Connected Apps, Disconnect.
60
Rate limited per connectionSixty calls per minute for each connection.

Full technical detail at /security.

Connect

Pick your assistant.

Staff only. Your organization must have assistant access turned on.

ClaudeClaude CodeChatGPTCursorVS CodeOpenCodepiOther clients
  1. Open Settings, then Connectors, then Add custom connector.
  2. Name it Enclave. Paste the server URL.
  3. Click Connect. Sign in, select the organization, click Allow.
  4. The first change asks for one more approval.
Server URLcopy
https://api.enclavehq.com/api/mcp
FAQ

Short answers.

Does it cost more?+

No. It is a switch on your organization. Ask the Enclave team to turn it on.

Who can connect?+

Staff with an owner, admin, user or custom staff role. Members cannot connect.

Can it see member data?+

Only what your role already sees. Email and phone need the manage permission. QR signatures and registration answers are never shared.

Can it delete an event?+

It can cancel one, after you confirm. It cannot delete one.

How do I revoke access?+

Console, Settings, Connected Apps, Disconnect. Every token for that app stops at once.

Which assistants work?+

Claude, Claude Code, ChatGPT, Cursor, VS Code, OpenCode, pi, and any other assistant that supports MCP.

Bring your assistant to the club. Keep the keys.

Ask us to turn on assistant access for your organization, or see Enclave first.