Skip to main content

Hyperstack Docs MCP Server

Connect MCP-compatible AI tools directly to the Hyperstack documentation for grounded answers with citation links.

The Hyperstack Docs MCP Server connects MCP-compatible AI tools directly to the Hyperstack documentation. When you ask a question in your AI client, the server searches the docs and returns grounded answers with links back to the source pages, so responses reflect the current documentation instead of a model's training data.

The server is read-only. It retrieves and cites documentation only. It cannot create, change, or delete any Hyperstack resource.

Two Hyperstack MCP Servers

Hyperstack offers two separate MCP servers for two different jobs:

  • Docs MCP Server (this page) answers questions from the documentation and returns citation links. It is read-only, hosted by Hyperstack, and needs no API key.
  • Hyperstack API MCP Server creates and manages real resources (Virtual Machines, clusters, volumes, billing) through the Hyperstack API. You run it yourself and it requires a Hyperstack API key.

Use the Docs MCP Server to learn and look things up. Use the API MCP Server to take action on your infrastructure.

Capabilities

With the Docs MCP Server connected, your AI client can:

  • Answer Hyperstack questions from the docs, with a link to each source page.
  • Retrieve a full documentation page when it needs complete parameter tables or code examples.
  • Browse the documentation structure by product area (Virtual Machines, Kubernetes, storage, networking, billing, AI Studio, hardware).
  • Explain a Hyperstack API error by status code, error reason, or message text, and point to the fix.
  • Look up GPU flavor specifications when comparing hardware or planning a deployment.

Because the server reads from the live documentation index, answers stay current with the published docs.

Connect to the server

The Docs MCP Server is hosted by Hyperstack over Streamable HTTP. There is nothing to install or run, and no API key is required.

Server URL:

https://docs.hyperstack.cloud/mcp

You can also open the server URL in a web browser. It shows a human-readable overview of the server, with links to the connection instructions and the available tools.

Add the server using the instructions for your client below.

Claude Code

Run the following command:

Add the Docs MCP Server to Claude Code
claude mcp add --transport http hyperstack-docs https://docs.hyperstack.cloud/mcp

Cursor

Add the server to your ~/.cursor/mcp.json file (or a project-level .cursor/mcp.json):

~/.cursor/mcp.json
{
"mcpServers": {
"hyperstack-docs": {
"url": "https://docs.hyperstack.cloud/mcp"
}
}
}

Claude Desktop

Add the Docs MCP Server as a custom connector:

  1. Navigate to Settings.
  2. Under Customize, click Connectors.
  3. Click Add, then click Add custom connector.
  4. Enter a Name for the server, such as Hyperstack Docs.
  5. Enter https://docs.hyperstack.cloud/mcp as the URL.
  6. Click Add.

The server requires no authentication, so leave Advanced settings empty.

You can also connect through mcp-remote instead. Add the following to your claude_desktop_config.json, then restart Claude Desktop:

claude_desktop_config.json
{
"mcpServers": {
"hyperstack-docs": {
"command": "npx",
"args": ["mcp-remote", "https://docs.hyperstack.cloud/mcp"]
}
}
}
note

For any other MCP-compatible client, use the server URL https://docs.hyperstack.cloud/mcp with the Streamable HTTP transport and no authentication.

Verify the connection

Once the server is added, confirm it is working by asking your AI client a Hyperstack question, for example:

  • How do I create a spot Virtual Machine on Hyperstack?
  • What GPU flavors are available with an H100?
  • What does a Hyperstack 409 already_exist error mean?

If the connection is working, the client calls the Docs MCP Server and returns an answer that includes one or more https://docs.hyperstack.cloud/docs/... source links.

In Claude Code, you can also list your configured servers and check the connection status:

List MCP servers
claude mcp list

Available tools

The server exposes five read-only tools. Your AI client calls them automatically based on your question. For the full parameter reference and example prompts, see the Tools Reference.

ToolPurpose
search_docsSearch the documentation for a concept, feature, API endpoint, or workflow.
get_pageRetrieve the full content of a specific documentation page.
list_sectionsList the documentation structure, optionally filtered by product area.
lookup_errorExplain a Hyperstack API error and point to the fix.
get_flavor_infoReturn GPU flavor specifications for a model or hardware query.

Back to top