{
  "server": {
    "name": "Hyperstack Docs",
    "version": "1.0.0",
    "transport": "http"
  },
  "capabilities": {
    "tools": {
      "listChanged": true
    }
  },
  "instructions": "You have access to the Hyperstack documentation corpus via these tools:\n\n- search_docs: Search for any concept, feature, API endpoint, or workflow.\n  Call this BEFORE answering questions about VMs, clusters, flavors, billing,\n  networking, storage, or any Hyperstack-specific term. Each result carries the\n  absolute docs URL of its page — cite it so the user gets a clickable source.\n\n- get_page: Retrieve the full content of a specific page when you need\n  complete parameter tables, code examples, or detailed reference content.\n  Accepts the docs URL from a search result or a bare /docs/... path.\n\n- list_sections: Get a table of contents, optionally filtered by product area\n  (vm, cluster, volume, networking, billing, ai_studio, hardware).\n\n- lookup_error: Look up any Hyperstack API error by HTTP status code,\n  error_reason string, or error message text to get the cause and fix.\n\n- get_flavor_info: Get GPU flavor specifications. Use before recommending\n  hardware configurations or answering pricing/capacity questions.\n\nCanonical hosts. These are the only Hyperstack hosts that exist. Do not construct others:\n  Core API        https://infrahub-api.nexgencloud.com\n  AI Studio API   https://console.hyperstack.cloud/ai/api/v1\n  Console         https://console.hyperstack.cloud\n  Documentation   https://docs.hyperstack.cloud\n\nIdentifiers must be quoted, not reconstructed. Hostnames, endpoint paths, flavor names\nand numeric limits are only correct if you read them in a tool result or in the list\nabove. If you do not have one, name the page that carries it rather than guessing at\nthe value.\n\n\nAnswer with what the documentation does give you. An answer that covers most of a\nprocedure and says which part is not documented is useful; declining because one detail\nis missing is not.\n\nThis corpus is documentation, not live account state. It cannot tell you a user's\nbalance, invoices, running resources, IP addresses, current GPU stock, or the status of\ntheir tickets or payments. For those, say the documentation cannot answer it and point\nto where the answer lives (the console, or the relevant API endpoint). Never present an\nexample response from a documentation page as the user's current data.",
  "endpoint": "https://docs.hyperstack.cloud/mcp",
  "production_endpoint": "https://docs.hyperstack.cloud/mcp",
  "server_card": "https://docs.hyperstack.cloud/mcp/server-card",
  "tools": [
    {
      "name": "search_docs",
      "description": "Natural-language search across the docs, with the source URL for each result."
    },
    {
      "name": "get_page",
      "description": "The full content of a specific page, by docs URL or a /docs/... path."
    },
    {
      "name": "list_sections",
      "description": "The table of contents, optionally filtered by product area."
    },
    {
      "name": "lookup_error",
      "description": "An API error's cause and fix, by status code, reason, or message text."
    },
    {
      "name": "get_flavor_info",
      "description": "GPU flavor specifications for hardware and capacity questions."
    }
  ],
  "docs": {
    "connect": "https://docs.hyperstack.cloud/docs/libraries/docs-mcp/",
    "tools_reference": "https://docs.hyperstack.cloud/docs/libraries/docs-mcp/tools-reference/"
  }
}