Skip to main content
Building your Phosra integration with an AI assistant? These docs are LLM-ready. Every page is available as clean Markdown, the entire site is published as a single machine-readable file, and a hosted MCP server lets your assistant search the docs in real time. Point your tool at the endpoints below and it works with the current content — no copy-pasting, no stale snapshots.
Two different MCP servers are referenced on this page and they do different jobs. The docs MCP server (https://docs.phosra.com/mcp) lets an assistant read these docs. The Phosra product MCP server (@phosra/mcp) lets an agent call the Phosra API on a family’s behalf using a phomcp_ token. This page is about the first one.

​
The AI-ingestion endpoints

Every Phosra docs deployment publishes the standard llms.txt files, a Markdown twin of each page, and a docs MCP endpoint. All four are served from the docs root and require no key:
ResourceURLWhat it is
Index/llms.txtA structured table of contents — one line per page with its title, URL, and summary.
Full corpus/llms-full.txtEvery page body concatenated into one file. Drop it into a context window as a complete knowledge base.
Well-known alias/.well-known/llms.txtThe same index at the discovery path tools probe automatically.
Any page as Markdown…/<page>.mdAppend .md to any docs URL for the raw Markdown source of that single page.

​
Grab the whole site in one call

/llms-full.txt is the fast path when you want your assistant to reason over all of Phosra — API reference, concepts, and guides — at once. It is the real, rendered page bodies (not just an index), so nothing is lost. 
# Structured table of contents — start here to see what exists
curl -s https://docs.phosra.com/llms.txt
Each entry in /llms-full.txt keeps a Source: line back to the canonical page, so an assistant can cite exactly where an answer came from: 
# Create MCP token
Source: https://docs.phosra.com/api-reference/control-plane/create-mcp-token

POST /mcp-tokens
Issues a new MCP token bound to the authenticated user's first family. The plaintext token
(`plain`, prefix `phomcp_`) is returned once in `CreatedMcpToken` and never stored server-side…

​
Docs MCP server

For assistants that speak Model Context Protocol, the docs are also a live MCP server at https://docs.phosra.com/mcp. It exposes search-and-retrieve tools over the current published content, so answers stay fresh as the docs change — no re-indexing on your side. Add it to any MCP-capable client. For Claude Desktop, Cursor, or VS Code, register the remote server: 
{
  "mcpServers": {
    "phosra-docs": {
      "url": "https://docs.phosra.com/mcp"
    }
  }
}
Once connected, ask questions like “How do I mint my first Phosra API key?” or “What does a connection.severed webhook payload look like?” and the assistant will pull the answer straight from these pages.

​
The page contextual menu

Every page has a contextual menu (top-right of the page header). Use it to hand the exact page you are reading to your assistant without leaving the docs:

Copy page

Copies the page as clean Markdown, ready to paste into any chat.

View as Markdown

Opens the raw .md source in a new tab.

Open in ChatGPT / Claude

Launches your assistant with the page pre-loaded as context.

Connect via MCP

Grabs the docs MCP endpoint so your tool can search the whole site.

​
Which one should I use?

One specific page

Use Copy page / View as Markdown, or append .md to the URL. Smallest context, most precise.

A whole topic

Grab /llms.txt, find the pages you need, then pull each one’s .md.

Everything at once

Pipe /llms-full.txt into your model as a complete knowledge base.

Live, always-current answers

Connect the docs MCP server so your assistant reads the latest content on demand.
Want an agent to act on the Phosra API — apply rules, read a family’s policy, enforce access — rather than read the docs? That is the Phosra product MCP server, authenticated with an MCP token.