Dockhold

MCP运维云端

提供方 dockhold · 包名 dockhold

运维云端 stdio · 本地进程 Token 社区 / 第三方 ClaudeCursorVS CodeCodex
查看接入方式

Put the project you are working on online. Deploys the current folder or a GitHub repo to a live HTTPS URL on Dockhold; reads status and logs, sets variables, resizes apps and databases...

一句话选型结论

按资料字段整理

Dockhold 属于运维云端类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

deploy hosting mcp paas web apps github

支持客户端

适用场景

deployhostingmcp

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
npx -y dockhold mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Dockhold当前 未标注 stdio · 本地进程 本地部署 有 未标注
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方dockhold上游标注的维护方 dockhold
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时dockhold · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

6.5 KB
来自项目仓库与上游目录的原文,未做删改

Dockhold for your AI coding tool

Put the project you are working on online without leaving your editor. Install once, sign in once in the browser, then say "put this online". Your AI tool deploys the current folder (or a GitHub repo) to Dockhold and reports a live HTTPS URL. It can also read status and logs, set variables, and resize apps and managed databases.

No token to copy. Sign-in happens through the browser, the same way as the Dockhold CLI, and every client below shares it.

  • Docs: https://dockhold.eu/docs
  • Registry name: eu.dockhold/dockhold
  • Requirements: Node.js 18 or newer (for npx)

Install

Every install below starts the same local MCP server, npx -y dockhold mcp. It forwards each request to Dockhold with the sign-in the CLI stored on your machine. Nothing sensitive goes into your editor config.

Claude Code```

/plugin marketplace add dockhold/mcp
/plugin install dockhold@dockhold


This installs the MCP server and a `deploy` skill (invoked as `/dockhold:deploy`, or picked up on its own when you ask to put the project online) that knows the whole flow: preflight, sign-in, deploy, and what to do when a build fails.

### Cursor

The button opens this link in Cursor:```
cursor://anysphere.cursor-deeplink/mcp/install?name=dockhold&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRvY2tob2xkIiwibWNwIl0sImVudiI6eyJET0NLSE9MRF9SRUYiOiJjdXJzb3IifX0=

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):```json
{
"mcpServers": {
"dockhold": {
"command": "npx",
"args": ["-y", "dockhold", "mcp"],
"env": { "DOCKHOLD_REF": "cursor" }
}
}
}


This repo is also an Agent Plugin (`plugin.json` and `mcp.json` at the root), so Cursor can install it from its plugin browser once it is listed there: open **Customize** in the sidebar, search for Dockhold, and choose **Install**.

### VS Code```sh
code --add-mcp '{"name":"dockhold","command":"npx","args":["-y","dockhold","mcp"],"env":{"DOCKHOLD_REF":"vscode"}}'

Gemini CLI```sh

gemini extensions install https://github.com/dockhold/mcp


This repo is also a Gemini CLI extension (`gemini-extension.json` at the root), so the install adds the MCP server and the same `deploy` skill.

### Cline

Ask Cline to "install the MCP server from https://github.com/dockhold/mcp". It follows `llms-install.md`: one settings entry, no token, then a browser sign-in. To do it by hand, add the entry below to `cline_mcp_settings.json` with `"env": { "DOCKHOLD_REF": "cline" }`.

### Any other MCP client

Use the same server entry in your client's config:```json
{
  "mcpServers": {
    "dockhold": {
      "command": "npx",
      "args": ["-y", "dockhold", "mcp"]
    }
  }
}

If your client gives a server only a few seconds to start, the first npx -y dockhold download can be too slow for it. Install the CLI once with npm i -g dockhold and the same entry starts instantly.

Sign in

The first time a tool needs your account it answers with a message that says to run npx dockhold login in a terminal. Run it, a browser tab opens, and you are done. The sign-in lasts 90 days and is shared by the CLI and every client above. Nothing else to configure.

What it looks like

> You: put this online
>
> AI: Checked the project: it listens on PORT and has a Dockerfile. You are not signed in yet, so I am running npx dockhold login. A browser tab will open.
>
> (you sign in, the tab says you are done)
>
> AI: Signed in. Deploying with npx dockhold deploy --name recipe-box. Uploading, building...
>
> AI: Your app is live: https://recipe-box-a1b2c3.dockhold.app
>
> You: show me the logs
>
> AI: (calls get_app_logs) The last 100 lines: the server started on port 8080 and has served 3 requests. No errors.

Local folders deploy through the CLI, which needs no GitHub account. A GitHub repository deploys through the deploy_app tool. Deploys on every push need the repository connected to Dockhold (list_github_repos gives the github_installation_id to pass); a repository deployed by URL alone builds once.

Tools

Tool Scope What it does
list_apps read List your apps with id, status, and URL
get_app_status read Deploy status, URL, last commit, error message for one app
get_app_logs read Recent runtime logs for one app
get_resource_usage read Account pools (compute, database RAM, storage) and per-app sizes
list_github_repos read Your connected GitHub repos, with the id needed to deploy private ones
deploy_app deploy Deploy a GitHub repo as a live web app
deploy_group deploy Deploy several connected services in one go
redeploy_app deploy Zero-downtime restart of an app
set_app_variable deploy Set a non-secret environment variable and roll it out
unset_app_variable deploy Remove a plain environment variable and roll it out
resize_app deploy Change an app's memory
resize_database deploy Change a managed database's memory
resize_database_storage deploy Grow a managed database's disk
set_app_storage deploy Give an app storage that survives restarts and deploys, or grow it
remove_app_storage deploy Remove an app's storage and erase its files

The browser sign-in has the read and deploy scopes, which covers every tool above.

Remote server (no CLI)

For a client that cannot run a local command, the same tools are served over Streamable HTTP at https://api.dockhold.eu/mcp. Create a token in the Dockhold dashboard under Settings, then API tokens (read-only, read+deploy, or with secrets), and pass it as a bearer:json { "type": "streamable-http", "url": "https://api.dockhold.eu/mcp", "headers": { "Authorization": "Bearer dh_mcp_..." } }

Claude Code: claude mcp add --transport http dockhold https://api.dockhold.eu/mcp --header "Authorization: Bearer dh_mcp_...". This is the one setup that puts a token in a config file, so keep that file out of version control.

A dashboard token can also carry the secrets scope, which unlocks five more tools over this connection: set_app_secret, unset_app_secret, bind_app_secret, list_secrets, list_app_secrets. The browser sign-in never has that scope; with the plugin, secrets are added in the dashboard's Secrets section.

Getting started with Dockhold

Dockhold is the easiest way to put your app online: push from GitHub or deploy from a folder, always on, secure by default. Sign in at app.dockhold.eu. The free tier needs no card.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Dockhold 怎么安装?

在客户端按下面的安装命令接入:npx -y dockhold mcp。对应的包名是 dockhold。装完在客户端配置里引用同一个包或端点。

Dockhold 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Dockhold 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Dockhold 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Dockhold 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Dockhold 能提供哪些能力?

资料显示能力标签包括 deploy、hosting、mcp、paas、web apps、github。具体工具清单以官方文档为准。

Dockhold 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

Dockhold 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。