2,500+ MCP servers ready to use
Vinkius

Salt Security 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 Salt Security 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": {
    "salt-security": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Salt Security
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 Salt Security MCP Server

Connect your AI directly with Salt Security to proactively defend your Application Programming Interface (API) environment. Improve API discovery, manage security posture, and remediate threats in real-time through simple conversational prompts.

GitHub Copilot Agent mode brings Salt Security 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

  • API Inventory & Discovery — View all auto-discovered APIs in your environment, including unknown or shadow APIs (get_inventory). Retrieve schema details, identify exposed sensitive data (PII), and analyze structural drifts (get_endpoint).
  • Threat Intelligence & Monitoring — Monitor active API attacks and business logic abuses as they happen (get_attacks). Profile known threat actors to uncover behavioral patterns (get_attackers).
  • Active Remediation — Respond to incidents immediately by triggering blockade commands against attackers, seamlessly passing instructions to your integrated WAFs (block_attacker).
  • Posture & Governance Assessment — Identify design flaws and vulnerabilities before they reach production (get_posture_vulnerabilities). Manage OpenAPI (OAS) specifications (list_oas_specs, upload_oas_spec) and verify active governance rules (get_governance_policies).

The Salt Security 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 Salt Security to VS Code Copilot via MCP

Follow these steps to integrate the Salt Security 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 Salt Security

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

Why Use VS Code Copilot with the Salt Security MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Salt Security 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

Salt Security + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Salt Security 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

Salt Security MCP Tools for VS Code Copilot (10)

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

01

block_attacker

Issues a command to block a specific attacker

02

get_attackers

Lists known threat actors profiled by Salt

03

get_attacks

Lists detected malicious API attacks

04

get_endpoint

Retrieves details for a specific API endpoint

05

get_governance_policies

Lists active API governance rules

06

get_inventory

Retrieves the auto-discovered API inventory

07

get_posture_vulnerabilities

Retrieves identified pre-production design flaws

08

get_system_health

Checks the health of traffic mirror ingestion

09

list_oas_specs

Lists all uploaded OpenAPI specifications

10

upload_oas_spec

Uploads a new OAS/Swagger specification

Example Prompts for Salt Security in VS Code Copilot

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

01

"List all auto-discovered APIs including shadow and zombie APIs in our infrastructure."

02

"Are we facing any recent attacks aimed at business logic?"

03

"Block attacker 'ATT-992' immediately."

Troubleshooting Salt Security MCP Server with VS Code Copilot

Common issues when connecting Salt Security 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.

Salt Security + VS Code Copilot FAQ

Common questions about integrating Salt Security 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 Salt Security to VS Code Copilot

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