Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Claude Desktop reads its MCP server list from a JSON config file. Add a single entry pointing at https://mcp.scaling.cloud and Claude will guide you through the OAuth flow on first use.

​
Server URL

https://mcp.scaling.cloud

​
Locate your config file

PlatformPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
If the file doesn’t exist, create it.

​
Add the Scaling entry

Open the file and add (or extend) the mcpServers block: 
{
  "mcpServers": {
    "scaling": {
      "url": "https://mcp.scaling.cloud"
    }
  }
}
Save and restart Claude Desktop.

​
Sign in

The first time Claude Desktop talks to the Scaling MCP server, it opens your default browser, redirects you to Clerk’s hosted OAuth consent screen, and asks you to approve the requested scopes. Approve, and control returns to Claude Desktop.

​
Verify it’s working

Open Settings → Connections in the Scaling dashboard. You should see a row for Claude Desktop (or whatever name Claude Desktop self-registered as) with a recent Last used timestamp.

​
Revoke access

Click Revoke in Settings → Connections in the Scaling dashboard. Subsequent Claude Desktop calls will return 401 until you reconnect.

​
Troubleshooting

  • “Failed to connect” — make sure your machine can reach https://mcp.scaling.cloud. The endpoint is publicly accessible; check corporate proxies and DNS.
  • OAuth window doesn’t open — confirm Claude Desktop has permission to open external URLs and that no firewall is blocking the localhost callback port Claude Desktop chose.
  • Connection works but tools fail with 401 — your Clerk session may have expired. Quit Claude Desktop, restart it, and complete the OAuth flow again. (This re-issue happens transparently for refreshable tokens but not always for first-party desktop apps.)