Search documentation

Search documentation

Connect an agent from the browser

Add Stratta as a remote MCP connector: one address, a browser sign-in, and no key to copy.

There are two ways to reach Stratta. This is the shorter one, and the only one that works in cloud agents such as ChatGPT, Codex cloud, or claude.ai, where nothing executes on a machine you control.

The address

https://stratta.ch/mcp

In your agent, add an MCP connector with this address. There is nothing to install: no Node, no Python, no API key.

In ChatGPT, Stratta is published in the plugin directory: open its listing, add it, and the Stratta OAuth flow starts when an authenticated tool is first used. Nothing to paste. OpenAI checks the server every day and makes a new tool available in the directory once it passes its review, so the directory can be a few days behind. Developer mode (Settings > Security and login), which adds the MCP server URL above by hand, always sees the 61 tools the server serves.

In ChatGPT, an answer can end with cards of the clauses it cites: the norm, the clause, the pages and the sentence quoted, checked word for word against the clause, with the full text one click away. The norm reader opens from the side panel of a conversation, to browse a norm without asking the agent.

From a terminal:

claude mcp add --transport http stratta --scope user https://stratta.ch/mcp

What happens next

On its first call your agent finds out it needs authorisation and sends you to a page on Stratta. It shows three things:

  • which application is asking. The name is declared by the application itself, so accept it only if you have just added it;
  • which account is being committed, with a way to switch;
  • which organisation will be read.

You authorise, or you refuse. Nothing is decided without that click.

Access covers every published norm in your organisation and your dossiers, on behalf of your account, until you withdraw it.

Withdrawing access

In your workspace, Connected agents lists the authorised applications and lets you disconnect them. A disconnected application loses access immediately and has to ask you again.

A connector is invisible by nature: it lives inside another application and shows no key. That is what this page is for.

Ingesting through the connector

The ingest_* tools are served to the connector. The pre-pass still reads a PDF on a machine: an agent that has one (Claude Code, Codex, Cursor, Gemini CLI) ingests through the connector, with no npm package and no key. It needs Python 3 with PyMuPDF and the pre-pass script, which it downloads from https://stratta.ch/ingest-prepass.py when it is not already on disk; the procedure is served to it as the resource stratta://skills/ingest-norm. Claude on the web and ChatGPT cannot ingest: nothing runs on a machine of yours there.

When the local server is the right one

Two cases, and they are clear-cut:

  • A dossier attachment read from your disk (add_attachment). It is the one tool the connector does not serve: use the local server.
  • An agent with no browser. A CI job, a scheduled task, a server: nothing there can open the authorisation page. It needs an API key.

Both paths read the same corpus, count against the same quota and apply the same tenancy rules. Only the way you prove who you are differs.

The remote connector exposes 61 tools, three of which a host calls for you rather than the agent: the citation cards, the norm reader, and the profile that tells two connected accounts apart. The local server exposes 59, the local attachment on top.

Security

  • The access token lives one hour and renews itself. An API key lives until you revoke it.
  • The exchange follows OAuth 2.1 with PKCE S256. The authorization code is single-use.
  • Losing membership of the organisation cuts the agent off on its very next call: membership is re-checked every time, never read from the token.