AgentTwin Documentation MCP Resources
AgentTwin Documentation offers 30 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.
-
AgentTwin agent testing — test workflows before production -
AgentTwin pricing and access -
About AgentTwin -
Contact AgentTwin -
Privacy and data handling -
AgentTwin developer resources -
AgentTwin API authentication -
AgentTwin API versioning and deprecation policy -
AgentTwin sandbox: test a synthetic workflow -
CLI and coding-agent reference -
Worlds, twins, and replicas -
Dashboard guide -
Read evidence and approve a fix -
FAQ -
Fidelity contract -
Welcome to AgentTwin -
Infrastructure and evidence -
Prepare your actual application -
Explore the browser demo -
Your first verified fix -
Product roadmap -
Safety and isolation -
Design reproducible scenarios -
From discovery to a verified fix -
What works today -
Troubleshoot setup and tests -
Example: timeout after a write -
Discover, test and retest -
Reproduce, fix, and retest -
Supported provider operations
Read from the server itself, by connecting to it and calling resources/list on 24 October 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.