What it does
See, deploy and debug your existing DeployVera projects from coding agents.
- Connects 电脑或云端
- Account or key Cloud: Needs Authorization · Local: Needs DEPLOYVERA_TOKEN
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-16 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 DeployVera。按照 https://mcp.popnx.com/i/deployvera-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.deployvera.com) · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 DeployVera 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称DeployVeraRemote MCP server URL · 地址https://mcp.deployvera.com/mcp在 Request headers 下添加这个名称和值
Header 名称Authorization值Bearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsDeployVera
试一试
用 DeployVera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 DeployVera,或回答中出现 DeployVera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 DeployVera
DeployVera 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
你可以改用这些方式
A · 使用能连接 DeployVera 的应用
- 需要 DeployVera 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
- 需要 DeployVera 的密钥(在开发者网站创建)
- 需要 DeployVera 的密钥(在开发者网站创建)
- 需要 DeployVera 的密钥(在开发者网站创建)
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
可连接 Claude Code · 约 5 分钟
需要 DeployVera 的密钥(在开发者网站创建)
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user deployvera https://mcp.deployvera.com/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude Code 中输入 /mcp
应能看到 DeployVera 在列表中并显示已连接
试一试
用 DeployVera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 DeployVera,或回答中出现 DeployVera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 DeployVera 的密钥(在开发者网站创建)
填写你的密钥
在 DeployVera 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 DeployVera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 DeployVera,或回答中出现 DeployVera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 DeployVera 的密钥(在开发者网站创建)
填写你的密钥
在 DeployVera 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 DeployVera 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 DeployVera,或回答中出现 DeployVera 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user deployvera https://mcp.deployvera.com/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"deployvera": {
"url": "https://mcp.deployvera.com/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"deployvera": {
"type": "http",
"url": "https://mcp.deployvera.com/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}安装在电脑上
Claude Code
claude mcp add --scope user deployvera --env DEPLOYVERA_TOKEN=your-value -- npx -y deployvera-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"deployvera": {
"command": "npx",
"args": [
"-y",
"deployvera-mcp"
],
"env": {
"DEPLOYVERA_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"deployvera": {
"command": "npx",
"args": [
"-y",
"deployvera-mcp"
],
"env": {
"DEPLOYVERA_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"deployvera": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"deployvera-mcp"
],
"env": {
"DEPLOYVERA_TOKEN": "your-value"
}
}
}
}需要你填写的值
DEPLOYVERA_TOKEN机密 必填 envDeployVera personal access token (dvp_...)- 可选:来自 DeployVera 面板的 Bearer dvp_... 令牌。省略则通过浏览器登录(OAuth)。
查看英文原文
Optional: Bearer dvp_... token from DeployVera panel. Omit it to sign in with the browser (OAuth).
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 deployvera.com 验证(注册中心会核实域名所有权)
- ✓ 通过
仍在维护
代码最后更新于昨天
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 348 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
已公开的漏洞(OSV.dev)
尚未检查
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/deployvera-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6103 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6103 个服务器的 93% 更新
- 基础检查结果等于或优于此分类中其他 6103 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
DeployVera 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:Authorization, DEPLOYVERA_TOKEN
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于昨天,最新版本(0.5.0)于前天进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 DeployVera | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
DeployVera for AI agents
Connect coding agents (Claude Code, Cursor, VS Code, Codex and any other MCP client) to your existing DeployVera projects. The agent can list projects, deploy, follow builds, read logs, get a plain-language explanation of a failed build, check managed databases, manage environment variables, create new projects and connect custom domains (both with browser approval). It uses DeployVera's hosted MCP server at https://mcp.deployvera.com/mcp (Streamable HTTP), listed in the official MCP Registry as com.deployvera/mcp. This repository also contains a Claude Code plugin with a deploy workflow skill, plus Cursor and Gemini CLI manifests.
Get a token (only for token-based setups)
Browser sign-in needs no token. For clients without OAuth support, or for CI, create one:
- Sign in to the DeployVera panel.
- Open Settings > AI agent access and create a token.
- Pick the scopes (
read,deploy,env) and a lifetime (30, 90 or 365 days). - Copy the token (
dvp_...). It is shown once.
Use the smallest scope set that works. A read token cannot change anything.
Install
Sign in with browser (recommended)
Add the server URL without any token. The client opens your browser, you sign in to DeployVera and choose the scopes and duration, and the client stores the login. Nothing to copy or paste. Connected apps are listed, and can be disconnected, in Settings > AI agent access.
Claude Code: plugin (MCP server plus the deploy skill):
/plugin marketplace add deployvera/deployvera-mcp
/plugin install deployvera@deployvera
Then run /mcp, select deployvera and authenticate. Or add the server only:
claude mcp add --transport http deployvera https://mcp.deployvera.com/mcp
Cursor:
One click adds the server; Cursor then opens the DeployVera sign-in. Or add it to ~/.cursor/mcp.json (the repository also works as a Cursor plugin with a root mcp.json):
{
"mcpServers": { "deployvera": { "url": "https://mcp.deployvera.com/mcp" } } }
VS Code (.vscode/mcp.json or the user mcp.json):
{
"servers": { "deployvera": { "type": "http", "url": "https://mcp.deployvera.com/mcp" } } }
Gemini CLI: the repository root is a Gemini CLI extension (gemini-extension.json) with the same URL, no token. Gemini CLI starts the browser login on the first 401 response.
With a token
Use this when the client has no OAuth login, or for scripts. Create a token first (see above).
Claude Code
claude mcp add --transport http deployvera https://mcp.deployvera.com/mcp --header "Authorization: Bearer dvp_..."
Cursor: Add to Cursor installs a placeholder token (YOUR_DEPLOYVERA_TOKEN); replace it in Cursor's MCP settings. Or in ~/.cursor/mcp.json:
{
"mcpServers": { "deployvera": { "url": "https://mcp.deployvera.com/mcp", "headers": { "Authorization": "Bearer dvp_..." } } } }
VS Code: VS Code asks for the token once and stores it securely.
{
"inputs": [ { "type": "promptString", "id": "deployvera-token", "description": "DeployVera token (dvp_...)", "password": true } ], "servers": { "deployvera": { "type": "http", "url": "https://mcp.deployvera.com/mcp", "headers": { "Authorization": "Bearer ${input:deployvera-token}" } } } }
Codex (~/.codex/config.toml; export the token in your shell):
[mcp_servers.deployvera]
url = "https://mcp.deployvera.com/mcp" bearer_token_env_var = "DEPLOYVERA_TOKEN"
Windsurf and other clients: any client that supports remote MCP over Streamable HTTP works. Use the URL https://mcp.deployvera.com/mcp and, for tokens, the header Authorization: Bearer dvp_.... For stdio-only clients use npx -y deployvera-mcp with the DEPLOYVERA_TOKEN environment variable.
Tools
| Tool | Scope | What it does |
|---|---|---|
list_services | read | Your own services with plan, status, app quota, apps used and free slots. Shared services are not included |
list_repositories | read | Repositories you can deploy from connected GitHub/GitLab (and Gitea where enabled): provider, full name, URL, default branch, private flag. No tokens |
list_projects | read | Projects with status, live URL, repo/branch, last build |
get_project | read | Details, latest build, and whether the live commit is behind the branch |
check_domain | read | Whether a custom domain is attached and whether each name currently points to the project (live DNS lookup) |
get_build | read | Build status (latest by default); wait_seconds (0-120) polls every 5 s until it ends |
list_databases | read | Managed databases (id, name, engine, status, project). Never connection details or credentials |
get_database_logs | read | Tail (default 100, max 500) of a managed database's sanitized operational log |
get_build_logs | read | Tail (default 200, max 1000) of the sanitized build log, or source: "runtime" |
explain_build_failure | read | Reason code, plain-English cause, concrete fix steps and the last ~40 log lines |
list_env_vars | env | Keys and flags only (build-time, multiline). Values are never returned |
set_env_vars | env | Bulk set {KEY: value}; optional build_time, apply (restart). Values are never echoed |
delete_env_var | env | Delete by key; always needs approval, optional approval_id |
deploy | deploy | Deploy the branch head, or a specific commit_sha; returns the build id; optional approval_id |
rollback | deploy | Redeploy the retained image of an earlier build; always needs approval, optional approval_id |
cancel_build | deploy | Cancel a queued or running build |
create_project | deploy | Create a project in one of your own services from a Git repository (service_id, repo_url, source, branch; optional name, port, build_method, root_directory); always needs approval. No env values: use set_env_vars afterwards |
start_domain_verification | deploy | Returns the DNS records (TXT ownership challenge plus CNAME/A) the user must create for a custom domain; changes no routing, no approval |
set_domain | deploy | Attaches the domain once DNS is verified (otherwise an error to retry after propagation); always needs approval |
remove_domain | deploy | Detaches the custom domain; always needs approval |
check_approval | read | Status of an approval request (pending, approved, denied, expired, used) |
New project and domain: list_services (a service with a free slot; ordering a plan stays in the panel) -> list_repositories -> create_project (approval) -> set_env_vars -> deploy / get_build -> start_domain_verification -> create the DNS records -> set_domain (approval) -> check_domain.
Typical flow after pushing code: deploy, then get_build with wait_seconds=120. If it fails: explain_build_failure, fix, push, repeat.
Example prompts
- "Deploy my latest commit and tell me if it fails."
- "Why did my last build fail? Fix it and redeploy."
- "Which of my projects is behind its branch?"
- "Add DATABASE_URL to the api project and restart it." (give the value only if you are comfortable sharing it with the agent)
- "Show the last 100 runtime log lines of my site."
- "Are my databases running? Show the Postgres log if one is not."
Approvals
Some actions need your approval in the browser, whatever the token or login scopes:
create_project,set_domain,remove_domain,rollbackanddelete_env_varalways require it.- Optionally, approve every deploy can be switched on for a token or login, so
deployrequires it too.
When approval is needed, the agent shows you a link that opens on https://deployvera.com/approve/…. Check that the address bar shows deployvera.com before you enter your password. Then check what will happen and confirm with your password and second factor. Requests expire after 10 minutes, and each approval works for one action only.
Security
- Scopes:
read,deploy,env. A token only does what its scopes allow. - Environment variable values are write-only: masked in
list_env_vars, never echoed byset_env_vars, scrubbed from error text. A value you type into a prompt is visible to that agent. - Tokens and browser logins cannot buy or change plans, make payments, change billing or account settings, or reach admin routes. Creating a project and connecting a domain are possible but always need browser approval.
- Tokens expire after 30, 90 or 365 days and can be revoked at any time in Settings > AI agent access.
- Rate limit: 120 requests per minute.
- The hosted server is stateless and does not store tokens. Keep tokens out of repositories; prefer an environment variable or your client's secret prompt over a literal value in a config file.
Links
- Website: https://deployvera.com
- Panel: https://deployvera.com/clientarea
- Documentation: https://deployvera.com/docs/en/quickstart
- Privacy policy: https://deployvera.com/legal/privacy-policy
- Terms of service: https://deployvera.com/legal/terms-of-service
- Support:
License
MIT. See LICENSE. Logo: DeployVera mark, all rights reserved by DeployVera.