# DIDWW MCP connection details

Use the following details to connect an MCP client to DIDWW.

## Connection information

| Setting | Value |
| --- | --- |
| Connection name | **DIDWW** |
| MCP server address | `https://api.didww.com/mcp` |
| Connection type | **Streamable HTTP with OAuth** |
| Authorization | Sign in and approve the connection through the DIDWW authorization page. |
| API key | Not required. |
| Client credentials | Not required. |

The MCP client registers automatically during the first connection. A client ID
and client secret are not required.

To test the connection without using your production account, connect to the
DIDWW MCP Sandbox. See [MCP Sandbox](sandbox.html).

Note

Only use an MCP server address published by DIDWW.

## Supported MCP clients

| Client | Availability |
| --- | --- |
| [Claude](how-to-guides/claude.html) | Supported in the Claude web application (`claude.ai`) and Claude Desktop. |
| [ChatGPT](how-to-guides/chatgpt.html) | Supported. |
| [Perplexity](how-to-guides/perplexity.html) | Supported on plans that allow custom connectors. A custom connector can be added only in the Perplexity web application. |
| Other remote MCP clients | May connect when they support Streamable HTTP with OAuth. Enter the DIDWW MCP server address and complete authorization in the browser. |

Availability may depend on the MCP client, plan, platform, and support for
remote OAuth-protected MCP servers. A client that cannot connect directly to a
remote MCP server requires a local MCP bridge.

## Authorization

After the MCP client connects to the server address, the DIDWW authorization
page opens in a browser. Sign in with the DIDWW User Panel credentials,
complete two-factor authentication when required, and approve the connection.

Warning

Enter your DIDWW password only on a DIDWW sign-in page. Do not provide your
password, API key, or two-factor authentication code in an MCP client
conversation.

## Account access

The connection is associated with the DIDWW user who authorizes it. The MCP
client can access only:

- DIDWW accounts available to that user
- information permitted by the user's existing access
- actions permitted by the user's existing roles

The active account determines which information, services, and actions are
available to the MCP client.

## Multiple accounts

If your DIDWW login can access more than one account, the following account
actions are always available regardless of your role:

| Action | Purpose |
| --- | --- |
| List accounts | Shows the DIDWW accounts available to your login. |
| Review the active account | Shows which DIDWW account the MCP client is currently using. |
| Switch accounts | Selects another accessible account for subsequent DIDWW requests in the current conversation. |

Permissions are evaluated separately for each DIDWW account. Switching
accounts can therefore change the information and actions available to the MCP
client.

Switching accounts does not grant new roles or permissions. The connection
uses the roles assigned to your user for the selected account.

To select the required account, you can ask the MCP client to:

1. Show the DIDWW accounts available to your user.
2. Switch to the account you want to use.
3. Confirm the active account before reviewing information or making changes.

For example:

```
Show the DIDWW accounts available to me.
Do not switch accounts yet.
```

After selecting the required account:

```
Switch to the DIDWW account named Example Account.
Confirm the active account before making any other changes.
```

## Manage the connection

To review connected MCP clients in the DIDWW User Panel:

1. Open the account switcher in the upper-right corner.
2. Select **Account Settings**.
3. Select the **MCP Clients** tab.

To disconnect an MCP client, select **Revoke** for the relevant client, or
select **Revoke all** to disconnect every listed client.

A connection that remains unused for 30 days requires DIDWW authorization
again the next time it is used. Follow the browser authorization process to
reconnect the MCP client.

Note

A revoked connection cannot be restored. To use the MCP client again, select
or add the DIDWW connection in the client and complete the DIDWW authorization
process again.

## Privacy and security

Information returned through DIDWW MCP is also processed by the connected AI
provider under its terms and privacy policy.

See [Privacy and data handling](privacy-and-data-handling.html) for details.
For information about how DIDWW processes personal data, see the [DIDWW
Privacy Notice](https://www.didww.com/privacy-notice).

On this page