Run your compliance program from the tools you already work in. from the tools you already work in.

With one endpoint. Point your MCP client at us.probo.com/api/mcp/v1 or eu.probo.com/api/mcp/v1, complete the OAuth flow, and the tools appear.

Yes. Use the same /api/mcp/v1 endpoint on your own Probo origin, with the authentication and permissions of your deployment.

Connect Claude, ChatGPT, Codex, Cursor, VS Code, Windsurf, Zed, OpenCode, or another compatible MCP client. The setup and authentication method depend on the client.

Agents can query risks, controls, evidence, audits, and findings, and create or update records when you grant the required write scopes.

Only when both its token scopes and the connected user’s permissions allow it. Use read-only scopes when the agent only needs to inspect data.

No. Access is limited to the intersection of the token scopes and the permissions of the person who connected it.

Clients discover the available tools and their schemas when they connect. Reconnect to discover newly available tools, subject to your granted scopes.

No. Probo uses the open Model Context Protocol, so compatible clients can connect without a proprietary integration.

Tools let an agent read or change Probo records. Skills provide reusable compliance workflows that guide how the agent uses those tools.

Yes. The compliance skills are open source, so you can read them, adapt them to your procedures, or write your own.

You choose the token scopes, and Probo enforces the connected user’s existing permissions on every operation.

Yes. Agents go through the same authorization layer as the console, and every authorized call is written to the audit log with the timestamp, the action, the resource, and the identity behind it. Since an agent authenticates with an OAuth token issued to a person, its actions are attributed to that person. Entries are immutable and exportable as CSV.

Probo sends nothing to a model provider. The MCP server only answers the client you connect, so where the data goes depends on that client: with Claude or ChatGPT it is processed by Anthropic or OpenAI under your own plan and your own retention and training settings. Point a local model at it and no third party sees anything. Probo's own AI features do use Anthropic and OpenAI, both listed on our subprocessor page.

Yes. API, MCP, and CLI access are included for every customer, with no add-on, no tier, and no per-call quota tied to a plan. What an agent can reach is set by OAuth scopes and user permissions, not by billing.