Pilot: Connect Apsis Vega to Claude or ChatGPT

Direct link to source page HERE

On this page

1. Before you start

Apsis Vega lets an AI assistant work with your Apsis One account: look up profiles, build segments, create and send emails, import data, and read your reports. You add it once for your whole organization or workspace. After that, each person signs in with their own Apsis One login.

Does your company sign in to Apsis One with Microsoft single sign-on (Entra ID)?

Once we enable Apsis Vega for your company, your Microsoft sign-in will look slightly different, both in Apsis Vega and in Apsis One. Each time you sign in, Microsoft shows an account picker. Always choose your work (Entra ID) account, the same account you use for Apsis One. Choosing a personal Microsoft account, or another account you're signed in with, won't give you access.

You will need:

For Claude: a Claude Team or Enterprise plan, and someone with the Owner or Primary Owner role to add the connector.
For ChatGPT: a ChatGPT Business, Enterprise or Edu workspace, and a workspace Admin or Owner to add the plugin. (Personal Plus/Pro plans can only use custom MCP servers in a limited, read-only way, so Apsis Vega can't create or send anything there.)
An Apsis One login for every person who will use Apsis Vega. Each person gets access to the Apsis One accounts they can already see when they sign in to Apsis One.
The connection details in the next section.

You only need to follow the section for the assistant you use. If your company uses both, follow both. Each one takes about 10 minutes, plus the time it takes us to reply where a step needs that.

2. Connection details

You'll copy these values during setup. Paste them exactly, with no extra spaces.

Name	`Apsis Vega`
Server URL	`https://mcp.ai.apsis.one/mcp`
OAuth Client ID for Claude	`PJVZTN8mA41aFzcPEkeSBx2xcUjeCUpt`
OAuth Client ID for ChatGPT	`e9HbuZOHegu73qVDOPGDgCYRhF7oCq8m`
OAuth Client Secret	Leave empty. Apsis Vega doesn't use one.
Your Apsis contact	agneta.nevell@efficy.com

3. Set up Apsis Vega in Claude

An Owner adds the connector once for the organization (steps 1–4). Then every member connects their own account (steps 5–6). Claude needs nothing back from us.

Part A — Organization Owner: add the connector

Owner: Open your organization's connector settings
Sign in at claude.ai and go to Settings → Organization settings → Connectors (labelled Admin settings → Connectors on some plans).
Owner: Add a custom connector
Click Add custom connector (on some plans: Add → Custom → Web) and fill in:
- Name: Apsis Vega
- Remote MCP server URL: https://mcp.ai.apsis.one/mcp
Owner: Enter the OAuth Client ID
Open Advanced settings and fill in:
- OAuth Client ID: the Claude Client ID from Connection details
- OAuth Client Secret: leave empty
Owner: Save
Click Add. Apsis Vega is now available to everyone in your organization. Let your team know they can connect.

Part B — Each team member: connect your account

Each user
Connect Apsis Vega
In Claude, go to Settings → Connectors, find Apsis Vega and click Connect.
Each user
Sign in with your Apsis One login
1. A browser window opens the Apsis sign-in page.
2. Sign in the way you sign in to Apsis One (email and password, or your company's Microsoft sign-in if you normally use it).
3. Then approve the Apsis Vega consent screen.
4. You're returned to Claude and the connector shows as connected.

Turning it on in a chat: in a conversation, open the + / tools menu, go to Connectors and check that Apsis Vega is switched on. Claude asks for permission the first time it uses each Apsis Vega action. You can choose Allow always for actions you're comfortable with.

4. Set up Apsis Vega in ChatGPT

A workspace Admin adds Apsis Vega to the workspace as a plugin, once. Members then install it and connect their own accounts. ChatGPT normally needs nothing back from us.

ChatGPT calls connectors plugins, so the menus below say Plugins.

Do Part A as a workspace Admin or Owner. Regular members don't see the Add button on the Plugins page.

Part A — Workspace Admin: add the plugin

Admin
Open your workspace's Plugins pageIn ChatGPT, open Workspace settings → Plugins.
Admin
Create the pluginClick Add → Create MCP plugin and fill in:
- Custom name: Apsis Vega
- Description: Work with your Apsis One account: profiles, segments, emails, imports and reports.
- Connection: Server URL, then https://mcp.ai.apsis.one/mcp
- Authentication: OAuth
You can leave the icon empty. Don't click Create yet.
Admin
Enter the OAuth settings
Click Advanced authentication settings and fill in:
- Registration method: User-Defined OAuth Client. A notice that CIMD is unavailable is expected; ignore it.
- OAuth Client ID: the ChatGPT Client ID from Connection details
- OAuth Client Secret: leave empty
- Token endpoint auth method: none. Apsis Vega has no client secret, so this one matters.
- Default scopes: select only openid, profile, email and offline_access, and leave the rest unticked. offline_access keeps you signed in, so you aren't asked to log in again every day.
- OIDC enabled: leave unticked.
Admin
Check the callback URL
The same advanced settings show a Callback URL, just above the Client ID. It should be exactly https://chatgpt.com/connector/oauth/ueXWGs6J3gRD. That URL is already allowed for every workspace, so if yours matches, go straight to the next step.

If your callback URL is different, you can still create the plugin, but don't connect yet. Click the URL to copy it and email it to your Apsis contact (see Connection details), for example:

Subject: Apsis Vega – ChatGPT callback URL for <your company> Hi, Please enable Apsis Vega for our ChatGPT workspace. Company: <your company name> Apsis One account: <your Apsis One account name> Callback URL: https://chatgpt.com/connector/oauth/<…> Thanks!

The callback URL isn't a password, so normal email is fine. We register it and reply when it's ready, usually within one business day. Until then, signing in fails with an error about a callback URL that isn't allowed.
Admin
Create it
Tick I understand and want to continue, then click Create.
Admin
Check who can install it
Apsis Vega now appears on the Plugins page, under your workspace's tab. Check that Availability is Enabled. Installation policy Available lets members install it themselves; change it there if only some people should use it.
Admin
Connect and test
Install and connect Apsis Vega for yourself as in Part B. Then start a new chat and ask: Using Apsis Vega, which Apsis One accounts can I access?

Part B — Each team member: connect your account

Each user
Install Apsis Vega
In ChatGPT, open Plugins, find Apsis Vega under your workspace's tab, and install it.
Each user
Sign in with your Apsis One login
When ChatGPT asks you to connect, sign in the way you sign in to Apsis One; there's no separate approval screen. Your teammates don't need to send us anything.

Using it in a chat: type @ in the message box and choose Apsis Vega, or simply mention "Apsis Vega" in your request.

5. Start using Apsis Vega

Try one of these in a new chat to check everything works:

Which Apsis One accounts can I access with Apsis Vega?
Show me the results of the last email we sent.
Create a segment of profiles who opened an email in the last 30 days.
Draft a newsletter email announcing our autumn sale, and give me a preview link.

Good to know

Email previews open in your browser. When Apsis Vega drafts an email, it gives you a preview link. Open it to see exactly how the email will look before anything is sent.
File uploads go through your browser. When you import profiles or add images, Apsis Vega gives you an upload link. Open it, choose your file, and the file goes straight to Apsis without passing through the AI assistant.
Check before you send. Apsis Vega acts with your own Apsis One permissions, so review the preview, audience and sender it shows you before you agree to send an email.
New features need a refresh. When we tell you about new Apsis Vega features, disconnect and reconnect Apsis Vega (or switch it off and on again in your connector settings) to pick them up. Claude and ChatGPT keep their own copy of the feature list until you do.

6. Troubleshooting and help

ChatGPT shows an error about the callback / redirect URL when I sign in.

Compare the plugin's callback URL with the one in ChatGPT step 4. If it's different, send it to us as described there and wait for our confirmation.

Claude says it couldn't connect or that authorization failed, before I ever see the Apsis sign-in page.

The connector was probably added with Register automatically, which Claude selects by default in the newer form. Remove the connector and add it again, choosing Use your own OAuth client with the Claude Client ID (Claude step 3). Sign-in settings can't be changed on an existing connector.

The sign-in page says I don't have access, or Apsis Vega says it can't find any accounts.

Check that you signed in with the same login you use for Apsis One. If you did, contact us with the email address you signed in with and we'll check your access.

I can't find the connector settings, the "Add custom connector" button, or "Create MCP plugin". Only Claude organization Owners and ChatGPT workspace Admins or Owners can add Apsis Vega, and only on the plans listed in Before you start. In ChatGPT it's under Workspace settings → Plugins → Add. Claude and ChatGPT sometimes rename menu items, so if a label differs slightly from this guide, look for the closest match under Connectors or Plugins.

The assistant doesn't use Apsis Vega.

Check that Apsis Vega is switched on for the conversation (see the notes at the end of the Claude and ChatGPT sections). Mentioning "Apsis Vega" in your request also helps.

Apsis Vega behaves oddly: an action is blocked before anything happens, or the assistant says an action is missing or lacks a setting.

Apsis Vega is still evolving, and Claude and ChatGPT keep their own copy of its list of actions until you refresh it, so an old copy can disagree with Apsis Vega. Refresh the connector, then start a new chat, because an existing chat keeps the copy it started with:

Claude: in Settings → Connectors, disconnect Apsis Vega and connect it again.
ChatGPT: on the Plugins page, open Apsis Vega and choose Refresh. If there's no Refresh, disconnect it and connect it again.

An action stopped by the assistant itself never reached Apsis, so nothing was changed; retry it in the new chat.

I'm asked to sign in again.

For security, sign-ins expire after a period of inactivity. Click Connect again and sign in. In ChatGPT, also check that offline_access was selected in the default scopes (ChatGPT step 3).

How do I remove Apsis Vega?

Each user can disconnect it under Settings → Connectors (Claude) or Plugins (ChatGPT). Owners and Admins can remove it for everyone from the same organization or workspace settings they used to add it.

Need help? Contact your Apsis contact at agneta.nevell@efficy.com. Please include which assistant you use (Claude or ChatGPT), the step you're on, and a screenshot of any error message.