# Overview

DIDWW MCP connects compatible MCP clients to your DIDWW account. It lets
you use natural-language requests to review account information and complete
supported DIDWW tasks while retaining your existing account permissions and
confirmation requirements.

## What is DIDWW MCP?

[Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) is an open
standard that allows an MCP client to request information or actions from a
connected service. DIDWW MCP provides this connection for supported areas of
your DIDWW account.

You can ask the MCP client for an outcome instead of navigating each
account area manually. For example, you can ask it to find an available number,
review routing information, check your balance, or prepare an export. The MCP
client interprets your request and uses only the DIDWW actions available
to the connected user.

Note

DIDWW MCP is intended for customer account use. It does not replace the DIDWW
API for building custom software integrations.

## How the connection works

The connection uses OAuth authorization. After you add or select DIDWW in a
compatible MCP client, your browser opens the DIDWW authorization page. Sign in
to the DIDWW User Panel and review the connection request.

After you approve the connection:

- the MCP client acts as the DIDWW user who approved it
- your User Panel roles determine which information and actions are available
- the connection can access only accounts available to that user
- you can switch between accessible accounts
- the connection appears under **Account Settings** > **MCP Clients**

Your DIDWW password, API key, and two-factor authentication code are not
entered in the MCP client conversation.

See [Connection details](connection-details.html) for the connection type,
server address, and authorization requirements.

## What you can do

DIDWW MCP supports the following service areas. Available actions depend on
the active account, assigned roles, enabled services, and service availability.

See [Available tools](available-tools.html) for exact tool names, access
types, and DIDWW confirmation requirements.

| Service area | Available actions |
| --- | --- |
| [Accounts](connection-details.html#mcp-multiple-accounts) | List accessible DIDWW accounts, review the active account, and switch the active account. |
| [Phone numbers](work-with-didww-mcp/phone-numbers.html) | Search coverage, review pricing, purchase DID numbers, manage supported settings and renewals, terminate numbers, and restore terminated numbers. |
| [Inbound routing](work-with-didww-mcp/inbound-routing.html) | Create and manage SIP, PSTN, and phone.systems(TM) trunks, assign DID numbers, configure number lists, and use trunk groups for failover or load balancing. |
| [Messaging](work-with-didww-mcp/messaging.html) | Create and manage inbound SMS trunks and groups, assign supported DID numbers, and configure incoming SMS routing to an HTTP endpoint or email address. |
| [Capacity](work-with-didww-mcp/voice-capacity.html) | Review supported capacity, purchase channels, assign channels, and manage capacity groups. |
| [Billing and payments](work-with-didww-mcp/billing-and-payments.html) | Review balances, invoices, orders, payments, refunds, and masked saved-card information. Billing information is read-only. |
| [Exports](work-with-didww-mcp/data-exports.html) | Prepare and download supported call-record, SMS-log, DID-number, order, and payment exports. |
| [Compliance and verification](work-with-didww-mcp/compliance-and-verification.html) | Review registration requirements, manage identities and addresses, upload documents securely, and review or submit supported verifications. |
| [Emergency calling](work-with-didww-mcp/emergency-calling.html) | Review requirements and pricing, create supported services, and submit or resubmit emergency verifications. |
| [Users and invitations](work-with-didww-mcp/users-and-invitations.html) | Review users, roles, and pending invitations, create invitations, and cancel pending invitations. |

Note

Use the DIDWW User Panel when an action is not available through MCP. See
[Troubleshooting](troubleshooting.html#mcp-troubleshooting) for help resolving access and
availability problems.

## Permissions and account access

DIDWW MCP uses the roles and permissions assigned to your DIDWW user.
Connecting an MCP client does not grant additional access or bypass
existing account controls.

If you have access to multiple DIDWW accounts, the connection uses one active
account at a time. Changing the active account also changes the records and
actions available to the MCP client.

An action may be unavailable when:

- your user role does not include the required permission
- the service or product is not enabled for the active account
- the requested record belongs to another account
- an account limit or service requirement prevents the action

Note

Account owners and administrators can review user roles and manage account
access in the DIDWW User Panel. See [Users and roles](../account-settings/adding-new-roles.html).

## Money, confirmations, and safety

DIDWW MCP distinguishes between immediate purchases, usage-based services, and
account changes that do not create a charge. Protected actions use a two-step
confirmation process so that you can review the result before DIDWW applies it.

### Actions that purchase a service

The following actions purchase DIDWW telecommunications services using funds
already available in the active account's prepaid balance. Funds must be added
separately through the DIDWW User Panel.

| Action | Purchase preview |
| --- | --- |
| Purchase phone numbers | Shows the selected phone numbers or requested quantity, availability, one-time setup charges, recurring charges, and included capacity. It also identifies numbers that will be supplied later when they are not immediately available. |
| Purchase additional flat-rate channels | Shows the selected capacity pool, number of channels, applicable price, renewal information, and active DIDWW account. |

Review the purchase preview carefully. DIDWW completes the purchase from the
prepaid balance only after you confirm it.

Note

DIDWW MCP cannot charge a saved payment card, add funds to the account, or
manage saved payment methods. If the balance is insufficient, add funds in
the DIDWW User Panel and request a new purchase preview.

### Usage-based PSTN trunks

A PSTN trunk forwards incoming calls from a DID number to a telephone number.
Creating the trunk does not charge your account.

Before creating a PSTN trunk, DIDWW shows the per-minute forwarding rate or
rate range for the selected destination. You must confirm this rate before
DIDWW creates the trunk. Confirming the rate does not generate a charge.

Usage charges begin only when an incoming call is forwarded through the PSTN
trunk. If the trunk does not forward a call, no per-minute forwarding charge
is generated.

Changing the PSTN destination also requires confirmation of the rate for the
new destination. If DIDWW cannot determine a rate, the trunk is not created or
updated.

### Capacity assignments

Assigning purchased flat-rate channels as dedicated or shared capacity does not
purchase more channels. Creating a capacity group also does not purchase
capacity.

Metered channels provide pay-per-minute capacity through a capacity group.
Usage charges apply only when an incoming call uses a metered channel.

See [Capacity](work-with-didww-mcp/voice-capacity.html) for capacity
types, assignments, priority, and example requests.

### Protected actions

DIDWW uses two-step confirmation for supported purchases, usage-rate
acceptance, destructive actions, user invitations, and other significant
account changes.

The first request presents a preview and does not change the account. Review
the active account, affected resources, prices, recurring charges, usage
rates, and consequences before confirming.

See [Available tools](available-tools.html) for the complete list of actions
and their DIDWW confirmation requirements.

### How two-step confirmation works

A protected action follows this sequence:

1. You explicitly request the action.
2. DIDWW prepares a preview of what will be purchased, created, changed,
   restored, terminated, or removed. Nothing has changed yet.
3. The MCP client presents the preview and waits for your decision.
4. You review the active account, affected resources, prices, recurring
   charges, usage rates, and consequences.
5. You confirm or reject the action.
6. After confirmation, DIDWW completes the action and returns the result.

A confirmation applies only to the action described in its preview. If a
protected value changes, such as the selected resource, quantity, destination,
price, or rate, DIDWW requires a new preview and confirmation.

A confirmation can be applied only once. Reusing the same confirmation does
not repeat the purchase, deletion, or other protected action.

If the connection is interrupted after confirmation, DIDWW returns the stored
result when the same confirmation is received again. Before starting a new
request, ask the MCP client to check the relevant account records to
confirm whether the action completed.

If a confirmation expires, the MCP client checks the relevant phone
numbers, orders, payments, services, or other records before preparing another
preview.

Note

An MCP client can display its own tool-approval request before contacting
DIDWW. The MCP client approval is separate from the DIDWW preview and
confirmation.

### Read-only requests

DIDWW MCP uses read-only actions when you ask only for information. It does not
purchase, create, update, assign, restore, terminate, or delete a resource
unless you explicitly request that action in the current conversation.

For example:

- finding phone numbers does not purchase them
- reviewing capacity does not purchase channels
- reviewing a PSTN rate does not create a trunk
- reviewing an identity or address does not submit a verification
- reviewing a resource does not delete it

When another account change is required to complete a request, the MCP client
explains the required change and waits for your instruction.

DIDWW MCP does not schedule actions, create timers, or perform recurring
account changes later.

Warning

MCP clients can make mistakes. Before confirming an action, verify the
active DIDWW account, phone numbers, quantities, destinations, prices, usage
rates, recurring charges, and affected resources.

## Privacy and data handling

Learn what DIDWW account information can be shared through an MCP client, how
protected information and documents are handled, and how to review or revoke
connected clients.

See [Privacy and data handling](privacy-and-data-handling.html).

## Request and account limits

- Requests are measured separately for each connected client. When the request
  rate is exceeded, DIDWW returns the number of seconds to wait.
- Access tokens expire after two hours. The MCP client refreshes them
  automatically while the connection remains valid.
- An MCP client can cache available actions for up to one hour.
- List requests are paginated. The default and maximum page size depend on the
  requested information, and every list response reports the page size that was
  applied.
- One bulk phone-number assignment can include up to 100 numbers.
- DIDWW account quotas continue to apply to trunks, groups, messaging
  resources, capacity groups, and other account resources.

Note

Use filters or supported data exports for large datasets. When an account quota
is reached, remove an unused resource or contact DIDWW Customer Support.

## Supported MCP clients

DIDWW provides connection guides for Claude, ChatGPT, and Perplexity. Other
compatible remote MCP clients may also connect.

See [Connection details](connection-details.html) for supported clients,
platforms, and connection requirements.

## Troubleshooting

Resolve common connection, authorization, account, upload, export, and
request-limit issues.

See [Troubleshooting DIDWW MCP](troubleshooting.html).

On this page