API & MCP · for developers and AI agents

Your hosting. In code or in chat.

A REST API for your servers, webspaces, domains and DNS, and an MCP server that lets Claude Code, Cursor or GitHub Copilot run them for you.

  • OpenAPI specification
  • Scoped API keys
  • Every call in the activity log

A REST API for everything you run.

Create and resize servers, manage webspaces, domains, DNS records and backups from your own scripts. Described in an OpenAPI specification and authenticated with a bearer key.

An MCP server for your AI agent.

Connect Claude Code, Cursor, GitHub Copilot or any client that speaks the Model Context Protocol, with the same key as the API. Your agent restarts servers, reads monitoring and edits DNS.

Keys with limits.

Pick every permission per resource, restrict a key to single servers, domains or webspaces, and give it a spending limit and an expiry date.

Your agent asks before it breaks something.

Reinstalls, restores, cancellations and everything else that cannot be undone wait for your explicit yes. Every call lands in the activity log, marked as API or MCP.

Automate the boring parts.

Questions about API and MCP.

What can I manage through the API?
Servers, webspaces, domains and DNS: from status and monitoring to backups, firewall, files and commands. The OpenAPI reference lists every endpoint.
How do I authenticate?
With an API key as a bearer token. You create keys in the dashboard under API / MCP, each with a name, its permissions and an optional expiry date.
Do I need a separate key for MCP?
No. The MCP server accepts the same API keys as the REST API, with the same permissions.
Which AI clients work with the MCP server?
Every client that speaks the Model Context Protocol over Streamable HTTP, for example Claude Code, Claude Desktop, Cursor and GitHub Copilot in VS Code. The endpoint is https://site.quest/mcp.
Can my agent delete something by accident?
Destructive tools such as reinstalling, restoring a backup, deleting files or cancelling need your explicit confirmation. And a key can only do what its permissions allow.
How do I limit what a key can do?
Choose each permission per resource, for example read-only for servers and DNS editing for domains. You can also restrict a key to single servers, domains or webspaces, and give keys that upgrade or order a spending limit.
Is there a rate limit?
60 requests per minute per API key, for REST and MCP together. Every response carries the remaining requests in its headers.
Can I see what a script or an agent did?
Yes. Every call shows up in the activity log, marked as API or MCP. With the X-Run-Id header you group all calls of one CI job or one agent run.