Salt Connect · See what exists and how it is governed See every API, MCP server and agent in your cloud, without touching traffic.
Agents reach your business through MCP servers and APIs, and many never show up in traffic you can inspect. Salt Connect uses read-only connectors to inventory what exists and how it is governed across AWS, Azure, GCP and GitHub, in minutes, not months.
“Salt Connect delivered results on day one. We saw our full API inventory, including dozens of zombie APIs, in under 30 minutes.”
DevSecOps Lead · Retail enterprise
The problem
You cannot govern
what you cannot count.
Sprawling microservices, decentralized development and inconsistent tagging make basic questions hard: how many APIs do we have, who owns them, and where is sensitive data flowing? Agents and MCP servers make the answers harder still.
01 API sprawl, no owners
Teams ship faster than inventories update. Most organizations underestimate their API count by a wide margin, and nobody can say who owns what.
02 Dormant and zombie assets
Deprecated APIs, inactive MCP servers and over-permissioned agents sit in cloud configuration. Tools that only watch traffic never see them.
03 Basic questions, no answers
Where is sensitive data flowing? Which gateway policies are missing? Without one inventory, every answer takes a project.
The shift
Stop waiting for traffic to reveal what you have. Ask your cloud, and read the configuration.
How it works
From read-only access to a governed inventory in four steps.
Step 01 Connect read-only
Salt Connect uses read-only connectors and the infrastructure you already run. No agents to deploy, no traffic to redirect, no architecture changes.
- Clouds: AWS, Azure, GCP
- Code: GitHub
- Deploy: minutes, zero traffic impact
Step 02 Read what is configured
Salt reads cloud, gateway and control-plane configureation to find what exists, including assets that never generate traffic.
- Gateways and their policies
- Cloud services and identities
- Scopes and reachable systems
Step 03 Build one inventory
Salt unifies everything it finds across clouds and regions into a single inventory, ready for the Agentic Security Graph.
- APIs across every cloud and region
- MCP servers and tools
- Agents and what they can reach
Step 04 Govern and assign
Flag zombie and deprecated APIs, over-permissioned agents and misconfigured gateways, then route each one to an owner.
- Zombie and deprecated APIs
- Over-permissioned agents
- Ownership and posture gaps
Part of the platform
Configuration is how you know what is allowed.
Salt gives you breadth across every agent, MCP server and API, and depth across exposure, source code, configuration and runtime behavior. Connect is the configuration layer.
Capabilities
What you get with Salt Connect.
Inside-out discovery
Find APIs, MCP servers and agents through your cloud integrations, not by waiting for traffic.
Unified inventory
One view across clouds, regions and gateways.
Zombie and deprecated API detection
See what is still live but no longer used or owned.
Ownership and posture visibility
Know who owns each asset and how it is configured.
Agent and MCP governance
Spot over-permissioned agents and inactive MCP servers.
Fast, non-intrusive deployment
Read-only connectors with zero impact on traffic.
Use cases
Where your team would use it.
Integrations
Works with the cloud you already run.
Connect plugs into your clouds, gateways and source code through read-only access. Nothing to rip out, reroute or rewrite.
FAQ
Frequently asked questions about Salt Connect.
Salt Connect builds an inventory of the APIs, MCP servers and agents in your cloud, and shows how each one is governed. It uses read-only connectors to AWS, Azure, Google Cloud and GitHub.
No. Salt Connect reads cloud and code configuration through read-only connectors, with zero impact on traffic. It finds assets that never show up in traffic you can inspect.
Salt Connect works with AWS, Microsoft Azure, Google Cloud and GitHub, and with gateways such as Kong and Apigee.
In under 30 minutes. Salt Connect starts inventorying your APIs, MCP servers and agents as soon as its read-only connectors are in place.
Salt Connect finds dormant and zombie APIs, inactive MCP servers and over-permissioned agents that sit in cloud configuration. Tools that only watch traffic never see them.
Salt Connect is the configuration layer of the Agentic Security Platform. Salt Surface adds what is exposed from outside, Salt Code adds source code, and Salt Collect adds runtime behavior.
See the APIs across your clouds.
Build your inventory in minutes, with zero traffic impact.