> ## Documentation Index
> Fetch the complete documentation index at: https://docs.proofage.net/llms.txt
> Use this file to discover all available pages before exploring further.

# ProofAge MCP server

> Connect Claude, Cursor, VS Code or any MCP client to your ProofAge account.

The ProofAge MCP server lets an AI assistant work with your ProofAge account the way your team does in the console: integrate ProofAge into an app, look into a verification, send a verification link, block a face, replay a webhook, or erase a person's data on request.

```
https://app.proofage.net/mcp/admin
```

## What it can do

<CardGroup cols={2}>
  <Card title="Integrate" icon="screwdriver-wrench">
    Create a test workspace, read its keys and URLs, create verifications, set test outcomes and replay webhooks against a local handler. Then create the live workspace.
  </Card>

  <Card title="Investigate" icon="magnifying-glass">
    Look up verifications, their decision and reason, images, webhook deliveries and statistics, with the same data as the console.
  </Card>

  <Card title="Support" icon="headset">
    Send a verification link, block or unblock a face, erase a person's data on request.
  </Card>

  <Card title="Read the docs" icon="book">
    The developer documentation and the OpenAPI spec are served as MCP resources, so the assistant writes code against the real API.
  </Card>
</CardGroup>

The full list is on [MCP tools reference](/integration/mcp/tools).

## Connect

The server uses OAuth: your MCP client opens a browser window where you sign in with your ProofAge console account and approve access. There are no API keys to paste.

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http proofage https://app.proofage.net/mcp/admin
    ```

    Then run `/mcp` in Claude Code and choose **proofage** to sign in.
  </Tab>

  <Tab title="Claude.ai">
    In **Settings → Connectors**, add a custom connector with the URL `https://app.proofage.net/mcp/admin`, then connect it and sign in.
  </Tab>

  <Tab title="Cursor">
    In `~/.cursor/mcp.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "proofage": { "url": "https://app.proofage.net/mcp/admin" }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    In `.vscode/mcp.json`:

    ```json theme={null}
    {
      "servers": {
        "proofage": { "type": "http", "url": "https://app.proofage.net/mcp/admin" }
      }
    }
    ```
  </Tab>

  <Tab title="Other clients">
    Any client that supports remote MCP servers over HTTP with OAuth works: point it at `https://app.proofage.net/mcp/admin`. The server supports OAuth discovery and dynamic client registration.
  </Tab>
</Tabs>

## Who you are on the server

The assistant acts as you, in the account you are working in in the console, and sees the tools your role allows:

| Role | Tools |
| - | - |
| Administrator | All tools. |
| Developer | Everything except erasing personal data and correcting document fields. |
| Support specialist | Verifications and statistics, verification links, the blocklist, the list of workspaces and webhook deliveries, correcting document fields, and erasing personal data. Not creating or changing workspaces, keys, webhook retries or test outcomes. |

Every action is recorded under your name, as it is in the console.

## Safety

* **Destructive actions take two steps.** Blocking or unblocking a face and erasing personal data first return a preview and a short-lived token; the assistant must then confirm with an exact phrase and a reason.
* **Live workspaces are protected.** Changing a live workspace or its keys only returns a preview; nothing is applied until you confirm. Live secret keys are never returned: you copy them from the console.
* **Creation is rate-limited per user**: verifications, workspaces, test outcomes and erasures.

To remove access, disconnect the server in your MCP client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.