Architecture

Stratta has two parts: the platform at stratta.ch (accounts, keys, organizations) and the MCP server @stratta/mcp (the connector you install in Claude). This page shows how they fit together. It's useful if you're integrating Stratta or just curious.

The big picture#

flowchart LR
    A[Claude / Claude Code] -->|MCP tools over stdio| B["@stratta/mcp<br/>(thin client)"]
    B -->|API key auth| C[Stratta backend]
    C --> D[(TreeRAG store:<br/>documents, sections,<br/>figures, formulas,<br/>tables, cross-refs)]
    E[stratta.ch web app] --> C
    F[You] -->|sign up, API keys,<br/>organization| E

The MCP server is a thin client#

@stratta/mcp is intentionally small. It:

• Speaks the Model Context Protocol over stdio to your Claude client.
• Authenticates each request with your API key.
• Forwards calls to the Stratta backend and returns the results.

All the data and logic (the norms, the org scoping, the citation structure) live on the backend. The package contains no norm content itself, which is why updates are just npx -y @stratta/mcp fetching the latest version.

The backend#

The backend stores each norm as a TreeRAG structure: a tree of sections under a document, with attached figures, formulas, tables, and crossRefs. Read tools query this tree; ingestion tools write to it. Every record carries an organizationId so requests are scoped to your workspace.

Authentication today: API keys#

Stratta authenticates the MCP connector with an API key. There is no browser-based OAuth login for the MCP server today. This keeps the connector simple and works everywhere stdio MCP works. (A remote, OAuth-based option has been evaluated but is not currently offered.) See Security and the MCP overview.

Related#