Once the MCP server is installed, you talk to Claude the way you normally would. These patterns help Claude use Stratta well and return answers you can verify.Documentation Index
Fetch the complete documentation index at: https://docs.stratta.ch/llms.txt
Use this file to discover all available pages before exploring further.
Just ask in plain language
You don’t need special syntax. Mention the norm if you know it, and ask for citations:[SIA 261, 8.2, p. 44].
Patterns that work well
Name the norm when you know it
Name the norm when you know it
“In SIA 263, how is the buckling resistance of a steel column verified?” — naming the norm
lets Claude go straight to the right document instead of searching across all of them.
Ask for the citation explicitly
Ask for the citation explicitly
Adding “cite the exact section and page” nudges Claude to back every claim with a reference
you can open in the printed norm.
Let it follow cross-references
Let it follow cross-references
For combination or safety-factor questions, ask the full question. SIA splits rules across
norms (the action in 261, the factors in 260). Claude follows the links — don’t artificially
restrict it to one norm.
Ask to see a figure
Ask to see a figure
“Show me the figure for the wind pressure coefficient zones.” Claude retrieves the figure and
includes a link to view it full-size.
Why answers are trustworthy
Claude is instructed to back every technical claim with a citation to a section it actually opened — never from memory. If a value depends on another norm, it follows the cross-reference before concluding. This is the core of how Stratta works.What Claude can’t do
- Answer about norms you haven’t ingested. Stratta only knows the norms in your workspace. See Supported norms and Ingest a norm.
- Replace engineering judgment. Stratta retrieves and cites the norm accurately; the responsibility for the design decision remains yours.
Next steps
Ingest a norm
Add the norms you need to your workspace.
MCP read tools
Exactly what Claude calls under the hood.