Appearance
Workflows Fresh
End-to-end patterns that combine the MCP servers and agent documentation formats into working setups.
| Workflow | What it shows |
|---|---|
| Run Both Servers Together | Wiring XMCP and the Docs MCP into one assistant so it can read docs and call the API |
| Agent Documentation Access | The decision flow for choosing llms.txt vs .md vs skill.md vs MCP |
| Build a Read/Write X Agent | A safe, allow-listed agent that searches, summarizes, and posts |
The mental model
flowchart TD
Q[Agent needs something] --> T{Read or act?}
T -->|Understand the API| D[Docs MCP / llms.txt / skill.md]
T -->|Call the API| X[XMCP tools]
D --> ANS[Grounded plan]
ANS --> X
X --> RESULT[Action performed on X]Reading and acting are two different jobs. The Docs MCP and the llms.txt family answer "how does this work?". XMCP answers "do it." The best agents use both.