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

# Connect AI Assistants to Your Account

> Connect Claude or Claude Code to your iDenfy dashboard account over MCP, choose which data areas it can view or edit, and disconnect it at any time.

You can connect Claude or Claude Code to your iDenfy account through the iDenfy account MCP server. Once it is connected, you can ask the assistant about your balance, webhook activity, verification statistics and settings, and it answers from your own account data.

<Info>
  Server URL: `https://mcp.idenfy.com/mcp`
</Info>

<Note>
  This is a different server from the [documentation MCP server](/resources/mcp). The documentation server only searches these docs. The account MCP server works with your dashboard account, within the data areas you grant it.
</Note>

***

## Before You Start

* The MCP server must be enabled for your company account, and your role must include the **Use MCP server** permission. Without both, the connection is refused. If your role does not have the permission, ask an Admin on your account. To have the server enabled for your company, contact [techsupport](https://idenfy-ivs.atlassian.net/servicedesk/customer/portal/1).
* Your manager account must belong to a single company. A manager with access to several companies cannot connect.
* If you sign in to the dashboard with single sign-on (SSO), iDenfy must first enable AI assistant connections on your SSO connection. Contact [techsupport](https://idenfy-ivs.atlassian.net/servicedesk/customer/portal/1) to request it.
* The assistant can only do what you can do yourself. It works through your manager account, and your own permissions are checked on every request. If you lose a permission after connecting, the assistant loses access to that data too.

***

## What the Assistant Can Access

The assistant never receives personal data about your end users. Every answer is built from a fixed list of non-personal fields, so names, document numbers, photos and similar data cannot be returned.

| Data area | What the assistant can see | Can it edit? |
| - | - | - |
| **Finances** | Balance, unit limits, remaining units, expiry date and funds | No |
| **Webhooks** | Configured webhooks, sent webhooks, their delivery statuses and the response from your server. Webhook payloads are never read | No |
| **Settings** | The identity verification (KYC), business verification (KYB) and AML settings shown in the dashboard | Yes, with Edit access |
| **Identity verification** | Statistics for a chosen period, filterable by country and document type, and the process details of a single verification looked up by scan reference. AML outcomes are reduced to a status and the types of flags found | No |
| **AML** | Check statistics and monitoring counts | No |
| **Business verification (KYB)** | Statistics, verified companies, flows, automation rules and questionnaires | Automation rules only, with Edit access |

Settings outside these areas, such as team members, API keys, plan and company details, are not available to the assistant.

### What Edit Access Allows

* **KYB automation rules.** The assistant can create an [automation rule](/guides/dashboard/risk/custom-rules), but it is created unassigned. It has no effect on any verification until you assign it to a flow in the dashboard. The assistant cannot create or edit flows or questionnaires.
* **Settings.** A settings change made by the assistant **takes effect on live verifications immediately**, exactly as if you had changed it in the dashboard. Grant Edit on settings only if you want the assistant to make those changes.

### Available Tools

You do not call these tools yourself. The assistant picks the right one for your question. If a tool needs a data area you did not grant, the assistant tells you to reconnect with that access.

| Tool | Access needed | What it does |
| - | - | - |
| `get_finances` | Finances · View | Returns your balance, expiry date and the unit allowance per service |
| `list_webhooks` | Webhooks · View | Lists the endpoints your account sends events to |
| `list_webhook_deliveries` | Webhooks · View | Lists recent deliveries, newest first, with the response from each receiving server |
| `get_settings` | Settings · View | Returns every configured KYC, KYB and AML setting |
| `describe_settings` | Settings · View | Returns the name, meaning, type and allowed values of each setting |
| `update_setting` | Settings · Edit | Changes one setting |
| `get_kyc_statistics` | Identity verification · View | Returns the approved share of KYC verifications over a period |
| `get_kyc_verification` | Identity verification · View | Returns one verification, looked up by scan reference |
| `get_aml_check_statistics` | AML · View | Returns how many AML screenings ran over a period, and how many raised a flag |
| `get_aml_monitoring_statistics` | AML · View | Returns how ongoing AML monitoring went over a period |
| `get_kyb_statistics` | KYB · View | Returns approved, denied and pending companies over a period |
| `list_kyb_companies` | KYB · View | Lists the companies your account verified |
| `list_kyb_flows` | KYB · View | Lists your configured KYB flows |
| `list_kyb_automation_rules` | KYB · View | Lists your configured automation rules |
| `list_kyb_questionnaires` | KYB · View | Lists the questionnaires shown to companies being verified |
| `create_kyb_automation_rule` | KYB · Edit | Creates one automation rule, unassigned |

***

## Connecting an Assistant

The account MCP server uses OAuth sign-in with your iDenfy dashboard login. Each AI client has its own client ID. There is no client secret, so leave the secret field blank wherever your client asks for one.

| Client | Client ID |
| - | - |
| Claude (claude.ai) | `qFxLIWx0WYQFBQR98ouk8TAVvNcPsXQj` |
| Claude Code | `b0HmgH86PmxvgKl7KOCuj6oY9EYw7qBV` |

Claude and Claude Code are supported today. Setup for ChatGPT, VS Code, Gemini CLI and Cursor is still being prepared and will be added here.

### Claude

<Note>
  On Claude Team and Enterprise plans, only an organization **Owner** can add the connector. Once it is added, each member connects it separately with their own iDenfy login.
</Note>

<Tabs>
  <Tab title="Team and Enterprise">
    1. As an Owner, go to **Organization settings → Connectors → Add → Custom → Web**.
    2. Enter a name, such as `iDenfy`, and the server URL `https://mcp.idenfy.com/mcp`.
    3. Choose **Use your own OAuth client**, paste the client ID `qFxLIWx0WYQFBQR98ouk8TAVvNcPsXQj`, and leave the secret blank.
    4. Save the connector. Each member then connects it and signs in with their own iDenfy login, as described in [Signing In and Choosing Access](#signing-in-and-choosing-access).
  </Tab>

  <Tab title="Pro and Max">
    1. Go to **Customize → Connectors**, click **+** and choose **Add custom connector**.
    2. Enter a name, such as `iDenfy`, and the server URL `https://mcp.idenfy.com/mcp`.
    3. Choose **Use your own OAuth client**, paste the client ID `qFxLIWx0WYQFBQR98ouk8TAVvNcPsXQj`, and leave the secret blank.
    4. Save the connector, connect it and sign in, as described in [Signing In and Choosing Access](#signing-in-and-choosing-access).
  </Tab>
</Tabs>

### Claude Code

Requires Claude Code 2.1.237 or later. Run:

```bash theme={"system"}
claude mcp add --transport http --scope user iDenfy https://mcp.idenfy.com/mcp --client-id b0HmgH86PmxvgKl7KOCuj6oY9EYw7qBV --callback-port 51789
```

* `--scope user` makes the server available in every project, not only the current one.
* `--client-id` and `--callback-port` are both required. Without `--client-id`, the connection fails.

Then run `/mcp` in Claude Code, select **iDenfy** and sign in.

<Warning>
  Port 51789 must be free on your computer. If another process is using it, the sign-in fails straight away and no browser page opens. There is no fallback port, so close the process that holds the port and try again.
</Warning>

### Signing In and Choosing Access

When the assistant asks you to sign in, iDenfy opens its own sign-in and consent screens:

1. **Sign in** with your iDenfy dashboard credentials. If your account uses two-factor authentication, you are asked for the code straight after your password. The login screen always appears, even if you are already signed in to the dashboard.
2. **Choose an account.** If your login is linked to more than one manager account, choose which one to connect. With a single account, this step is skipped.
3. **Choose what the assistant can reach.** The screen names the assistant that is asking for access and lists the data areas your role can use. Each area has separate **View** and **Edit** options, and View never grants Edit. Edit is offered only where your role can make changes.
4. Click **Allow** to continue with the access you selected, or **Cancel** to decline.
5. **Confirm the authorization.** A final authorization screen asks you to confirm the connection. Accept it to finish connecting.

You can also allow the connection with nothing selected. The assistant is then connected, but it cannot reach any of your data.

Each sign-in connects one account. To connect a second company through the same assistant, sign out of the iDenfy connection in the assistant and connect again.

<Note>
  Connections do not check your account's IP whitelist, because a hosted assistant connects from its provider's servers rather than from your network. If a connection comes from an IP address that iDenfy has not seen for your login before, the usual new IP login email is still sent as a notice.
</Note>

***

## Managing Connected Assistants

To see which assistants are connected, go to **Settings → Company details** and open the **Connected apps** tab. It lists the assistants connected to your manager account. Each one shows the date it was connected and the access it holds.

To disconnect one, click **Disconnect**, check the access it will lose, and confirm. The assistant loses access straight away. Disconnecting ends every connection you made through that assistant at once. It removes future access only, so anything the assistant already did, such as a rule it created, stays in place.

### Connection Lifetime

A connection ends after 7 days without use. It also has a maximum lifetime, however often it is used. When a connection ends, sign in again from the assistant.

Logging out of the dashboard does **not** disconnect your assistants. Apart from expiring, a connection ends only when you disconnect it from **Connected apps**, when your password or two-factor authentication is reset, or when your account is deactivated.


## Related topics

- [Company Details](/guides/dashboard/settings/company-details.md)
- [Model Context Protocol (MCP)](/resources/mcp.md)
- [AI Reviewer](/guides/dashboard/settings/ai-reviewer.md)
- [Zapier Integration](/integrations/zapier.md)
- [Reports and Documents Tab](/guides/dashboard/general/reports-documents-tab.md)


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