Consent Checker MCP

Use the Consent Checker MCP server from Cursor, Claude Code, or another MCP client with the same API key you already use for the Consent Checker API.

What You Can Do

• Start a consent check
• List your recent runs
• Fetch run status
• Fetch the markdown report
• Fetch the raw session JSON
• Fetch screenshot metadata and browser-usable screenshot URLs
• Start summary generation
• Fetch summary or analysis status

Authentication

Your MCP client should send:

Authorization: Bearer <api_key>

The MCP server forwards that same Bearer token to the authenticated Consent Checker API.

That means:

• the API key determines which account is making the request
• you only see runs that belong to your account
• reports, sessions, screenshots, and summaries are scoped the same way

Deployed MCP Endpoint

Use the deployed MCP endpoint:

https://mcp.papayacomply.ai/

Cursor Config

Put this in .cursor/mcp.json:

{
  "mcpServers": {
    "consent-checker": {
      "url": "https://mcp.papayacomply.ai/",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Code Style Config

If your MCP client accepts a URL plus headers, use:

{
  "name": "consent-checker",
  "url": "https://mcp.papayacomply.ai/",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

Available Tools

• run_consent_check
• list_recent_runs
• get_run_status
• get_run_report
• get_run_session
• get_run_screenshots
• get_run_analysis
• start_run_analysis

Screenshot URLs

Screenshot responses include browser-usable image URLs.

That means a frontend or client can render them directly, for example:

<img src="https://..." alt="Consent checker screenshot">

The client does not need a Supabase API key as long as the returned URL is already public or pre-signed.

Good To Know

• MCP access uses the same API key as the authenticated API
• runs started through MCP still appear in the web app
• reports, screenshots, sessions, and summaries remain available in the GUI
• if your API key works against the API, it should work the same way through MCP