2,500+ MCP servers ready to use
Vinkius

Drata MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

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.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Drata and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "drata": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Drata
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 Drata MCP Server

Connect your Drata account to any AI agent and take full control of your continuous compliance and automated security monitoring through natural conversation.

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

What you can do

  • Compliance Control Oversight — List internal compliance controls and fetch exact evaluation states to see if technical or administrative requirements are passing or failing
  • Personnel Compliance Tracking — Monitor employee and contractor directories to identify missing security training, background checks, or policy acknowledgments
  • Security Policy Auditing — Retrieve the overarching InfoSec documentation and extract renewal dates and completion rates to assess audit readiness
  • Automated Test Monitoring — Detail which technical monitors across AWS, GCP, or Azure are triggering compliance deviations in real-time
  • Framework Readiness — Track active compliance frameworks (SOC 2, ISO 27001, HIPAA) and get overall readiness scores and control completion percentages
  • Vendor Risk Management — Returns the vendor risk inventory to track security questionnaires and data risk classifications for third-party subprocessors
  • Cloud Asset Verification — Insight into how EC2, RDS, and other infrastructure nodes align against underlying compliance controls

The Drata MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Drata to VS Code Copilot via MCP

Follow these steps to integrate the Drata MCP Server with VS Code Copilot.

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Drata

Ask Copilot: "Using Drata, help me..."10 tools available

Why Use VS Code Copilot with the Drata MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Drata through the Model Context Protocol.

01

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

02

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

03

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

04

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

Drata + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Drata MCP Server delivers measurable value.

01

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

02

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

03

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

04

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

Drata MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Drata to VS Code Copilot via MCP:

01

drata_get_control

Returns passing/failing status, which automated tests provide evidence for this control, the explicit auditor language defining the risk logic, and any manual evidence uploads. Use to investigate why a control is failing, what evidence supports it, or to prepare for auditor questions about a specific requirement. Get detailed status of a specific Drata control — pass/fail state, automated test evidence, and auditor-facing risk language

02

drata_get_person

Returns MDM (Jamf/Intune) enrollment status, background check clearance date, onboarding milestone completion, linked IdP (Okta/Google Workspace) groups for access control mapping, security training completion date, and any compliance gaps. Use when investigating a specific employee compliance issue. Get the compliance onboarding state of a specific employee — MDM enrollment, background checks, IdP grouping, and training milestones

03

drata_get_policy

Essential for assessing audit readiness regarding mandatory annual document refreshes. Get detailed status of a specific Drata policy — renewal dates, employee acknowledgment rates, owner assignment, and version history

04

drata_list_assets

Each asset shows: resource type, resource ID, compliance status against linked controls, encryption-at-rest verification, network boundary adherence, and associated region/VPC. Use when the user asks about infrastructure compliance, unencrypted resources, or needs an asset inventory for audit evidence. List cloud infrastructure assets monitored by Drata — EC2 instances, RDS databases, S3 buckets, and other resources with compliance status

05

drata_list_controls

Each control represents a specific requirement (e.g., "Passwords must be 12+ characters", "MFA enabled for all users", "Encryption at rest required"). Returns control name, description, passing/failing status, mapped framework(s), linked tests, and control owner. Use when the user asks about compliance posture, failing controls, or audit gap analysis. List all compliance controls in Drata — the discrete technical and administrative requirements mapped to SOC 2, ISO 27001, HIPAA, and GDPR frameworks

06

drata_list_frameworks

Each framework shows: name, version, overall readiness score, percentage of controls passing, number of controls mapped, and target audit date. Provides a high-level view of multi-framework compliance posture. Use for board-level reporting, audit planning, or determining which framework needs the most attention. List active compliance frameworks tracked by the Drata workspace — SOC 2 Type II, ISO 27001, HIPAA, GDPR, PCI DSS — with readiness scores

07

drata_list_personnel

Each person includes: name, email, role, employment type, Security Awareness Training status (completed/overdue/not started), device compliance (MDM enrolled, encrypted, antivirus), background check clearance, and policy acceptance rates. Use for "who is non-compliant?", "which employees have overdue training?", or pre-audit personnel reporting. List all tracked personnel in Drata with security training status, device compliance, background check clearance, and policy acceptance

08

drata_list_policies

Each policy includes: name, category, CISO approval status, version number, last review date, next review due, and employee acknowledgment completion rate. Policies are mandatory for SOC 2 / ISO 27001. Use when the user asks about policy status, which policies need review, or audit readiness regarding documentation. List all security and compliance policies in Drata — Information Security, Data Classification, Incident Response, Acceptable Use, and more

09

drata_list_tests

Each test monitors a specific technical requirement in real-time (e.g., "S3 Buckets must not be public", "GitHub branch protection enabled", "MFA enforced in Okta"). Shows test name, associated control, pass/fail status, last evaluation time, and failing resources if any. Use when the user asks about automated monitoring, which checks are failing, or real-time compliance status. List Drata automated continuous compliance tests — real-time monitors checking AWS, GitHub, Okta, and other integrations for security deviations

10

drata_list_vendors

Each vendor includes: company name, data risk classification (Critical/High/Medium/Low), security questionnaire completion status, SOC 2 report review status, last assessment date, data categories shared, and assigned risk owner. Use for vendor risk assessment, subprocessor audits, or evaluating the security posture of your supply chain. List third-party vendors in Drata vendor risk management — risk classification, security questionnaire status, and SOC 2 report reviews

Example Prompts for Drata in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Drata immediately.

01

"Show me all failing compliance controls"

02

"What is the compliance onboarding status for employee John Doe?"

03

"List my active compliance frameworks and readiness scores"

Troubleshooting Drata MCP Server with VS Code Copilot

Common issues when connecting Drata to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

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

Drata + VS Code Copilot FAQ

Common questions about integrating Drata MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect Drata to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.