Integrations

Connect Probo to the client where you already work. Choose an integration below based on whether you need a conversational assistant, a code editor, a terminal workflow, or an application API.

Each guide covers the configuration format and credential method required by that client.

Before you connect

Claude integrations use interactive OAuth and open Probo in your browser for authorization. Integrations configured with a bearer credential use a scoped OAuth token created in Probo. Review MCP authentication before creating or sharing credentials.

AI assistants

Choose an interactive client for investigating compliance data, reviewing records, and completing guided tasks through conversation.

Claude.ai Use Probo in the Claude web application with interactive OAuth

Claude Desktop Use Probo from the macOS or Windows desktop application with interactive OAuth

Code editors

Use a code-editor integration when Probo context should be available alongside your repository and development workflow. These clients use a scoped OAuth token in their MCP configuration.

Cursor Add Probo as a remote server in a project or user mcp.json file

Visual Studio Code Connect GitHub Copilot agent mode with native MCP support

Windsurf Make Probo tools available to Cascade through a remote MCP server

Zed Connect Probo as a context server in the Zed editor

Terminal clients

Choose a terminal client for command-line investigation, scripted development tasks, or workflows that do not require a graphical interface.

Claude Code Connect the Claude Code CLI with interactive OAuth

OpenCode Add Probo to an OpenCode configuration with a scoped OAuth token

Application APIs

Use an application API when you need a repeatable workflow, control over the available tools, or integration with your own product.

OpenAI Responses API Expose selected Probo tools to an application using the OpenAI SDK

Connect safely

Whichever client you choose:

1. Connect to the MCP endpoint for the Probo deployment that contains your data.
2. Grant only the scopes needed for the intended workflow.
3. Use a separate credential for every client or environment when interactive OAuth is unavailable.
4. Start with a read-only request and review tool arguments before approving a write.

If a client cannot connect, review authentication errors or test the endpoint with MCP Inspector.

Continue exploring

Browse MCP tools Find available operations, schemas, and behavior hints

Paginate results Retrieve complete result sets from list operations