Model Context Protocol (MCP)

The Sitequest MCP endpoint lets AI assistants like GitHub Copilot, Claude, or other MCP-compatible clients interact with your infrastructure directly.

Overview

MCP (Model Context Protocol) is an open standard that allows AI applications to securely connect to external tools and data sources. Sitequest implements a stateless Streamable HTTP MCP server.

• Endpoint: POST https://hosting.site.quest/mcp
• Protocol version: 2025-03-26
• Transport: Streamable HTTP (stateless, JSON responses)
• Authentication: Same API keys as the REST API

Available Tools

VPS tools

Domain tools

Order tools

Webspace tools

Shared web hosting with isolated PHP/MariaDB sites. SFTP and exec tools operate as the unprivileged site Linux user, jailed to the site's home directory.

Pricing for webspaces is not yet exposed via MCP. Use the REST endpoint GET /api/v1/webspaces/pricing until a get_webspace_pricing tool is added.

Setup for VS Code / GitHub Copilot

Create a .vscode/mcp.json file in your workspace:

{
  "servers": {
    "sitequest": {
      "type": "http",
      "url": "https://hosting.site.quest/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with an API key that has the scopes you need (e.g. vps:read, domains:read).

After saving the file, VS Code will detect the MCP server automatically. You can then ask Copilot questions like:

• "List my VPS instances"
• "What domains do I have?"
• "Show me the details for server X"

Setup for Other MCP Clients

Any MCP client that supports the Streamable HTTP transport can connect. Configure:

• URL: https://hosting.site.quest/mcp
• Method: POST only (GET returns 405)
• Headers:
  • Authorization: Bearer YOUR_API_KEY
  • Content-Type: application/json
  • Accept: application/json, text/event-stream

Manual JSON-RPC Example

Initialize:

curl -X POST https://hosting.site.quest/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": { "name": "my-client", "version": "1.0" }
    }
  }'

List available tools:

curl -X POST https://hosting.site.quest/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/list"}'

Call a tool:

curl -X POST https://hosting.site.quest/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "list_vms",
      "arguments": {}
    }
  }'

Authentication

MCP uses the same API key system as the REST API. See Authorization for details on creating keys and managing scopes.

Rate Limiting

MCP requests share the same rate limit as the REST API: 60 requests per minute per API key. Rate limit headers are included in every response.

Differences from REST API

Source code & client examples

The Sitequest MCP server listing, sample client configurations (VS Code, Claude Desktop, Cursor, and more), and the directory listing for MCP catalogs are maintained in the public repository:

github.com/Sitequest-Software/sitequest-mcp