Connect an AI assistant (organizers)

Use Claude, ChatGPT, Microsoft Copilot Studio, Cursor or VS Code to work on your Jade events: look up registrations, fix a participant record, check housing pickup, run a report or draft a campaign email — in plain language, from the assistant you already use.

Before you start

1. You need a Jade organizer login with access to at least one client.
2. AI assistant access is on by default for every client. A client administrator can turn it off under Developers → AI assistants in that client (see Turn it off for a client below). While it is off your assistant can still sign in, but it will not see that client’s events.
3. Your assistant must support remote MCP servers (sometimes called custom connectors) with OAuth sign-in. All the assistants below do; on business plans an administrator may need to allow custom connectors first.

The server address

Every assistant needs the same address. There is no API key to copy — you sign in instead.

/api/mcp/organizer

Without anything added, the assistant gets every toolset listed below — up to 234 tools. Some assistants load only a limited number of tools from one server, or choose less reliably from a long list; for those, add ?toolsets= with a comma-separated list of the toolsets you need, for example /api/mcp/organizer?toolsets=registration,housing.

Set up your assistant

Assistant menus change often. If a label below has moved, look for “custom connector”, “MCP server” or “Model Context Protocol”.

Claude

1. In Claude (web or desktop), open Settings → Connectors and choose Add custom connector. On a Team or Enterprise plan an owner may add it for the organization first.
2. Name it “Jade”, paste the server address, and save.
3. Choose Connect, sign in to Jade, and allow the connection (see Signing in). Then enable the connector in a chat from the tools menu.

Claude Code: run the command below, then type /mcp in a session and choose to authenticate.

claude mcp add --transport http jade /api/mcp/organizer

ChatGPT

1. In ChatGPT, open Settings → Apps & Connectors → Advanced settings and turn on Developer mode. On Business, Enterprise and Edu workspaces an administrator may need to allow it.
2. Back in Apps & Connectors, choose Create. Name it “Jade”, paste the server address, and pick OAuth as the authentication.
3. Sign in to Jade and allow the connection. In a new chat, add the Jade connector from the tools menu (the + button).

Microsoft Copilot Studio

1. Open your agent and go to Tools → Add a tool → New tool → Model Context Protocol.
2. Enter “Jade” as the name, a short description, and the server address. For authentication choose OAuth 2.0 with dynamic discovery — Jade registers the connection automatically, so there is no client ID or secret to enter.
3. Create a connection, sign in to Jade, allow it, and add the tool to the agent. Each person who uses the agent signs in as themselves.

Cursor

Add Jade to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor shows a sign-in button next to the server the first time.

{
  "mcpServers": {
    "jade": {
      "url": "/api/mcp/organizer"
    }
  }
}

VS Code (GitHub Copilot agent mode)

Add Jade to .vscode/mcp.json in your workspace (or run MCP: Add Server from the command palette), start the server, and sign in when prompted.

{
  "servers": {
    "jade": {
      "type": "http",
      "url": "/api/mcp/organizer"
    }
  }
}

Signing in

1. When you connect, the assistant opens a Jade sign-in page in your browser. Sign in exactly as you do for Jade.
2. Jade then asks Connect [app] to Jade as you? and shows the website it will return you to. Check both: only allow an app you just set up yourself. Choose Authorize, or Deny if anything looks wrong.
3. You are returned to the assistant, which now lists the Jade tools. It stays connected: its access renews itself while you keep using it, and stops if it goes unused for 30 days or if your Jade access changes.

For engineers: this is standard OAuth 2.1 — authorization code with PKCE (S256), dynamic client registration, RFC 8707 resource indicators, and discovery through RFC 9728 protected-resource metadata advertised on the 401 response. Access tokens last one hour; refresh tokens rotate and last 30 days. The endpoint is also listed, with its toolsets and every tool it serves, in Jade’s MCP discovery document (the last address below).

GET /.well-known/oauth-protected-resource/api/mcp/organizer
GET /.well-known/oauth-authorization-server/api/oauth
GET /api/.well-known/mcp.json

Using it

Ask in plain language — “how many people registered for the Lisbon summit this week?”, “move the Nguyen party to the Hilton block”. The assistant starts with list_my_events to find the event, then passes its eventCode (and clientCode if two of your clients use the same code) to each event tool, and a clientCode to the client tools, such as creating or cloning an event. Most assistants ask you before running a tool that changes data; Jade marks each tool as read-only, a change, or an action that cannot be undone, so they can.

Toolsets and tools

Jade serves 234 organizer tools in 13 toolsets. list_my_events is always included, whichever toolsets you pick. You only see the tools your Jade role allows — someone without housing access will not get the housing tools, for example.

What is not available, and why

Almost every organizer tool is available. The few left out only work inside Jade itself, would change what every other organizer’s built-in assistant does, would set Jade’s built-in assistant working on its own outside this connection, are internal steps of a background job, or need wider access than a connection carries:

• On-screen actions: moving you between Jade screens, on-screen cards, the question cards and step-by-step helpers in Jade’s chat, and filling in the Flow Designer on screen. Outside Jade there is no screen for them to act on.
• Writing the built-in assistant’s shared memory and custom instructions. They belong to the whole event and every organizer’s built-in assistant follows them, so one person’s outside assistant does not rewrite them. Reading them is available.
• Creating, editing, running now, or pausing and resuming scheduled jobs. A scheduled job runs on its own, as the person who set it up — for a prompt, as Jade’s built-in assistant with all of its tools — separately from this connection, so a client’s AI assistant access setting and this connection’s other limits do not apply to what it does. Listing scheduled jobs and deleting one is available.
• Reports written from a prompt: creating one (create_report), or running one that was. Jade’s built-in assistant writes them, separately from this connection and with all of its tools, so a client’s AI assistant access setting would not apply to it. Designed reports and dashboards (design_report) and Jade’s standard reports are available, and run_report runs them.
• The privacy look-ups — the retention policy and its runs, the personal-data map, and what Jade holds about one person. They only run on Jade’s own screens.
• The internal steps of background runs — the raw row feeds and result writers behind reports and analyses (use query_data or export_event instead) — and uploading a chat attachment, which an outside assistant does not have.
• A few account-wide administration tools — importing clients, granting license seats and checking on an import job — which need wider access than a connection to one client carries.

Actions that cannot be undone

Your assistant can do what you can, including things that cannot be taken back:

• Money: recording payments, filling the hotel waitlist (it charges the saved card), promoting waitlisted registrations, importing a past event with its payments, and executing sourcing awards.
• Sends: sending or scheduling campaigns, upsells and survey invitations; group, company and speaker invitations; booth assignment emails; and broadcast emails to one or several events.
• Contracts and suppliers: sending a contract for e-signature, voiding a signature envelope, and distributing an RFP.
• Deletes and resets: deleting campaigns, upsells, groups, directory connections, scheduled jobs and test imports; removing hotel waitlist entries; archiving an event; resetting an event to an earlier version; copying configuration over an event; and writing event configuration directly.
• Personal data leaving Jade: exporting a whole event (with personal data if asked), and running or saving a report that emails its results — personal data included — to its recipients, now or on a schedule.

Each runs with your own Jade permissions and nothing more, and Jade marks each one as destructive so your assistant asks you before running it. Read what it is about to do before you approve, and keep approval switched on for these if your assistant lets you skip it. Where there is a preview — a campaign preview, a dry run of a broadcast or an import, the differences between two versions — ask for it first.

Turn it off for a client

1. In Jade, open the client and go to Developers → AI assistants.
2. Turn off Allow AI assistants for this client. Only a client administrator can change it; everyone else sees whether it is on.

It takes effect immediately, in both directions: turning it off stops every connected assistant on its next request, for every organizer of that client. It does not change anyone’s permissions — an assistant still only reaches what its person could.

Disconnecting an app

Open Developers → AI assistants in any of your clients. Your connected apps lists every app you have allowed, when you connected it and when it was last used. Choose Disconnect and it loses access immediately. Removing the connector inside the assistant alone does not end its Jade access — disconnect it in Jade too.

Access also ends on its own when your Jade account is deactivated or loses all client access, or when the app goes unused for 30 days.

Rate limits

Each connected app may make 120 requests per minute. Beyond that Jade answers 429 Too Many Requests with a Retry-After header; every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Normal use never gets close — the limit exists to stop a runaway loop.

Troubleshooting

“AI assistant access is turned off for client …”

A client administrator has turned AI assistant access off for that client. If you need it, ask one of them to turn it back on under Developers → AI assistants.

An event is missing from list_my_events

Either a client administrator has turned AI assistant access off for its client, the client is no longer active, or your Jade login does not have access to that event. Check that you can open it in Jade.

“Forbidden — … requires the … permission”

Your Jade role does not allow that action for that event. The assistant cannot do more than you can; ask your administrator if you need the access.

The sign-in page says your account has no organizer access

Your Jade login is not a member of any client. Ask a Jade administrator to add you, then connect again.

“Ambiguous event code — pass clientCode”

Two of your clients use the same event code. Tell the assistant which client you mean; it will pass clientCode from list_my_events.

The assistant says it is not authorized, or asks you to sign in again

Its access ended — it was disconnected, unused for 30 days, or your Jade access changed. Reconnect it from the assistant’s connector settings.

“Unknown toolset(s)” when connecting

Check the ?toolsets= part of the address against the toolset names in the table above (events, registration, housing, reports, email, exhibitors, sessions, sourcing, onsite, design, marketing, automation, clients).

The assistant warns about too many tools, or cannot find one you know exists

Some assistants load only part of a long tool list. Add ?toolsets= to the address with just the toolsets you need (see The server address above), then reconnect.

“Rate limit exceeded” / 429

The app made more than 120 requests in a minute. Wait for the Retry-After time; if it keeps happening, the assistant is probably looping — stop it and rephrase the request.

Related

• MCP: both endpoints side by side
• Connect an AI assistant (participants)