4,000+ servers built on MCP Fusion
Vinkius
VS Code CopilotIDE
Why use Salt Security MCP Server with VS Code Copilot?

Bring Api Security
to VS Code Copilot

Create your Vinkius account to connect Salt Security to VS Code Copilot and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Block AttackerGet AttackersGet AttacksGet EndpointGet Governance PoliciesGet InventoryGet Posture VulnerabilitiesGet System HealthList Oas SpecsUpload Oas Spec
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Salt Security

What is the 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.

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

How it works

  1. Enable the Salt Security integration in your workspace.
  2. Navigate to your Salt Security console.
  3. Go to the Settings or Administration section and generate a new API Token.
  4. Paste this token securely into the configuration fields provided below.
  5. Ask the AI: "Are there any known threat actors exploiting our APIs right now?"

Built-in capabilities (10)

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

Why VS Code Copilot?

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.

  • 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

See it in action

Salt Security in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run Salt Security with Vinkius?

The Salt Security connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full Salt Security details →
Salt Security
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Salt Security using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

Salt Security and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Salt Security to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures Salt Security for VS Code Copilot

Every request between VS Code Copilot and Salt Security is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can the AI forcefully block attackers or does it just view them?

You can explicitly instruct the AI to use the block_attacker tool, which triggers a remediation event across your security infrastructure (e.g., WAF integrations). It provides both visibility and direct active response.

02

Does Salt Security allow me to upload spec definitions (OAS) directly from my files via chat?

Yes, you can upload raw specification content using the upload_oas_spec tool for vulnerability testing and validation. Provide the exact OpenAPI content, and Salt will interpret it securely naturally properly successfully cleanly nicely properly natively completely optimally brightly cleanly beautifully actively quickly seamlessly efficiently correctly elegantly faithfully efficiently natively perfectly.

03

How frequently is the API inventory auto-discovered?

Salt maintains a continuous discovery architecture via passive traffic monitoring. This prevents any drift and immediately identifies 'Ghost APIs' when queried using the get_inventory capability.

04

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.

05

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.

06

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.

07

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.

08

MCP tools not available

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

Explore More MCP Servers

View all →