Cerbos (Access Control) MCP Server for VS Code CopilotGive VS Code Copilot instant access to 19 tools to Add Policy, Add Schema, Authzen Evaluation, and more

Name: Cerbos (Access Control)
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Cerbos (Access Control) MCP Server for VS Code Copilot is a standout in the Developer Tools category — giving your AI agent 19 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "cerbos-access-control": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Cerbos (Access Control) and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Cerbos (Access Control) MCP Server

Connect your Cerbos instance to any AI agent to streamline authorization management and policy auditing through natural language.

GitHub Copilot Agent mode brings Cerbos (Access Control) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 19 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Permission Checks — Use check_resources to evaluate if a principal (user) has the rights to perform specific actions on resources.
Query Planning — Generate AST query plans with plan_resources to filter database results based on complex authorization logic.
Policy Management — List, retrieve, add, or delete policies (RBAC/ABAC) using the Admin API tools like list_policies and add_policy.
Schema & Auditing — Inspect resource schemas and review access logs with list_auditLogs to ensure compliance.
Health & Metrics — Monitor your PDP (Policy Decision Point) status with get_health and get_metrics directly from the chat.

The Cerbos (Access Control) MCP Server exposes 19 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 19 Cerbos (Access Control) tools available for VS Code Copilot

When VS Code Copilot connects to Cerbos (Access Control) through Vinkius, your AI agent gets direct access to every tool listed below — spanning authorization, rbac, abac, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add policy on Cerbos (Access Control)

Add a new policy

add

Add schema on Cerbos (Access Control)

Add or update a schema

authzen

Authzen evaluation on Cerbos (Access Control)

Perform a single AuthZEN access evaluation

authzen

Authzen evaluations on Cerbos (Access Control)

Perform batch AuthZEN access evaluations

check

Check resources on Cerbos (Access Control)

Check permissions for a set of resources

delete

Delete policy on Cerbos (Access Control)

Delete a policy by ID

disable

Disable policy on Cerbos (Access Control)

Disable a policy

enable

Enable policy on Cerbos (Access Control)

Enable a policy

get

Get authzen config on Cerbos (Access Control)

Get AuthZEN configuration metadata

get

Get health on Cerbos (Access Control)

Get Cerbos health status

get

Get metrics on Cerbos (Access Control)

Get Prometheus metrics from Cerbos

get

Get policy on Cerbos (Access Control)

Get a specific policy by ID

get

Get schema on Cerbos (Access Control)

Get a specific schema by ID

get

Get server info on Cerbos (Access Control)

Get Cerbos server version and build information

list

List audit logs on Cerbos (Access Control)

List audit logs

list

List policies on Cerbos (Access Control)

List all policies

list

List schemas on Cerbos (Access Control)

List all schemas

plan

Plan resources on Cerbos (Access Control)

Produce a query plan (AST) for filtering resources

update

Update policy on Cerbos (Access Control)

Update an existing policy

Connect Cerbos (Access Control) to VS Code Copilot via MCP

Follow these steps to wire Cerbos (Access Control) into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Cerbos (Access Control)

Ask Copilot: "Using Cerbos (Access Control), help me...". 19 tools available

Why Use VS Code Copilot with the Cerbos (Access Control) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Cerbos (Access Control) through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Cerbos (Access Control) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Cerbos (Access Control) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Cerbos (Access Control) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Cerbos (Access Control) immediately.

"Check if user 'user_123' with role 'admin' can 'delete' the resource 'document:abc'."

"Show me the health status and version of my Cerbos server."

"List all policies and tell me if there are any for the 'expense' resource."

Troubleshooting Cerbos (Access Control) MCP Server with VS Code Copilot

Common issues when connecting Cerbos (Access Control) to VS Code Copilot through Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Cerbos (Access Control) + VS Code Copilot FAQ

Common questions about integrating Cerbos (Access Control) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.