Integrations

The Probo MCP Server can be integrated with various AI assistants and code editors. Choose your platform below to get started.

AI Assistants

Connect Probo to your favorite AI assistant to manage compliance data through natural conversation.

Claude

Claude Desktop Native MCP support with simple HTTP configuration

Claude Code CLI tool with MCP server configuration

Claude.ai Web interface with workarounds for MCP

Best for: Natural language compliance queries, report generation, risk assessments

Features:

• Direct access to all 32 Probo tools
• Native understanding of compliance terminology
• Long context windows for detailed analysis

---

OpenAI

OpenAI / ChatGPT Integrate with OpenAI API or create custom GPTs

Best for: Custom applications, automation scripts, GPT actions

Features:

• Function calling integration
• Custom GPT creation
• API-based workflows

Code Editors & IDEs

Integrate Probo directly into your development environment for compliance-aware coding.

AI-Powered Editors

Cursor AI-first IDE with one-click MCP installation

Windsurf Codeium's AI editor with MCP support

Zed Fast, collaborative code editor with MCP support

Opencode AI AI-powered coding assistant with MCP integration

Best for: Compliance-aware code generation, inline documentation

Features:

• Code generation with compliance context
• Inline risk annotations
• Automated compliance checks

---

VS Code

Visual Studio Code Use Continue.dev or build custom extensions

Best for: Custom workflows, enterprise environments

Features:

• Continue.dev AI assistant integration
• Custom extension development
• Full VS Code ecosystem access

Comparison

Choose the right integration for your needs:

Platform	Setup Difficulty	Native MCP
Claude Desktop	Easy	✅ Yes
Claude Code	Easy	✅ Yes
Cursor	Easy	✅ Yes
Windsurf	Easy	✅ Yes
Zed	Easy	✅ Yes
Opencode AI	Easy	✅ Yes
VS Code	Medium	⚠️ Via extension
OpenAI	Medium	⚠️ Via API
Claude.ai	Hard	❌ No

Quick Start Guide

1. Generate API Token

Before configuring any integration:

1. Log into your Probo web interface
2. Navigate to Settings → API Tokens
3. Click “Generate New Token”
4. Copy the token for configuration

See Authentication for details.

2. Choose Your Platform

Select an integration based on your workflow:

• For interactive compliance queries → Claude Desktop or Claude.ai
• For command-line automation → Claude Code
• For coding with compliance context → Cursor, Windsurf, Zed, or Opencode AI
• For custom applications → OpenAI or VS Code
• For enterprise integration → VS Code with custom extensions

3. Configure the Integration

Each platform has specific configuration requirements. Follow the guide for your chosen platform:

HTTP Configuration (most platforms):

{
  "mcpServers": {
    "probo": {
      "url": "https://your-probo-instance.com/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer your_api_token_here"
      }
    }
  }
}

4. Verify Connection

Test your integration:

Example query:

"List all organizations I have access to"

Expected behavior: The AI should use the listOrganizations tool and display your organizations.

Use Cases by Integration

Compliance Conversations (Claude Desktop)

You: "Show me all high-priority risks and their mitigation status"
Claude: [Uses listRisks tool with filtering]

You: "Add a new vendor called CloudBackup Inc that provides backup services"
Claude: [Uses addVendor tool]

You: "Generate a compliance status report for our SOC 2 audit"
Claude: [Uses multiple tools to gather data and create report]

Code Generation (Cursor/Windsurf)

# Type: "Create a function to check if all vendors have been reviewed"
# Cursor generates:

async def check_vendor_reviews(organization_id):
    """Check if all vendors have recent reviews."""
    vendors = await probo.list_vendors(organization_id)

    overdue = []
    for vendor in vendors:
        days_since_review = (datetime.now() - vendor.last_reviewed).days
        if days_since_review > 90:
            overdue.append(vendor)

    return overdue

CLI Automation (Claude Code)

# Daily compliance check script
claude-code "Generate a daily compliance report including:
- Open nonconformities
- Overdue obligations
- High-priority risks
- Upcoming audit dates"

# Vendor management
claude-code "List all vendors that haven't been reviewed in 90 days"

Custom Applications (OpenAI/VS Code)

// Build custom compliance dashboard
const dashboard = await generateComplianceDashboard(organizationId);

// Automated risk assessment
const risks = await assessNewRisks(projectData);

// Integration with CI/CD
const complianceStatus = await checkComplianceBeforeDeploy();

Multiple Environments

Configure different Probo instances for various environments:

{
  "mcpServers": {
    "probo-dev": {
      "url": "http://localhost:8080/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${PROBO_DEV_TOKEN}"
      }
    },
    "probo-prod": {
      "url": "https://probo.company.com/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${PROBO_PROD_TOKEN}"
      }
    }
  }
}

Troubleshooting

Connection Issues

Problem: Cannot connect to Probo MCP Server

Solutions:

1. Verify Probo instance URL is correct
2. Check API token is valid and not expired
3. Ensure HTTPS is used for production
4. Test connection with curl:

   curl -H "Authorization: Bearer YOUR_TOKEN" \
     https://your-probo-instance.com/api/mcp/v1/health

Authentication Errors

Problem: 401 Unauthorized errors

Solutions:

1. Regenerate API token
2. Verify token is in Bearer format: Bearer your_token
3. Check token hasn’t been revoked
4. Ensure no extra spaces or newlines in token

See Authentication Troubleshooting for more details.

Tools Not Available

Problem: AI says tools aren’t available

Solutions:

1. Restart your client application
2. Verify MCP server configuration is correct
3. Check client logs for errors
4. Ensure organization_id is valid

Best Practices

Security

• ✅ Use environment variables for tokens
• ✅ Create separate tokens for each integration
• ✅ Rotate tokens every 90 days
• ✅ Use HTTPS for all production connections
• ❌ Don’t commit tokens to version control
• ❌ Don’t share tokens between environments

Performance

• Use pagination for large datasets
• Cache results when appropriate
• Filter server-side instead of client-side
• Use appropriate page sizes (20-100 items)

Organization

• Name tokens descriptively (“Claude Desktop - Production”)
• Document which tokens are used where
• Set up monitoring for token usage
• Review and revoke unused tokens

Advanced Integration

Custom Workflows

Build custom workflows combining multiple tools:

1. Risk Assessment Workflow: Fetch risks, check mitigations, update status
2. Vendor Management: List vendors, check reviews, send reminders
3. Compliance Reporting: Gather data from multiple sources, generate reports
4. Audit Preparation: Collect evidence, check compliance, identify gaps

API Wrapper Libraries

Create wrapper libraries for common operations:

class ProboClient {
  async getAllHighRisks(orgId: string) {
    // Paginate through all risks
    // Filter for high scores
    // Return sorted results
  }

  async checkVendorCompliance(orgId: string) {
    // List all vendors
    // Check review dates
    // Return overdue vendors
  }
}

Integration with Other Tools

Combine Probo MCP with other tools:

• Jira: Create tickets for nonconformities
• Slack: Send compliance alerts
• Email: Automate compliance reports
• Monitoring: Track compliance metrics