Connect ChatGPT or Claude to Saff
Let an AI assistant read your approved Saff tables over MCP, and see exactly what it can and cannot reach.
Connecting
Copy the server URL
It is on the MCP tab under Integrations in your workspace.
Add the connector
In ChatGPT, add a custom MCP connector with that URL and OAuth. In Claude, add a custom web connector and choose Sign in with Claude's published identity.
Sign in with Saff
Choose a workspace where you are an owner or admin. Demo accounts cannot connect, and your AI organisation may need an administrator to allow custom connectors first.
Choose the tables
Nothing is preselected. Picking “all current and future tables” includes ones created later. No API key is involved.
What the assistant can read
Tables and columns
Which tables exist and how their fields are set up.
Rows and evidence
Extracted values with their confidence, the evidence behind them, and the correction history.
Processing status
Whether a batch or a document has finished, and how it ended.
What it cannot do
It cannot upload or extract, edit or review, acknowledge a security finding, delete anything, download originals, export, or touch payments and credentials. Links it returns still need an ordinary Saff sign-in to open — they are not download credentials.
Anything flagged by a security check stays hidden until an authorised person acknowledges it in Saff. Ordinary low-confidence or unreviewed values are readable, with their status attached.
What it costs
Nothing in Saff. Reading over MCP draws nothing from your balance and nothing from the monthly free documents. Your assistant's own subscription and usage rules still apply, and whatever it receives is then held under your account there.
A workspace has to be eligible for integrations before it can connect: a verified owner and, once, a funded wallet. Spending that balance afterwards does not disconnect anything.
Limits
Each connection may make 300 tool calls a minute, sharing that budget with the workspace's other API reads, and search is limited to 30 calls a minute. A workspace may hold ten active connections at once. Lists return 20 results by default and 50 at most.
| Code | What to do |
|---|---|
| resource.not_found | The item does not exist, or it is outside the tables you approved. |
| api.insufficient_scope | The connection was not granted that kind of read. |
| api.invalid_cursor | Permissions or the query changed. Start the list again. |
| mcp.invalid_connection | Reconnect, after checking you are still a member of the workspace. |
| rate_limit.exceeded | Wait for the number of seconds the response gives, then retry. |
Changing or ending access
Owners and admins manage connections on the MCP tab under Integrations. Access can be narrowed or cut immediately; widening it needs a fresh authorisation from the assistant. Leaving the workspace, or losing owner or admin rights, ends access on its own.
Disconnecting stops any further reading. It cannot reach back and remove what the assistant already received, which is the honest limit of any connection like this one.
Does the assistant see my original documents?
No. It reads extracted values and their evidence, never the source files, and it cannot download originals.
Can it change a value I corrected?
No. The connection is read-only. It can see the correction history, including whether a value was changed by a person or came from the extraction, and it can change nothing.
Can our own software be connected to ChatGPT and Claude like this?
Yes. Lenouar, the company behind Saff, builds MCP servers for other software and submits them to the ChatGPT and Claude app directories, as it did for Saff: see its AI assistant integrations service.