INTEGRATIONS · MCP connectors
Model Context ProtocolMCP connectors
The Model Context Protocol gives Edrak a standard way into systems without a native connector: internal tools, legacy platforms, niche software. One MCP server per system.
What Foundry reads
- Internal tools and databases
- Legacy platforms without modern APIs
- Third-party and niche software
- Anything an MCP server can expose
What Atlas writes back
- Actions through the same MCP contract
- Approvals where your rules require them
- Results returned to the source system
- Every call under explicit authority
The same permissions, masking and audit apply to every MCP call, exactly as they do to native connectors.
How the connection behaves
The same rules as every Edrak connection
- Reads under permission
- Retrieval respects the source system's access model. People and agents see only what they are allowed to see.
- Writes under authority
- Actions execute only where authorized, with approvals where your rules require them.
- Audited end to end
- Every read and write lands on the audit log with its authority, evidence and author.
One connection among many.
Native connectors and MCP, all behind the same governance plane.
Explore Integrations & MCP →