Salt Security MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes
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
Vinkius supports streamable HTTP and SSE.
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.




{
"mcpServers": {
"salt-security": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
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 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.
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
Salt Security + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Salt Security 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
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:
block_attacker
Issues a command to block a specific attacker
get_attackers
Lists known threat actors profiled by Salt
get_attacks
Lists detected malicious API attacks
get_endpoint
Retrieves details for a specific API endpoint
get_governance_policies
Lists active API governance rules
get_inventory
Retrieves the auto-discovered API inventory
get_posture_vulnerabilities
Retrieves identified pre-production design flaws
get_system_health
Checks the health of traffic mirror ingestion
list_oas_specs
Lists all uploaded OpenAPI specifications
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.
"List all auto-discovered APIs including shadow and zombie APIs in our infrastructure."
"Are we facing any recent attacks aimed at business logic?"
"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.
MCP tools not available
Salt Security + VS Code Copilot FAQ
Common questions about integrating Salt Security MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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 with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
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.
