Working from Claude or ChatGPT

You can look after your employee list from the chat you already have open. Connect Claude or ChatGPT to Spherum once, sign in as yourself, and then ask in plain words: who hasn’t answered, invite these people, archive somebody who has left. The assistant works as you — with your role and in your spheres — and it never sees what is on anyone’s card.

What you can ask for

The assistant can do six things, the same ones you do on Dashboard:

You ask	What happens
“Who hasn’t accepted their invitation yet?”	It lists the records you can see, with their status and a link to each in the Portal.
“Invite Mary Major, mary.major@example.com, Internal.”	One record is created and the invitation goes out.
“Add these twelve people, but don’t email them yet.”	Up to 20 records at a time. Nobody is emailed unless you ask for it.
“Send Mary her invitation again.”	Re-sends to someone who hasn’t granted access yet.
“Richard Roe has left. Archive him.”	Archives the record, frees the seat and ends your company’s access to his card.
“Richard is back. Restore him.”	Takes the record out of the archive. Access does not come back by itself: he grants it again.

It asks before it acts. Inviting, re-sending and archiving reach real people, so the assistant confirms with you first. Read what it proposes before you say yes — especially a list.

What it cannot do, by design: read a card, revoke anyone’s access, work with tokens, export or print, or change settings. When you need a card, it gives you a link to it in the Portal, where you read it as usual.

Before you start

A Spherum account as an operator or an administrator. You sign in with it during connecting, exactly as you sign in to the Portal, second factor included. What the assistant can see is what that account can see.

Your Claude or ChatGPT account. Any account works: it does not have to use the same email address as Spherum, and the two are never linked beyond this connection. In a company plan of Claude or ChatGPT, the workspace admin may have to add Spherum for everyone first.

The server address. In the Portal, open Settings → Connected apps and press Copy next to the address. It is the same for everyone:

https://api.spherum.ae/api/public/v1/mcp

How connecting works

The whole flow takes about a minute and happens once.

1. You add Spherum in your assistant, using the server address.
2. The assistant sends you to Spherum. A browser tab opens on the Spherum sign-in page.
3. You sign in with your Portal account, the way you always do.
4. Spherum asks you to confirm which app is connecting, to which company, and as whom. You press Allow.
5. You are back in the assistant, and Spherum appears among its connectors.

No key is copied anywhere, and nothing is stored on your computer.

Connecting Claude

The same steps work in Claude in the browser (claude.ai) and in the Claude desktop app.

If your company has already added Spherum for everyone, open Customize → Connectors, press Connect next to Spherum, and go straight to step 5.

1. Open Customize → Connectors and choose Add custom connector.

2. Give it a name, for example Spherum, and paste the server address.

3. Leave the sign-in options as Claude detects them: Sign in now under Authentication, and Register automatically under OAuth client.

   

4. Press Add, then Connect next to Spherum.

5. If a Claude sign-in page opens first, sign in with the same Claude account you are using in the app. This is Claude checking it is you, not Spherum yet.

6. The Spherum sign-in page opens. Sign in, check the confirmation page, and press Allow.

In a new chat, make sure Spherum is switched on in the connectors menu of the message box, then ask your first question.

Connecting ChatGPT

Where Spherum works in ChatGPT depends on your ChatGPT plan.

On any plan with Codex — in the ChatGPT desktop app. Spherum is added as a server for Codex, and you work with it in Codex rather than in an ordinary chat.

1. Open Settings → Plugins, choose Add, and pick the custom MCP option.

2. Give it a name, for example spherum, choose Streamable HTTP, and paste the server address. Leave the bearer token and header fields empty: you sign in instead. Press Save.

   

3. On the MCPs tab, press Authenticate next to it. The Spherum sign-in page opens in your browser.

   

4. Sign in. The confirmation page names the app Codex and warns that you will go back to an app on this computer. That is expected when you started from the ChatGPT app: press Allow.

   

5. A page saying Authentication complete opens. Close it, and the Authenticate button is gone.

Ask your questions in Codex. An ordinary ChatGPT chat does not see servers added this way, and will say Spherum isn’t available.

On Business, Enterprise and Edu plans — in ChatGPT chats. A ChatGPT workspace admin adds Spherum once; you then pick it in a chat by typing @ and sign in to Spherum when ChatGPT asks. For the admin’s steps, see Adding Spherum to your company’s Claude or ChatGPT. On other plans, ChatGPT chats either don’t offer custom servers or let them only read.

The confirmation page

This is the one page where you decide, so read it before you press Allow.

The company. The name of the workspace the app will act in. If you work for more than one, make sure it is the right one.

You. At the foot of the page: Signed in as your name and email address. If it is somebody else’s — a shared computer, an old sign-in — choose Sign in as someone else.

What it will be able to do. The six actions above, and nothing else.

Where you go back. The address of the assistant you started from. When Spherum cannot confirm the app — it is not Claude or ChatGPT, or it returns to a program on your computer — the page says so in a highlighted box. Only continue if you started connecting from that app yourself.

Cancel sends you back to the assistant with nothing connected.

A conversation, for example

You: Who in our team hasn’t accepted their invitation yet?

Assistant: Two people are still at Invited: Mary Major (mary.major@example.com), invited on 3 October, and John Q. Public (john.public@example.com), invited on 9 October. Each has a link to their record in the Portal.

You: Send both of them the invitation again.

Assistant: I’ll re-send the invitation to Mary Major and John Q. Public. Shall I go ahead?

You: Yes.

Assistant: Done — both invitations have been sent again.

The names and addresses above are made up, as everywhere in this documentation.

How long a connection lasts

Up to 90 days. After that, the assistant asks you to sign in to Spherum again, second factor included. In between, it stays connected on its own.

It ends sooner when your Spherum sessions end: a new password, an administrator resetting your account, or using a recovery code. It also ends when your account or the workspace is archived. Connect again from the assistant if you still need it.

Disconnecting

Open Settings → Connected apps in the Portal. Every connection is listed with the app, when it was connected, and when it was last used. The bin icon disconnects it at once: the assistant’s next request is refused.

Your administrators see your connections too, and can disconnect them — for a lost laptop, for instance. Tell them if you no longer use one.

Everything the assistant does is recorded as you, exactly as if you had done it in the Portal.

When something goes wrong

What you see	What it means
“Spherum staff accounts cannot connect apps”	You signed in with a Spherum staff account. Sign in with your company account.
“This workspace is archived, so no app can be connected to it”	The company’s workspace is closed. Nothing can be connected to it.
“Couldn’t reach the MCP server” in Claude	Check the address against Settings → Connected apps. If it matches, write to support@spherum.ae.
The assistant can’t find somebody you know is there	They are in a sphere you are not assigned to. The assistant sees what you see in the Portal.
ChatGPT says Spherum isn’t available in this chat	It was added for Codex. Ask in Codex, or see Connecting ChatGPT for chats.
The assistant asks you to sign in again	The 90 days are up, or your sessions ended. Sign in again from the assistant.
An invite is refused because the person already exists	A record with that email is already there, archived ones included. Ask the assistant to find it, and restore or re-send instead.