Connect the Vanta MCP server to Unblocked to give AI agents live compliance context

When a Vanta test fails, the fix almost always lives in code — an infrastructure definition, an access policy, a logging setting — but the failure lives in Vanta, and engineers bounce between the two to work out which resource is out of compliance and why. Vanta’s MCP server exposes tests, controls, and vulnerability data to AI agents, and Unblocked connects to it once so every agent can ask about compliance without its own Vanta setup.

This is a third-party MCP server: Vanta hosts and maintains it, and Unblocked connects to it as a verified MCP server. Nothing is ingested or indexed — Unblocked calls the read-only tools you select at the moment a question needs them, so answers reflect your tests and controls as Vanta evaluates them now.

Wiring Vanta’s MCP server straight into an agent gives it a list of failing tests. Unblocked’s Context Engine reasons across those results and your other sources — following a failing test to the resource it flags, the infrastructure change that caused it, and the Jira ticket or Slack thread where remediation was discussed — and returns one cited answer.

Once connected, any MCP-compatible coding agent — Claude Code, Cursor, Devin, GitHub Copilot, Codex — reaches Vanta context through a single Unblocked MCP server connection.

What you get

• Live tests, controls, and remediation context — Agents see which Vanta tests are failing, the resources behind them, and the controls and frameworks they map to, as Vanta evaluates them right now.
• Compliance gaps next to the code — Vulnerable assets and framework coverage gaps surface where engineers make changes, so a compliance fix starts in the editor instead of a dashboard.
• Read-only, tool-level control — Tools that upload policy documents or otherwise change Vanta are never offered. You choose which read tools Unblocked may call, and Vanta still applies the signed-in user’s role. Change the selection anytime from Settings → Data Sources.
• Context Engine reasoning — Vanta results are reconciled with your code, pull requests, tickets, and conversations, so a failing test leads to the change that broke it and the discussion about fixing it — with citations.

Prerequisites

• An Unblocked account (free to start).
• An active Vanta user who can sign in through Vanta’s OAuth flow for your Vanta region; some Vanta MCP tools are available only to Vanta Admins.
• An MCP-compatible coding agent (Claude Code, Cursor, Devin, etc.) to use the context in your editor.

Step 1: Connect Vanta to Unblocked

1. In Unblocked, go to Settings → Data Sources → Connect another data source, and under Security & Compliance select Vanta.
2. The Vanta MCP server URL is filled in for you. Choose OAuth, click Connect, and sign in to Vanta to authorize Unblocked.
3. Once Unblocked discovers the server’s tools, select the read-only tools it may use and click Save Settings.

Step 2: Install the Unblocked MCP server

On macOS or Linux, one command auto-detects and configures the supported agents on your machine:

On Windows, or when you prefer remote MCP, add the server manually using the configuration below, or follow the manual install guide .

claude mcp add -s user --transport http unblocked https://getunblocked.com/api/mcpsse

{
  "mcpServers": {
    "unblocked": {
      "url": "https://getunblocked.com/api/mcpsse"
    }
  }
}

https://getunblocked.com/api/mcpsse

To give Claude Code, Cursor, GitHub Copilot, Codex, or another MCP-compatible AI coding agent access to Vanta context, connect Vanta to Unblocked and add the single Unblocked MCP server to your agent.

Unblocked acts as the MCP context layer for your Vanta data, searching controls, tests, and frameworks alongside your other connected sources and returning cited results through these tools:

• context_researchResearches a question across your connected sources and calls the Vanta tools you selected when failing tests, controls, or vulnerable assets are relevant, returning a synthesized answer with citations.
• context_get_urlsFetches the full content behind URLs your agent encounters across connected sources — Jira, Linear, Notion, Confluence, Slack, GitHub, and more.

Questions you (or your agent) can ask Unblocked about your Vanta data:

• Which Vanta tests started failing this week, and which infrastructure pull requests merged around then?
• What resources does the failing encryption test flag, and where are they defined in our Terraform?
• Which controls for our audit framework have no linked evidence, and is anyone working on them in Jira?
• Which vulnerable assets is Vanta tracking for the API service, and what did the team decide about them in Slack?