dockxo
FeaturesPricingBlogChangelogGet started Sign in
features/mcp-claude
Ask about your servers in plain wordssince v1.2

Claude & MCP

dockxo is an MCP server. Connect Claude or any MCP client and ask why a site returns 503, which certificates expire this month, or have it deploy and check a service, with exactly the access you allow.

  • MCP server at /mcp on your panel, Streamable HTTP, works with Claude, Claude Code, Cursor, VS Code and other MCP clients
  • Connect with OAuth: paste the URL, choose read only, read and deploy, or full access, approve. No token to copy
  • 34 tools: overview, services, logs, deployments, servers, monitors, certificates, open ports, traffic, database and cache health, deploy, restart, env, domains, redirects
  • Never deletes services, projects, volumes or servers, and never touches your sign-in methods or tokens
  • Passwords, tokens, keys and credentials inside URLs are masked in every answer; env values are read one at a time
  • Every change it makes is in the activity log as MCP (Claude): …; connected apps disconnect with one click

Ask, instead of clicking through

Most questions about a server are a dozen clicks: open the service, the logs, the last deploy, the server’s load, the load balancer’s health check. Connected to dockxo, Claude does those clicks for you and tells you what it found.

  • “laravel.shop returns 503 since ten minutes. Why?” It reads the service, its health, the last 300 log lines, the recent deployments and the server’s load, and answers with the evidence.
  • “Which certificates expire this month, and which domains do not point at my servers any more?”
  • “Deploy the api, wait for it, and tell me if it is healthy.”
  • “Which databases are open to the whole internet?”

Connect in a minute

Claude (desktop or claude.ai): Settings → Connectors → Add custom connector, name dockxo, URL https://panel.dockxo.com/mcp. dockxo opens a page in your browser where you choose what Claude may do and approve. Nothing to copy.

Claude Code:

claude mcp add --transport http dockxo https://panel.dockxo.com/mcp

then /mcp to sign in. Other clients take the URL and an API token in an Authorization header; Settings → API & MCP shows the exact JSON.

Exactly the access you allow

Access What it can do
Read only everything you can see in the panel: projects, services, logs, deployments, servers, monitors, certificates, open ports, jobs, traffic, the activity log
Read and deploy also deploy, restart, start and stop services, cancel jobs, run a monitor check
Full access also change env variables, domains, redirects and monitors, and read env values

Tools outside the chosen access are not even listed. Nothing that deletes a service, project, volume or server is offered at all, and a connected app can never change the account itself: tokens, password, email, two-factor, passkeys. The tools that change something are marked as such, so Claude asks before it runs them.

Built on the same API

Every tool goes through the panel’s own HTTP API with the client’s token, so the permission checks are the ones scripts and the browser get. Answers are shaped for a model: the fields that matter, dates you can read, secrets masked. OAuth 2.1 with dynamic client registration and PKCE, access tokens that last an hour and refresh tokens that rotate on every use. API tokens for scripts now have the same three scopes.

Related posts