Bring Gdpr
to Cursor
Learn how to connect Dastra to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Dastra MCP Server?
Connect your Dastra account to any AI agent and take full control of your data privacy and GDPR/LGPD compliance workflows through natural conversation.
What you can do
- DSR Orchestration — Manage the full lifecycle of Data Subject Requests (DSR) programmatically, from creation and status tracking to high-fidelity resolution and archiving
- Breach & Incident Tracking — Programmatically document and track security incidents and data breaches to maintain a perfectly coordinated regulatory response
- ROPA & Asset Intelligence — Access your Record of Processing Activities (ROPA) and documented datasets to oversee data flow and classification across workspaces
- Compliance Architecture — Retrieve complete directories of actors (controllers, processors), tags, and processing activities to maintain a high-fidelity privacy registry
- Workspace Visibility — List and manage multiple workspaces programmatically to coordinate privacy operations across different business units directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your API Access Token from your Dastra user profile (API Access)
3. Start managing your compliance registry and privacy requests from Claude, Cursor, or any MCP client
No more manual record logging or digging through complex compliance tables in the portal. Your AI acts as your dedicated DPO and compliance coordinator.
Who is this for?
- Data Protection Officers (DPOs) — instantly retrieve ROPA summaries and check DSR statuses using natural language commands
- Compliance Teams — automate the documentation of security incidents and monitor dataset classifications without leaving your workspace
- Developers & Ops — integrate automated privacy right handling and data mapping into custom internal tools through simple AI queries
Built-in capabilities (12)
Archive a DSR
Create a new data breach record
Create a new Data Subject Request
Get details for a specific DSR
). List actors
List data breaches
List datasets
List Data Subject Requests
List processing activities (ROPA)
List workspace tags
List all workspaces
Update an existing DSR
Why Cursor?
Cursor's Agent mode turns Dastra into an in-editor superpower. Ask Cursor to generate code using live data from Dastra and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Dastra in Cursor
Dastra and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dastra to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Dastra in Cursor
The Dastra MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Dastra for Cursor
Every tool call from Cursor to the Dastra MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Dastra Access Token?
Log in to Dastra, click your profile icon, navigate to API Access, and generate a new Access Token for your account.
What is a DSR request?
Data Subject Requests are exercises of privacy rights (Access, Erasure, etc.) submitted by individuals under data protection laws.
Can I manage multiple workspaces?
Yes! Use the list_workspaces tool to identify your workspace IDs, then use them as parameters in other tools like list_dsr or list_breaches.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.