Connect your tools to your privacy workflow

Connect an AI client

1. In a client that supports remote MCP and OAuth, add https://app.privacyrequests.co/mcp as a Streamable HTTP server.
2. Sign in to Privacy Requests, including two-factor authentication when enabled.
3. Review the client identity, select your workspace and choose the permissions it needs. Write access, workspace configuration and final workflow actions are separate choices and default off.
4. Allow the connection. Start by asking the client to find a case and explain its current workflow blockers.

Read access can share accessible case details, requester wording, internal notes, tasks, response drafts and settings with your chosen AI client. Review that client's data-handling terms before connecting. Manage and revoke connections in Settings → AI connections.

Choose the access you need

• mcp:read: read accessible cases, tasks, settings and product guidance.
• mcp:write: prepare case work, including notes, tasks and response drafts.
• mcp:configure: change eligible workspace settings.
• mcp:finalize: perform eligible final workflow actions after explicit confirmation.

Permissions do not expand your workspace role. The client must show you the action, saved contents, recipient and consequences before requesting confirmation for a final action. Identity checks, reviewer approvals and delivery requirements still apply. An AI client cannot complete requester verification or another person's approval on their behalf.

Available tools are discovered after authentication. Client compatibility varies; use a client that supports the advertised protocol and OAuth flow.

Build with the client API

The REST API uses scoped bearer tokens created in the app. These are separate from MCP OAuth connections. The client API reference includes token setup, request examples and the OpenAPI description.

Resources for agents and developers

• MCP server card: connection metadata using the evolving server-card format.
• Agent skills index and Privacy Requests workflow skill: setup and safe workflow guidance.
• API catalog: supported integration descriptions and documentation.
• OAuth resource metadata and authorization server metadata.

Public pages also support Markdown requests with Accept: text/markdown. These resources contain public product guidance only; customer cases and files require an authorized app connection.