Bring Authorization
to Cursor
Learn how to connect Cerbos to Cursor and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Cerbos MCP Server?
Connect your Cerbos instance to any AI agent to manage complex authorization policies through natural language conversation.
What you can do
- Permission Evaluation — Use
check_resourcesto instantly verify if a principal can perform specific actions on resources based on your policies. - Query Planning — Generate AST-based query plans with
plan_resourcesto filter database results according to user permissions. - AuthZEN Compliance — Leverage standardized access requests using
authzen_evaluationandauthzen_evaluationstools. - System Monitoring — Check instance health and build metadata using
get_server_infoandget_authzen_config.
How it works
- Subscribe to this server
- Provide your Cerbos instance base URL (e.g.,
http://localhost:3592) - Start auditing and testing your access control logic directly from your chat interface
Who is this for?
- Software Engineers — debug complex RBAC/ABAC policies without manual API calls
- Security Auditors — verify permission logic across different roles and resource attributes
- DevOps Teams — monitor Cerbos instance metadata and configuration status
Built-in capabilities (6)
Single action evaluation using the AuthZEN entity model
Supports execute_all, deny_on_first_deny, and permit_on_first_permit semantics. Batch evaluation of multiple access requests using AuthZEN
This is a read-only evaluation. Evaluates permissions for a principal on a set of resources
Returns endpoint URLs for the AuthZEN APIs
Returns the version and build details of the Cerbos instance
Produces a query plan for obtaining a list of resources a principal is allowed to access
Why Cursor?
Cursor's Agent mode turns Cerbos into an in-editor superpower. Ask Cursor to generate code using live data from Cerbos and it fetches, processes, and writes. all in a single agentic loop. 6 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
Cerbos in Cursor
Cerbos and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Cerbos 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 | 4,000+ 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 Cerbos in Cursor
The Cerbos 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 6 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
Cerbos for Cursor
Every tool call from Cursor to the Cerbos MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check if a specific user has permission to access a resource?
Yes. Use the check_resources tool by providing the principal (user) details and the resource information. The agent will return an evaluation of allowed or denied actions.
How do I generate a filter for my database based on user permissions?
Use the plan_resources tool. It produces a query plan (AST) that you can use to construct database queries, ensuring users only see records they are authorized to access.
Is it possible to verify the Cerbos server version via AI?
Yes, the get_server_info tool retrieves the version, build date, and commit hash of your connected Cerbos instance.
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.
Explore More MCP Servers
View all →
BOE (Boletín Oficial del Estado)
17 toolsAccess the Spanish Official State Gazette (BOE) — search consolidated legislation, daily summaries, and legal analysis directly from your AI agent.
Orkes Conductor
6 toolsOrchestrate microservice workflows via Orkes Conductor — list definitions, track running executions, search workflow history, and inspect task states from any AI agent.
Cin7 Core
10 toolsEquip your AI agent to manage inventory, sales orders, and purchase orders via the Cin7 Core (formerly DEAR Systems) API.
Scribe
10 toolsCreate step-by-step guides and SOPs automatically by recording your workflow and generating visual documentation instantly.