Connect your systems
Bring your own MCP server, at no build fee
A system your company already runs an MCP server for can be connected as it is, inside your own Azure tenant. You choose which of its tools to include, and we review the tool list with you first. There is no build fee. Foreign MCP tools are admitted only when the server marks them read-only.
What it can do
The tools the server exposes. You choose which of its tools to include, and we review the tool list with you first.
Write capabilities
Foreign MCP tools are admitted only when the server marks them read-only.
- Your IT admin adds the server.
- A manager decides who may use it.
- Only then does it appear in your library.
How it connects
- It reads through the system's MCP server or REST API, inside your Azure tenant.
- Your IT admin picks the endpoints and fields; a manager decides who uses it.
- Your admin tags personal or sensitive columns before the first sync.
- Credentials are designed to be held in your own Key Vault, never printed or logged.
- It writes only where your admin allows.
Questions
What does it cost?
There is no build fee for connecting a system's own MCP server.
Can a foreign MCP server write?
Foreign MCP tools are admitted only when the server marks them read-only.