MCP Sandbox#

The DIDWW MCP Sandbox is a testing environment for connecting an MCP client to DIDWW and trying requests before you use your production account.

Use the Sandbox to test the MCP connection, authorization, and supported workflows without affecting production data or incurring real charges.

Connection information#

Setting

Value

Connection name

DIDWW Sandbox

MCP server address

https://sandbox-api.didww.com/mcp

Connection type

Streamable HTTP with OAuth

Authorization

Sign in and approve the connection through the DIDWW Sandbox 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.

Note

Only use an MCP server address published by DIDWW.

Use the Sandbox to test the workflows you plan to use. Some workflows behave differently in the Sandbox. See Sandbox limitations.

For the production server address, see DIDWW MCP connection details.

Sandbox and production are separate environments. A Sandbox connection can access only Sandbox accounts and data, and a production connection can access only production accounts and data. Sandbox and production sign-in credentials are not interchangeable.

Warning

Check the server address before you authorize the connection. A connection to https://api.didww.com/mcp uses your production account, where orders and configuration changes are real.

Connect to the Sandbox#

  1. Create a Sandbox account, or sign in to an existing one. For detailed registration instructions, see the DIDWW account registration guide.

  2. In your MCP client, add a connection with the server address https://sandbox-api.didww.com/mcp. Follow the guide for your client, and replace the production server address with the Sandbox address. See Connect Claude, Connect ChatGPT, or Connect Perplexity.

  3. Name the connection DIDWW Sandbox if your client allows it, so that you can tell it apart from a production connection.

  4. When the DIDWW Sandbox authorization page opens in a browser, sign in with your Sandbox User Panel credentials and approve the connection.

To confirm the connection, ask the MCP client to show the active DIDWW account.

Add funds to a Sandbox account#

Funds are needed only to test paid actions, such as buying numbers or capacity. Connecting an MCP client and making read-only requests do not require funds.

  1. Contact DIDWW Support at support@didww.com to verify your Sandbox account for the first payment. Funds cannot be added until the account is verified.

  2. After the account is verified, add a payment card to the Sandbox account using any suitable Stripe test card.

  3. Use the Add Funds flow in the Sandbox User Panel.

Important

Do not use real payment-card information in the Sandbox. Sandbox payment cards and balances have no monetary value and do not affect production.

Sandbox limitations#

  • Sandbox data is separate from production data.

  • Production accounts cannot be used in the Sandbox, and Sandbox accounts cannot be used in production.

  • Identity verification is unavailable in the Sandbox.

  • Telephone numbers and other Sandbox resources are test resources.

  • Some external provider or carrier behavior may not be reproduced completely.