Skip to main content
Connect an AI tool to Failproof AI Cloud and work with your agents’ data from it. Your tool can query sessions and events, run read-only SQL, read dashboards, alerts, issues, audits, and policies, and, if you hold the permission, make changes such as creating an alert or deploying a policy. Every call runs with your own permissions, in one organization you choose when connecting. There is one address for everyone, hosted or self-hosted:

​
Connect a client

Add the address to your client. The first time a tool is used, your browser opens. Choose where your Failproof AI Cloud is, sign in, pick one organization, and select Allow. Cancel connects nothing. The page names the app and where it returns to. An app that isn’t identified by its own web address is marked unverified app, so continue only if you just started this from your own client.
In claude.ai or Claude Desktop, go to Settings → Connectors → Add custom connector. Name it Failproof AI, enter the address, select Add, then Connect.On Team and Enterprise plans, an owner adds the connector for the organization first. Each person then connects their own account.

​
One organization per connection

A connection acts only in the organization you picked. To use two organizations, add the server twice under different names, such as failproofai-acme and failproofai-sandbox, and connect each to its own organization. Demo organizations don’t accept connections. Pick your own organization instead.

​
Permissions

A connection can do what you can do in the organization, within the set below. It follows your current permissions: if an admin gives you more, the tool gains it, and if they take something away, the tool loses it on its next call. A few tools need no permission because they read no organization data: building session and event links, and searching this documentation. An AI tool can never touch API keys, users, settings, or organization administration, and it can’t send events.

​
Approving changes

Writes ask you first if your client can show the prompt. You see what will change and select Approve this change to go ahead. If you decline or don’t answer within about 4 minutes, nothing changes. Some clients stop waiting after a minute, so answer promptly.
A client that doesn’t support prompts isn’t asked, and a write runs as soon as the client makes the call. There, your client’s own confirmation is the only one, so keep it on for write tools.

​
Connected apps and revoking

Settings → Integrations → MCP lists your connected apps in the current organization, with their permissions and last use. Revoke cuts an app off at once. Removing the server in your client also revokes the connection. You can have up to 5 connected apps per organization. Connecting the same app again replaces its earlier connection.

​
Self-hosted deployments

Choose Self-hosted Failproof AI Cloud when connecting, and enter the address you sign in at. Your deployment must be reachable over public HTTPS. Tool calls and their results pass through the hosted Failproof AI gateway on their way between your AI tool and your deployment. The gateway doesn’t store them.

​
What happens to your data

Results go to the AI tool you connected, and that tool’s provider handles them under its own terms. For each tool call, Failproof AI logs the tool’s name, its outcome, how long it took, and the organization, never the arguments or results. See the privacy policy.

​
Troubleshooting

Still stuck? Email support@befailproof.ai.