An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Salt Security to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Stop API attacks and manage your security posture through chat.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Salt Security.

  1. 01

    Get attackers

    This capability pulls a list of known threat actors profiled by Salt. Use it to understand the behavioral patterns of attackers targeting your environment.

  2. 02

    Get attacks

    This capability retrieves a list of detected malicious API attacks. It helps you see active threats as they happen.

  3. 03

    Get endpoint

    This capability fetches specific details for a single API endpoint. It is useful for inspecting schema details or identifying sensitive data exposure.

  4. 04

    Get governance policies

    This capability lists your active API governance rules. Use it to verify that your APIs are following established security standards.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Salt Security.

  1. 05

    Get inventory

    This capability retrieves your auto-discovered API inventory. It helps you find shadow or zombie APIs in your infrastructure.

  2. 06

    List oas specs

    This capability shows all your uploaded OpenAPI specifications. Use it to manage your API documentation within the security workflow.

  3. 07

    Upload oas spec

    This capability allows you to upload a new OAS or Swagger specification. It helps keep your security models up to date.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Salt Security.

  1. 08

    Get system health

    This capability checks the health of your traffic mirror ingestion. Use it to ensure your security data is flowing correctly.

  2. 09

    Block attacker

    This capability issues a command to block a specific attacker. It passes instructions to your integrated WAF to stop active threats.

  3. 10

    Get posture vulnerabilities

    This capability retrieves identified design flaws from the pre-production phase. Use it to fix vulnerabilities before they reach production.

Real work

What teams actually run

01

Shadow API Detection

Identify undocumented or zombie APIs that have been missed by standard discovery capabilities.

02

Rapid Incident Response

Block a specific malicious actor immediately after detecting an active attack.

03

Pre-production Auditing

Find design flaws in your API structure before they are deployed to production.

04

Governance Enforcement

Verify that all active APIs comply with your organization's security policies.

Automate a task

Put Salt Security to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Salt Security works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Salt Security to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

915ms average. Fast in production.

Salt Security is checked daily against the live service.

Daily averagePeak 1169ms
Oct 3Today
Fastest day
776ms
Slowest day
1169ms
14-day trend
Slowing+20%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Salt Security, so you can see the experience inside your AI.

It does not authenticate your account with Salt Security. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Salt Security Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Salt Security capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "salt-security-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_HEqpwxZCJGloy9SZRikbBjYA9GqrD7wwt82MwMIn/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Salt Security in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Salt Security owners hand off.

This MCP is built for security teams managing large-scale API ecosystems who need to move faster than traditional consoles allow.

  • 01

    API Security Engineer

    Uses the agent to monitor threats and manage API posture.

  • 02

    SOC Analyst

    Hands off threat investigation and attacker blocking to the AI.

  • 03

    DevSecOps Engineer

    Uses the capability to audit OpenAPI specs and find pre-production flaws.

FAQ

Questions Salt Security owners ask.

  • 01

    How do I block an attacker using this MCP?

    You can simply tell your AI client to block a specific attacker. The MCP will then issue a command to your Salt Security console to trigger a blockade via your integrated WAF.

  • 02

    Can this MCP find shadow APIs?

    Yes. The MCP uses the get_inventory capability to retrieve auto-discovered APIs, which includes identifying shadow and zombie APIs.

  • 03

    What AI clients can I use with Salt Security?

    You can use this MCP with any MCP-compatible client, such as Claude, Cursor, Windsurf, or VS Code.

  • 04

    Does this MCP help with API documentation?

    Yes. You can list existing OpenAPI specifications or upload new ones directly through your AI client.

  • 05

    How does the MCP handle API vulnerabilities?

    The MCP can retrieve identified pre-production design flaws using the get_posture_vulnerabilities capability.

  • 06

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

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

  • 07

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

  • 08

    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.

Explore

More in Fort Knox

Suggestions

Connect Salt Security to Claude, Cursor, ChatGPT & more