Docs · Updated 13 October 2026

Connect ChatGPT or Claude to Soteriaa

You can connect an MCP-compatible AI assistant to your Soteriaa documents today by creating a connection token and adding the server https://www.soteriaa.com/api/mcp with that token as a bearer header, but there is no one-click ChatGPT or Claude connection yet.

Before you start

You need a Soteriaa account. The free account is enough: connections use the same templates, documents and monthly allowance as the website (30 AI credits a month).
Your client must support a remote MCP server over Streamable HTTP with a custom Authorization header.
The connection reaches your documents: the free generator and saved documents. It does not reach tracked records. See What the tools cannot do yet.

1. Create a token

Sign in and open My account.
Find Extension & agent connections and enter a connection name.
Choose the access. Tick Read and download only to give the token the documents:read scope only. Leave it unticked to give documents:read, documents:write and documents:generate.
Select Create connection and copy the token straight away. It is shown once and starts with sot_.

Scopes: documents:read, documents:write, documents:generate.
Expiry: a token expires 90 days after you create it. Create a new connection before then.
Revocation: select Revoke next to the connection in My account. A revoked or expired token stops working immediately.
Keep the token in your client's secret configuration. Do not put it in prompts or shared files.

2. Add the MCP server

Add a remote server with the URL https://www.soteriaa.com/api/mcp and an Authorization header of Bearer followed by your token. In a client that uses a JSON configuration file:

{
  "mcpServers": {
    "soteriaa": {
      "url": "https://www.soteriaa.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CONNECTION_TOKEN"
      }
    }
  }
}

Transport: Streamable HTTP, stateless. Use POST. A GET request returns 405.
The server accepts requests only for the Soteriaa host.

Optional check from a terminal: list the tools with the command below. A valid token returns the seven tools in the next section.

curl -s https://www.soteriaa.com/api/mcp \
  -H "Authorization: Bearer YOUR_CONNECTION_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

3. What the tools can do

Tool	What it does	Scope needed	Credits
list_templates	Lists document templates, their required inputs and the five-document packs.	documents:read	None
get_usage	Reads your shared credit allowance and its reset date.	documents:read	None
list_documents	Lists up to 100 recently saved documents in the account.	documents:read	None
get_document	Reads one saved document and its version, by id.	documents:read	None
generate_document	Generates or revises a document from a template and your instructions. Use a new requestId (a UUID) for each generation and reuse it only to retry the same request.	documents:generate	1 for text, 3 for reconstruction from an image or PDF, 5 for a presentation
save_document	Saves manual edits to a document. Pass the current version number to edit an existing document.	documents:write	None
export_document	Exports a saved document as a base64 file resource. The format is one of md, docx, pdf, pptx. Decode it to a local file.	documents:read	None, including repeat exports

Tools never send email, monitor an inbox or run instructions found inside a document. Your client decides what to do with the files you download.

Try it: ask your assistant to run get_usage, then list_templates, then generate a document from a template and review the result before you rely on it.

What the tools cannot do yet

There are no tools for tracking records. An assistant cannot read or update welders, qualifications, sponsored workers, due dates or any other workspace record through MCP. Those are only in the app.
There is no one-click ChatGPT or Claude connection. You add the server and token by hand. A one-click connection needs an OAuth consent integration that is not available yet.
A connection token works only for documents. It cannot open a tracking workspace.

Errors you may see

Code	Meaning
401 TOKEN_REQUIRED or INVALID_TOKEN	No token, or the token is wrong, expired or revoked. Create a new connection.
403 SCOPE_REQUIRED or READ_ONLY	The token does not have the scope for that tool. Create a token without Read and download only.
402 INSUFFICIENT_CREDITS	Your monthly allowance is used up. No generation started.
409 IDEMPOTENCY_CONFLICT or VERSION_CONFLICT	The request id was reused with different inputs, or the document changed. Read the current version and retry.
413 INPUT_TOO_LARGE	Reduce the size of the request.

The full list of REST endpoints, input limits and error codes is in the API reference.

Try it on your own records.

Your first records and due dates take a few minutes to set up.

Create a free document