Skip to main content

Troubleshooting Guide

Common issues with the Hyperstack API MCP Server, and how to resolve them.

This guide outlines common issues when you connect an AI client to the Hyperstack API MCP Server at https://console.hyperstack.cloud/ai/mcp. Each section provides structured diagnostic procedures and verified resolutions.

Important: Live Infrastructure Changes & Data Loss Risk

This MCP server can create, modify, and delete real Hyperstack resources, which may incur charges on your account. Always review actions before confirming them. NexGen Cloud is not liable for any unintended resource usage, costs, or data loss resulting from the use of this tool. Use it at your own risk.

Sign-In Issues​

Use the guidance below when your client cannot add the server, sign in, or stay signed in.

Your Client Cannot Add the Server​

The MCP Server accepts connections from clients whose redirect address it recognizes, which covers clients running on your own machine, Claude on the web, and Open WebUI's hosted service.

If your client is rejected when it registers, it is reachable at an address the server does not recognize. Connect from one of the clients listed above instead.

Sign-In Does Not Complete​

If the browser opens the Hyperstack sign-in page but your client never reports a connection, the sign-in was not returned to the client.

  1. Complete the Sign-In in the Same Browser Session​

    Finish the sign-in in the browser window your client opened, rather than copying the address into another browser or profile.

  2. Retry the Connection​

    Remove the server from your client and add it again. Each attempt starts a new sign-in, and an abandoned attempt expires on its own.

Tool Calls Fail After Working Earlier​

Your session credentials expire, and your client renews them automatically. A tool call that fails after a period of inactivity usually means the renewal did not complete.

  • Error: Refresh temporarily unavailable, please retry

    Another renewal for the same session is already running. Run the request again.

  • A failure that persists across retries means the session can no longer be renewed. Remove the server from your client, add it again, and sign in.

Claude Desktop Issues​

The following check helps resolve connection problems between Claude Desktop and the MCP Server.

MCP Server Not Connected​

Claude Desktop shows no MCP tools, or reports that the server is unavailable.

Open Settings → Connectors and find the connector you added. Check that its Remote MCP server URL is https://console.hyperstack.cloud/ai/mcp. If the connector does not show as connected, click Connect and complete the sign-in in the browser window that opens.

For the full procedure, see Connect to the MCP Server in the Claude Desktop Setup Guide.

API Errors​

The following errors are returned directly by the Hyperstack API.

Rate Limit Exceeded​

A 429 response indicates that too many requests were sent in a short period of time.

Error: Rate limit exceeded (429)

  1. Wait Before Retrying​

    Wait approximately 60 seconds before retrying your request so the rate limit window can reset.

Request Timeout​

Timeout errors occur when a request takes longer than the allowed processing time.

Error: Request timeout

  1. Reduce Request Size​

    Break large requests into smaller operations to reduce processing time.

  2. Retry the Request​

    Wait briefly before attempting the request again.

On this page