Documentation

On this page
  1. What this is?
  2. Install in Claude
  3. Other MCP clients
  4. The trust model
  5. Verifying citations
  6. Retrieval architecture
  7. The MCP API
  8. The REST API
  9. Privacy & logging

What this is?

anthroposophy.ai is a retrieval API over the Gesamtausgabe (GA 1–354), Rudolf Steiner’s complete published works. The corpus is exposed through three interfaces:

All three interfaces serve identical content under the same trust guarantees and citation contract. Synthesis is the responsibility of the agent or the human reader; the system supplies verbatim passages, citation verification, and trust signals.

The system is not a conversational assistant. It does not paraphrase Steiner from a language model’s training memory. It is a corpus with retrieval primitives, an explicit trust contract, and a marked boundary between retrieval and synthesis.

A stock language-model agent answering questions about Steiner draws on two sources: training memory — uneven, paraphrased, mixed with secondary commentary, and unable to cite specific volume / lecture / paragraph references with reliability — and web search, which returns encyclopedia summaries rather than verifiable primary sources and rarely surfaces the German original alongside an English translation. An agent using this API shifts from hallucination-prone synthesis to retrieval-anchored response. Quotations carry stable per-paragraph URLs; translations declare their edition and their alignment to the German source; references are verified before they are cited; and a negative finding (“Steiner does not say X”) is surfaced as substantive evidence rather than concealed as a retrieval failure. The agent contract at /llms.txt directs the client to preserve the boundary between retrieval and synthesis, and the trust signals on every response carry that boundary through to the reader.

Install in Claude

If you use the Claude website or desktop app, this site can be installed as a connector. Once installed, Claude will use the corpus to answer questions about Steiner’s work, citing verbatim passages with stable URLs.

Server URL
https://anthroposophy.ai/mcp
  1. In Claude, open Customize from the left sidebar, then click Connectors.
  2. Click the + button at the top of the Connectors panel.
  3. Paste the URL above into the server URL field. Give the connector a name (e.g. Anthroposophy.ai).
  4. Click Connect.
  5. Start a new conversation and ask an anthroposophy-related question.
Try this first Where does Steiner discuss the etheric reappearance of Christ? Show me the German alongside the English.

The connector is read-only. It exposes the retrieval tools described under The MCP API and cannot take any action on the user’s account. Claude invokes the tools only when the conversation calls for them.

Other MCP clients

For Claude Code, Cursor, or any other MCP-capable client, point the client at https://anthroposophy.ai/mcp. The server uses streamable HTTP transport per MCP spec 2025-11-25. Access is anonymous; rate limits may be applied as the service scales.

The server’s instructions field carries the agent contract — verify before citing, distinguish retrieval from synthesis, render citation URLs inline — and is delivered to the client on the initial handshake. The same prose is published at /llms.txt for direct inspection.

The trust model

Every retrieved passage carries a text_trust value indicating textual provenance:

Quotation gating

The fetch_passage tool returns quote_safe: true only when text_trust is verbatim. The agent contract at /llms.txt restricts the use of quotation marks to content retrieved under this flag, and prescribes indirect-speech phrasing (“Steiner describes…”, “in the lecture of…”) for material that is not verbatim. This operationalises the distinction between citation and synthesis at the response level.

Verifying citations

Any citation not directly returned by a retrieval call should be verified before it is used.

verify_locus

The MCP tool verify_locus and the REST endpoints under HEAD /v1/steiner/verify/... confirm the existence of a GA reference — volume, lecture date, and paragraph — in the indexed corpus. A 200 response indicates that the reference is indexed; a 404 indicates that it is not indexed or is malformed. Verification is intended to occur before a citation is committed to.

Translation provenance

Each passage response includes edition_basis (the published edition the passage was drawn from), is_original (true for the original-language source, false for translations), and alignment_confidence (paragraph-count parity between the translation and the original-language source). The original-language source is reachable at the same passage URL via ?edition=original or the relevant lang parameter (for Steiner, lang=de).

Cross-edition comparison

fetch_parallel returns the same passage across multiple translation editions side-by-side. The tool is used when translation choices are at issue — for instance, when comparing how successive translators have rendered a German idiom or a Steiner-coined philosophical term.

Negative evidence

“Does Steiner say X about Y?” is a research-grade question whose answer may be negative. A 404 from verify_locus indicates that the cited reference does not exist in the indexed corpus, allowing the negative finding to be treated as substantive evidence rather than concealed as a retrieval failure.

Retrieval architecture

The Gesamtausgabe is full-text indexed at paragraph granularity. Searches are language-aware in both English and German, ranked by relevance, and returned with stable per-paragraph citation URLs.

The MCP API

MCP (Model Context Protocol) is the agent-tool protocol used by Claude and several other AI clients. The MCP server at https://anthroposophy.ai/mcp publishes the tools below. The canonical, versioned list is maintained at /changelog.

Tools

The REST API

The REST API at https://anthroposophy.ai/v1/ serves the same content as MCP. Access is anonymous; rate limits may be applied as the service scales.

Search

GET /v1/steiner/search?q=etheric+body&lang=en

Required parameter: q. Optional parameters: lang (en or de, default en), n, ga, ga_range, from_date, to_date, edition, cursor. English uses Porter stemming; German uses Snowball-de.

Verify

HEAD /v1/steiner/verify/ga/13
HEAD /v1/steiner/verify/ga/13/1909-08-30
HEAD /v1/steiner/verify/ga/13/1909-08-30/p47

Returns 200 if the reference is indexed, 404 if it is not. Required prior to quoting any citation not retrieved directly within the current session.

Fetch passage

GET /v1/steiner/en/ga/13/1909-08-30/p47.json
GET /v1/steiner/de/ga/13/1909-08-30/p47.json
GET /v1/steiner/en/ga/13/1909-08-30/p47?edition=RSP1964

The JSON response includes available_versions[], edition_basis, alignment_confidence, and is_original. Omitting the .json suffix returns a browseable HTML rendering with a sidebar enumerating other available versions.

Discovery and static endpoints

Privacy & logging

MCP and REST calls are logged on the server for operational monitoring and capacity planning. Logs record the request (tool name, parameters, timestamp, source IP) and the response metadata (status, byte size, latency). Logs do not capture downstream agent prompts or the wider reasoning context a client may carry; only the requests issued to the retrieval API are recorded.

Rate limits are enforced at the edge per source IP. There is no per-user accounting, as there is no authentication.