Use WideWired with an AI agent
Connect your agent to register an account, set up devices and manage networks through conversation. Complete top-ups on the website.
Connect the MCP server
In an agent host that supports Streamable HTTP MCP, add the endpoint for this site:
{"mcpServers":{"widewired":{"url":"https://www-api.widewired.com/mcp"}}}
The agent host must support keeping account credentials private and supplying authentication for subsequent calls.
Register or sign in through your agent
Ask the agent to register an account or sign in to an existing one. Register with an email address and password, then complete email verification. Complete two-factor authentication if enabled. See Signing up and signing in and Account.
Enter passwords and verification codes only through a trusted private input in your agent host. Do not publish credentials or complete sign-in responses in shared conversations. The account has the same permissions, device limits, rewards and billing rules as an account used in the console.
Ask for a task and check the result
Start with a concrete request, for example:
- “Create a network for my laptop and server, then guide me through connecting both devices.”
- “Show the devices awaiting approval and ask me before approving any.”
- “Check the link between these devices and explain its recent packet loss.”
- “Show this month's usage and my available credit.”
- “Find recent configuration changes and help me contact support.”
Review the selected network and affected devices before approving a change. Require confirmation before deletion or running installation commands. Installation requires permission on each device; an agent on a computer cannot grant VPN permissions on a phone.
After setup, ask the agent to confirm that the intended devices are approved and online, then test a real connection between them. Use Quickstart for the same verification steps in the console.
Add credit in the browser
Ask the agent for the recharge link and complete payment on the website. After payment, ask it to check the posted balance. MCP does not create purchases or start checkout. See Billing.
For client developers
The available tools are search_operations, describe_operation, call_operation and recharge. Search by user task, read the selected operation's fields and requirements, then call it with the user's decisions.
For direct integrations, read this site's operation directory and OpenAPI. HTTP clients supply the account access credential in Authorization: Bearer ... on each request or privately to call_operation. Implement the account human-verification challenge for registration, sign-in when required, and password reset; follow the operation description rather than asking the remote MCP service to solve it. Store authentication responses privately. Support attachment calls through MCP accept a base64 file up to 8 MiB.
Quick troubleshooting
| Symptom | Action |
|---|---|
| The host cannot authenticate later calls | Check that it supports private account credential storage and authenticated MCP calls |
| Cannot sign in after registration | Complete email verification and check the email address and password |
| An operation requires fresh authentication | Complete the requested password or authenticator check before retrying |
| A device is still pending | Verify the device identity and approve it, then check its connection |
| Credit did not change after payment | Check the browser purchase status and posted balance; do not duplicate the order |