Contact AgentTwin about AI agent testing — AgentTwin Documentation MCP Resource
Contact AgentTwin about AI agent testing
is one of 39 resources on the
AgentTwin Documentation
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Contact AgentTwin about AI agent testing from your client
- Claude Code AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing run in your project directory
- Claude Desktop AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing ~/.cursor/mcp.json
- VS Code AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing .vscode/mcp.json
- Zed AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing ~/.config/zed/settings.json
- Windsurf AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing ~/.codeium/windsurf/mcp_config.json
- Cline AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing ~/.gemini/settings.json
- Grok AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing .mcp.json (in your project root)
- ChatGPT AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing Settings → Connectors → Add custom connector
- LangChain AgentTwin Documentation Resource/Contact AgentTwin about AI agent testing pip install langchain-mcp-adapters
Other resources on this server
- AgentTwin | Digital twins for testing AI agents
- AgentTwin enterprise pricing
- About AgentTwin
- Privacy and data handling
- AgentTwin developer resources
- AgentTwin API authentication
- AgentTwin API versioning and deprecation policy
- AgentTwin sandbox: test a synthetic workflow
- Security at AgentTwin
- Subprocessors
- Terms of Service
- Data Processing Agreement
- Documentation for coding agents
- AgentTwin REST API reference
- CLI and coding-agent reference
- Worlds, twins, and replicas
- Dashboard guide
- Read evidence and approve a fix
- Try the sample test
- FAQ
- Fidelity contract
- Start with your project
- Runtime requirements and verification
- AgentTwin MCP servers and connection guide
- Prepare your actual application
- Explore the browser preview
- Pull request checks
- Set up your project
- Product roadmap
- Safety and execution limits
- Design reproducible scenarios
- From discovery to a verified fix
- What works today
- Troubleshoot setup and tests
- Understand a timeout after a write
- How a workflow becomes a test
- Reproduce, fix, and retest
- Supported provider operations
Read from the server itself, by connecting to it and calling resources/list on 14 November 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.