Data Processing Agreement — AgentTwin Documentation MCP Resource
Data Processing Agreement
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 Data Processing Agreement from your client
- Claude Code AgentTwin Documentation Resource/Data Processing Agreement run in your project directory
- Claude Desktop AgentTwin Documentation Resource/Data Processing Agreement ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentTwin Documentation Resource/Data Processing Agreement ~/.cursor/mcp.json
- VS Code AgentTwin Documentation Resource/Data Processing Agreement .vscode/mcp.json
- Zed AgentTwin Documentation Resource/Data Processing Agreement ~/.config/zed/settings.json
- Windsurf AgentTwin Documentation Resource/Data Processing Agreement ~/.codeium/windsurf/mcp_config.json
- Cline AgentTwin Documentation Resource/Data Processing Agreement ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentTwin Documentation Resource/Data Processing Agreement ~/.gemini/settings.json
- Grok AgentTwin Documentation Resource/Data Processing Agreement .mcp.json (in your project root)
- ChatGPT AgentTwin Documentation Resource/Data Processing Agreement Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentTwin Documentation Resource/Data Processing Agreement Settings → Connectors → Add custom connector
- LangChain AgentTwin Documentation Resource/Data Processing Agreement pip install langchain-mcp-adapters
Other resources on this server
- AgentTwin | Digital twins for testing AI agents
- AgentTwin enterprise pricing
- About AgentTwin
- Contact AgentTwin about AI agent testing
- 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
- 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.