Connect Apsis Vega to Claude or ChatGPT

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.

The Apsis Vega skills are optional but recommended. They are short written guides that teach the assistant how to do common jobs well with Apsis Vega, such as building an audience, importing contacts, or planning and sending an email campaign. You add them once, after the connector (Part C of each 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 for the connector and another 5 to 10 for the skills, 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.

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). The Owner can add the skills at any time after that (steps 7–11). Claude needs nothing back from us.

Part A — Organization Owner: add the connector

1. 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).
2. 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
3. Owner Enter the OAuth Client ID What you see next depends on your organization. Claude shows one of two versions of this form.
   • If you see Authentication and OAuth client choices:
     • Authentication: Sign in now
     • OAuth client: Use your own OAuth client. Claude marks Register automatically as detected and selects it, but Apsis Vega doesn't support that option and sign-in will fail. Change it.
     • Client ID: the Claude Client ID from Connection details
     • Client secret: leave empty
   • If you see Advanced settings instead: open it and fill in
     • OAuth Client ID: the Claude Client ID from Connection details
     • OAuth Client Secret: leave empty
   Check this before saving. Claude doesn't let you change sign-in settings afterwards, only remove the connector and add it again.
4. 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

5. Each user Connect Apsis Vega In Claude, go to Settings → Connectors, find Apsis Vega and click Connect.
6. Each user Sign in with your Apsis One login A browser window opens the Apsis sign-in page. 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). Then approve the Apsis Vega consent screen. You're returned to Claude and the connector shows as connected.

Part C — Organization Owner: add the Apsis Vega skills

Do this any time after Part A. It adds the skills for everyone in the organization; members don't need to connect anything beyond Part B.

7. Owner If the upload is refused, check that skills are switched on You can usually skip this step. If Claude refuses the upload in step 9, or the skills don't show up afterwards, check in Admin settings that Skills is on and, on Enterprise, that Code execution and file creation is on as well, then try again.
8. Owner Download the skills Download apsis-vega-skills-claude.zip. Don't unzip it.
9. Owner Upload it Go to Admin settings → Plugins & skills → Add → Plugins → Upload a plugin (not the Skills entries above it). Choose Upload to a new marketplace, give it a name such as Apsis Vega, then choose the ZIP and click Upload. Claude runs a short security scan; wait until the plugin shows Passed.
10. Owner Make it available to everyone A new plugin starts with No one yet. On its row, open the ⋮ menu, then Default access, and choose Installed by default. (Available to install lets members add it themselves from Customize → Plugins.)
11. Each user Find the skills The plugin appears under Customize → Plugins with its four skills. Claude uses them by itself when a request fits, for example "How many contacts do I have in Stockholm?". Connect Apsis Vega under Customize → Connectors first (Part B); the plugin does not add a second connector.

4. Set up Apsis Vega in ChatGPT

A workspace Admin adds Apsis Vega to the workspace as a plugin, once (steps 1–7). Members then install it and connect their own accounts (steps 8–9). The Admin can add the skills at any time after that (steps 10–16). ChatGPT normally needs nothing back from us.

ChatGPT lists both the Apsis Vega connector (Part A) and the Apsis Vega skills (Part C) as plugins, so the menus below say Plugins.

Part A — Workspace Admin: add the plugin

1. Admin Open your workspace's Plugins page In ChatGPT, open the Admin Console → Plugins (called Workspace settings → Plugins in some workspaces). It opens on admin.openai.com, with a tab named after your workspace.
2. Admin Create the plugin Click + Add → Create MCP App (Create MCP plugin in some workspaces) 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.
3. 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.
4. 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.
5. Admin Create it Tick I understand and want to continue, then click Create.
6. 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.
7. 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

8. Each user Install Apsis Vega In ChatGPT, open Plugins, find Apsis Vega under your workspace's tab, and install it.
9. 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.

Part C — Workspace Admin: add the Apsis Vega skills

Do this any time after Part A. ChatGPT links the skills to your own Apsis Vega plugin by its ID, which is different in every workspace, so you write that ID into one file before uploading.

10. Admin Find your plugin ID In Admin Console → Plugins, open the Apsis Vega plugin from Part A. The address bar ends in plugin_asdk_app_ followed by 32 letters and digits. Copy the part from asdk_app_ onwards, for example asdk_app_0123456789abcdef0123456789abcdef.
11. Admin Download and unzip the skills Download apsis-vega-skills-chatgpt.zip and unzip it (double-click it on a Mac; on Windows, right-click → Extract All). You get a folder called apsis-vega-skills-chatgpt.
12. Admin Write your ID into .app.json The file is inside the folder. On a Mac, Finder hides files whose names start with a dot: press ⌘⇧. (Command, Shift and full stop) in the folder to show them. On Windows they're already visible. Open .app.json in a plain text editor (TextEdit on a Mac, Notepad on Windows) and replace asdk_app_REPLACE_WITH_YOUR_PLUGIN_ID with your ID. Keep the quotes:
    • Before: "id": "asdk_app_REPLACE_WITH_YOUR_PLUGIN_ID",
    • After: "id": "asdk_app_0123456789abcdef0123456789abcdef",
    Save the file.
13. Admin Zip it again Right-click the apsis-vega-skills-chatgpt folder and compress it: on a Mac, Compress; on Windows, Compress to ZIP file (or Send to → Compressed (zipped) folder). Compressing the files inside the folder instead works too.
14. Admin Upload it In Admin Console → Plugins, on your workspace's tab, click + Add, choose your new ZIP and click Add plugin. When you see Plugin successfully uploaded, click Done. If you see Could not add plugin. Please try again., the skills are already uploaded: update them instead (see the note below).
15. Admin Check it and set who gets it Open Apsis Vega Skills from the Plugins list.
    • Apps should show Apsis Vega marked Required. If the page shows Unavailable apps instead, the ID in .app.json wasn't replaced or is wrong: fix it (step 12), zip again, and upload it with … → Upload new version.
    • Sites: switch off Allow site visitors to use this plugin. It's on by default.
    • Availability → Workspace default: choose Installed to give the skills to everyone, or leave Available to let members install them themselves.
16. Each user Get the skills With Installed, members have the skills already. With Available, they open Customize → Plugins, find Apsis Vega Skills on the workspace's tab and click + Install plugin. Anyone who hasn't connected Apsis Vega yet is asked to sign in, as in step 9.

5. Start using Apsis Vega

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

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 App".

Only Claude organization Owners and ChatGPT workspace Admins or Owners can add Apsis Vega or its skills, and only on the plans listed in Before you start. In ChatGPT it's under Admin Console → 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.

ChatGPT shows "Unavailable apps" on the Apsis Vega Skills page.

The plugin ID in .app.json wasn't replaced, or doesn't match your Apsis Vega plugin. ChatGPT accepts the upload without a warning, so check the page after every upload. Fix the ID (ChatGPT steps 10–13) and upload it with … → Upload new version.

ChatGPT says "Could not add plugin" or "Could not update plugin".

Could not add plugin on + Add means the skills are already uploaded: open Apsis Vega Skills and use … → Upload new version instead. Could not update plugin can be temporary: try once more.

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. Remove the skills too (see the end of Part C); in ChatGPT, removing the skills leaves the connector in place, so remove both.