Skip to main content
Saphion runs its own MCP server. Once you connect an AI tool to it, you can ask that tool to work with your Saphion Projects, Actions, records and files without leaving the tool. It acts as you: it can do only what you can do in Saphion, and everything it does is recorded.
Everyone with a Platform seat can connect their own tools.
Settings showing the server address and Claude setup.

Saphion in other AI tools

​
Before you start

  • You need a Platform seat and your Saphion work account.
  • Your Saphion must have published its server address. If it has not, Settings > Saphion in other AI tools says “Not published yet”. Your Saphion contact can turn it on.
  • A tool must be set up for your Saphion. If it is not, its section says “Not set up yet” and gives no steps. Your Saphion contact can set it up.

​
Find the server address

Open Settings > Saphion in other AI tools, under Preferences. The Server address section shows the address and a Copy button. The address ends in /api/mcp. Every tool signs in with Microsoft, as you. Saphion does not keep a list of the tools you have signed in.

​
Connect a tool

Choose the tab for your tool. Each connects with your Saphion server address and signs in as you.
The steps in Saphion are for Claude Code.
1

Add the server

Under Claude, copy the command in Add the server and run it in your terminal. It has this form:
2

Sign in

In Claude Code, run /mcp, choose saphion and sign in with your Saphion work account.
3

Ask Claude to use Saphion

For example, “Use Saphion to list my open Actions due this week.” Claude can do only what you can do in Saphion.
The Claude setup command and instructions.

Claude setup

​
Upload a file from your computer

Ask the tool to put a file from your computer into Saphion, for example “Add this PDF to the Harbour Road Project’s Files” or “Import this spreadsheet into the Contacts board”. Saphion gives the tool a link for that one file, which works for 15 minutes. The file lands in the Project’s Files, in a record’s Files, or in an import you then review, under the same size limits as uploading in Saphion. You must be able to change the Project or record it goes to. See Files and Import and export.

​
Choose the Organisation a tool works in

A tool works in one Organisation at a time. By default it is the one you have selected in Saphion. If you belong to several, ask the tool to list your Saphion Organisations and to use one of them. Saphion keeps that choice for that tool until you change it. Every reply from Saphion names the Organisation it worked in. A tool can also ask Saphion who it is acting for, the date and time, and the Organisation, as Beacon is told.

​
See what a tool has done

Everything a tool does is recorded under your name.
  • In Settings > Saphion in other AI tools, a tool that has done something for you has an Activity row with an Open button. It opens the record of what that tool has done for you in this Organisation. It is not in your chats.
  • In Saphion’s Activity, a change reads “Claude via MCP for” your name. A comment or update posted through a tool says “via Claude” or “via ChatGPT”. See Activity.

​
Limit what a tool may do (Admins)

Only an Organisation Admin sees External assistants, at the foot of the settings tab. For each tool, two switches (for example Claude: Read Saphion) control what it may do in your Organisation:
1

Switch a permission off

A tool with Change Saphion off can still read, and is not offered any tool that changes things. With both off, the tool is blocked in your Organisation and says so.
2

Choose Save permissions

The change takes effect on the tool’s next call, for everyone in your Organisation.
3

Undo a restriction

Use existing access removes the restriction and returns the tool to your people’s own Saphion permissions.
External assistant read and change permissions for Claude and ChatGPT.

External assistant permissions

If two Admins change this at once, Saphion refuses the second save and asks you to Reload permissions. This does not supply AI inside Beacon, and it does not hand over any app or model-provider credentials.

​
How it works

  • Admins set the ceiling. Organisation Admins decide which tools may act in their Organisation, and what each may do.

​
How a tool acts under your access

Whichever tool you use, a request travels the same way. Saphion checks it before anything changes.

​
What a tool can and cannot do

​
Approvals

Changes run as you, within your permissions. Anything that archives or deletes records, shares something, or sends something through a connected system, asks first. A tool that supports prompts shows the question with Allow once and Do not allow. Your answer is recorded the same way as in Beacon. A connected system’s tool that is set to Blocked, or to Needs approval, behaves exactly as it does for Beacon. See Connectors.
Permanent deletion is never available to a connected tool. Archive-and-delete requests are always confirmed by you.

​
Privacy and data

  • Everything a tool reads leaves Saphion for that tool and its provider.
  • Saphion applies its data-use checks to what each tool is sent.
  • Sign-ins are held by Microsoft. To stop one tool, an Admin switches off its permissions. To stop your own use, remove the server in that tool.

​
FAQ

An Admin has switched off Read Saphion, Change Saphion or both for that tool. Your Saphion access has not changed. Ask an Admin.
Sign-ins are Microsoft’s, so Saphion keeps no list of the tools you have signed in. Each connected tool has an Activity row once it has done something for you.
In Saphion’s Activity, under your name, and in the tool’s own record, which you open from the Activity row in Settings > Saphion in other AI tools. It is not in your chat list.
Claude and ChatGPT, which includes Codex. A tool is connectable only once your Saphion has set it up; otherwise its section says “Not set up yet”.
Check Activity to see what it did, then change the record back or restore it. An Admin can switch off Change Saphion for that tool.