This repository provides an official Claude Code plugin that connects Claude to the Vanta MCP Server, giving you access to Vanta's security and compliance tools directly inside your Claude Code sessions.
Note: Vanta's remote MCP server is currently in beta. Request access at support@vanta.com.
Claude Code automatically connects to Vanta's hosted MCP server at:
https://mcp.vanta.com/mcp
This gives Claude tools to:
- Remediate failing tests — list failing compliance tests, inspect which entities are out of scope, and get the context needed to fix them
- Manage controls — browse controls and their framework mappings, list associated tests, and access linked evidence documents
- Assess vendor risk — review vendors, run security assessments, manage risk attributes, and track compliance documentation
- Track vulnerabilities — surface vulnerable assets, and monitor remediation progress
- Govern policies — list, download, and upload policy documents across your compliance program
- Analyze compliance gaps — enumerate framework requirements and identify coverage gaps across SOC 2, ISO 27001, and more
| Command | Description |
|---|---|
/vanta:fix-test <test-id or URL> |
Fix a failing test by generating IaC changes and opening a PR |
/vanta:list-tests |
Show failing tests prioritized by what you can fix from this repo |
/plugin marketplace add VantaInc/vanta-mcp-plugin
/plugin install vanta
/reload-plugins
This loads the plugin and starts the MCP server without restarting Claude Code.
In Claude Code, run /mcp and select vanta. A browser window will open in your Vanta app — click Allow to complete OAuth authorization.
For detailed setup instructions across Claude Code, Cursor, and Perplexity, see the Connecting to Vanta MCP guide.
All integrations use OAuth against https://mcp.vanta.com/mcp. No API keys or tokens to manage.
- Connecting to Vanta MCP — setup guide for Claude Code, Cursor, and Perplexity
- Vanta documentation
- Report an issue
This project is licensed under the terms of the MIT open source license. Please refer to LICENSE file for details.