docs mcp MCP Resources
docs mcp offers 49 resources. A resource is data the server exposes for a client to attach as context — a file, a page, an API response — rather than an action. Each has its own page, per client.
-
Agent Team Api -
Agent Team Events -
Architecture -
Engine Commands -
Engine Testing -
Eval Runner -
How Tandem Works -
Protocol Matrix -
Spawn Policy -
Tools -
Tui Commands -
Agent Teams -
Agents And Sessions -
Channel Integrations -
Configuration -
Control Panel -
First 10 Minutes -
Headless Deployment -
Headless Service -
Learn Walkthroughs -
Overview -
Settings And Safety -
Troubleshooting -
Tui Guide -
Workflows -
Agent Runtime Guide -
Agent Workflow Mission Quickstart -
Automation Examples For Teams -
Automation V2 Webhooks -
Autonomous Coding Agents Github Projects -
Browser Setup And Testing -
Choosing Providers And Models For Agents -
Creating And Running Workflows And Missions -
Destination Router -
Destinations -
Engine Authentication For Agents -
Enterprise Client Onboarding Runbook -
Enterprise Data Governance -
External Sources -
Incident Monitor -
Incident Monitor External Log Intake -
Long Running Multi Workflow Goals -
Mcp Automated Agents -
Production Governance -
Prompting Workflows And Missions -
Python -
Scheduling Automations -
Sdk -
Security Posture
docs mcp also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.