MCP Gateway
Plug your agent into outside services and let it call their tools as if they were its own.
MCP Gateway connects your AI agent to remote services that speak the Model Context Protocol, so it can browse and call their tools from inside your workspace. Administrators and power users reach for it to extend what the agent can do beyond Sois's built-in apps.
What you can do
- Connect any MCP-compatible server by its endpoint URL, over Streamable HTTP, Server-Sent Events, Standard I/O or a managed connection.
- Authenticate securely — API key, bearer token, OAuth 2.0 or basic auth — using a credential held in your Password Vault, never typed into the open.
- Discover the tools and resources each connected server exposes, and test the connection before relying on it.
- Let your agent call remote tools and read remote resources as part of its work.
- Track every tool call in a history log — which tool, who called it, how long it took, and whether it succeeded.
How to use it
An administrator switches MCP Gateway on from Settings → Apps, then adds each server. To connect one, give it a name and endpoint, choose how it authenticates, and link a Password Vault credential so the secret stays safely stored. Test the connection to confirm it's live and to pull in the list of available tools.
Once a server is active, your agent can use its tools automatically when a request calls for them — you don't wire anything up by hand. The history view lets you see exactly what was called and confirm everything behaved.
Working with your agent
You connect the service once; from then on you simply describe the outcome, and your agent reaches for the right remote tool without you naming it.
You: "Use the connected analytics server to pull last month's traffic"
Agent: Calls the remote tool on that server and returns the figures.
How it fits
MCP Gateway widens your agent's reach the same way the built-in apps do — its tools sit alongside Contacts, your Inbox and everything else the agent can call. Credentials come from your Password Vault, keeping every connection authenticated without exposing a secret.
Tip. Always link a Vault credential rather than pasting a key inline — it keeps the secret encrypted and lets you rotate it in one place.