Skip to main content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools
Changelog
Integrations

Connect AI agents via OAuth2 (CIMD)

MCP clients like Claude and ChatGPT can now register with Probo through a standard OAuth2 client metadata document instead of a pre-provisioned client ID.

Connect AI agents via OAuth2 (CIMD) screenshot

Connecting an MCP client to Probo used to mean provisioning a client ID by hand first.

With OAuth2 Client ID Metadata Document (CIMD) support, clients like Claude and ChatGPT register themselves by pointing at an HTTPS client_id URL. Probo fetches and caches the metadata document, upserts the client on first use, and advertises CIMD support in OIDC discovery once you’ve configured which client URLs are allowed.

It’s opt-in. Nothing changes until you add allowed CIMD client URLs to your OAuth2 config, and existing pre-provisioned MCP clients keep working exactly as before.