Skip to content
  • There are no suggestions because the search field is empty.

Connecting AI agent to Gleanin with MCP

In this article, you’ll learn how to connect an AI app such as Claude or ChatGPT to your Gleanin account with MCP, including approving the connection, choosing which accounts it reads, removing its access, and creating an MCP key for scripts.

Once connected, you can ask the AI app about your events’ results in plain language instead of building a report by hand.

How MCP works
The MCP page
Connecting an AI app
Approving the connection in Gleanin
Choosing which accounts a connector reads
Removing a connector’s access
Creating an MCP key
Revoking an MCP key

How MCP works

The Model Context Protocol (MCP) is an open standard that AI apps use to read data from other applications. Gleanin runs an MCP server, so when you add it to your AI app, the app can answer questions about your events’ results, for example which speakers drove the most registrations.

  • Read-only - nothing can be changed, sent or deleted through MCP.
  • Your role, your accounts - the AI app reads as you, and only the accounts you approve where you are a Manager or Admin.
  • Checked on every request - if you become a Viewer, are removed from the account, or MCP is taken off the plan, the app stops reading that account on its next request.
  • One connector, several accounts - you choose the accounts when you approve it, and you can change them later.
  • Per person - connectors and MCP keys belong to the person who set them up, so each person on the account connects their own.

The AI app can read:

  • Events, their asset hubs and attendee campaigns
  • Shares, web visits and conversions by channel and day
  • Which assets and advocates perform best
  • Who was invited and who hasn’t shared yet
  • One edition compared with another

This includes your speakers’ and exhibitors’ names, email addresses and personal hub links. No attendee is listed by name.

MCP is included in Gleanin Pro. If you are on Gleanin Starter, it comes with the Connect add-on.

Note: For events from Gleanin Classic, click counts by day are approximate, and there is no breakdown by asset.

The MCP page

  1. Click your account name at the top of the left-hand side menu
  2. Click MCP server

On the page, you will see:

  • Custom connectors: how to add Gleanin to your AI app, with the Server URL. Once something is connected, this becomes Connect another AI app; click Show how to connect to open it
  • Connectors reading {account}: every AI app that reads this account, with when it was approved and last used
  • MCP key: your MCP key for this account, or the Create MCP key button
  • This account: your role, and how many connectors and keys the account has
  • What AI can read: what a connected app can see

Each account has its own connectors and key. To manage another account’s, switch account from the account menu.

Connecting an AI app

You start in the AI app, not in Gleanin. There is nothing to copy back into Gleanin.

To connect an AI app, follow the steps below:

  1. Click your account name at the top of the left-hand side menu
  2. Click MCP server
  3. Under Server URL, click the copy button
  4. Click the tab for your AI app and follow its instructions:
    1. Claude: open Settings → Connectors → Add custom connector, name it Gleanin and paste the server URL. Leave the client ID and secret empty
    2. ChatGPT: on the web, turn on Developer mode under Settings → Security and login. Then open Plugins, select +, name it Gleanin, paste the server URL and choose OAuth. On Business, Enterprise and Edu workspaces, an admin may need to allow Developer mode first
    3. Claude Code: run the command shown on the tab in your terminal
    4. Codex: add a remote (HTTP) MCP server named gleanin with the server URL
    5. Other apps: add the server URL to any AI app that supports remote MCP connectors with sign-in (OAuth)
  5. Your AI app opens the Gleanin consent screen. Approve the connection as described below

Once approved, the app appears under Connectors reading {account}.

Note: Each time an app reconnects, it may register itself again, so the same app can appear twice. The older one is labelled Older connection from the same app, and you can remove it.

Approving the connection in Gleanin

  1. If you aren’t signed in, sign in. You will see Continue to authorise {client} above the form
  2. If you belong to more than one account, under Which account?, click the account the app should read, then click Continue
  3. On Allow {client} to access Gleanin?, check what the app Will be able to read
  4. Click Allow access

Gleanin sends you back to your AI app, and you can start asking about your events.

Accounts you can’t connect are greyed out in the list, with the reason: Viewer — not available or MCP not enabled. To pick again, click Choose a different account. To sign in as someone else, click Switch account at the bottom.

If you click Cancel, nothing is shared with the app.

Note: Please complete the consent screen within 10 minutes. After that, you will see Request expired and need to start again from your AI app.

Note: If your account uses two-factor authentication, you may be asked to Verify your identity. Enter your authenticator code and click Verify.

Choosing which accounts a connector reads

  1. Click your account name at the top of the left-hand side menu
  2. Click MCP server
  3. Under Connectors reading {account}, click Choose accounts next to the app
  4. Tick the accounts the app should read, and untick the rest
  5. Click Save changes

You will see the message Accounts updated.

The app picks up the change on its next request, so there’s no need to reconnect. You need to keep at least one account ticked. To stop the app reading altogether, remove its access instead.

Removing a connector’s access

  1. Click your account name at the top of the left-hand side menu
  2. Click MCP server
  3. Under Connectors reading {account}, click Remove access next to the app
  4. Confirm:
    1. If the app also reads your other accounts, click Remove access. It stops reading this account and keeps the others. You will see the message Access removed
    2. If this is the only account it reads, click Disconnect. You will see the message {app} disconnected

To disconnect an app from all your accounts at once, click Disconnect {app} from all accounts instead in the same window.

A disconnected app disappears from the list. To use it again, connect it again from the AI app.

Creating an MCP key

An MCP key is an API key for the same server, without the consent screen. Use it when your AI app or workspace can’t add a custom connector, for example for a script.

  • One per account - you can have one MCP key per account, and it reads only that account.
  • Reads as you - anyone who has the key can read the account’s results as you, until you revoke it.
  • Shown once - Gleanin doesn’t store the key, so it can’t be shown again.

To create an MCP key, follow the steps below:

  1. Click your account name at the top of the left-hand side menu
  2. Click MCP server
  3. Under MCP key, click Create MCP key
  4. Under Name, enter what the key is for
  5. Tick I'll keep it out of shared docs, chats and code repositories
  6. Click Create key
  7. Under Your MCP key, click the copy button and store the key somewhere safe, such as a password manager
  8. Click I've stored it safely

If you lose the key, revoke it and create a new one.

Revoking an MCP key

  1. Click your account name at the top of the left-hand side menu
  2. Click MCP server
  3. Under MCP key, click Revoke key
  4. Click Revoke key to confirm

You will see the message Key revoked.

Please keep in mind that revoking a key is a permanent action. Anything using it stops working straight away. You can create a new key for the account afterwards.