DevX Viral API and MCP

In the dashboard, under Settings → API keys, give it a name and pick a role. The key is shown only once: copy and store it. It starts with dvx_.

The server is at https://api.devxviral.com/mcp, over HTTP transport. In Claude Code:

claude mcp add --transport http devxviral https://api.devxviral.com/mcp \
  --header "Authorization: Bearer dvx_YOUR_KEY"

In Cursor (or any client that accepts a server by URL):

{
  "mcpServers": {
    "devxviral": {
      "url": "https://api.devxviral.com/mcp",
      "headers": { "Authorization": "Bearer dvx_YOUR_KEY" }
    }
  }
}

The dashboard shows these commands ready, with your key, for Claude Desktop too.

Routes live at https://api.devxviral.com/api/… and accept the same key in the header. The key acts as its creator, in their workspace, with the chosen role.

curl https://api.devxviral.com/api/accounts \
  -H "Authorization: Bearer dvx_YOUR_KEY"

Billing and referrals are read-only with a key; keys and administration don't accept any key.

Some processing-heavy tools (view frame, export, transcribe, search references, upload and import) also have a daily cap per workspace.

• admin Everything: view, post, videos, accounts, members and settings.
• editor View, post, and work on videos and accounts. No settings or billing.
• analista Read only.

A key never has a role above its creator's.

• 401 unauthorized The Authorization header is missing, or the key was revoked.
• 402 feature_not_in_plan The plan doesn't include the API, or the action writes and the plan is read-only.
• 403 forbidden The key's role can't perform this action.
• 429 rate_limited Too many calls per minute. Wait the time in the Retry-After header.