DeployVera

Registre officiel Outils de développement

See, deploy and debug your existing DeployVera projects from coding agents.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http deployvera 'https://mcp.deployvera.com/mcp' --header 'Authorization: <Optional: Bearer dvp_... token from DeployVera panel. Omit it to sign in with the browser (OAuth).>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "deployvera": {
            "type": "http",
            "url": "https://mcp.deployvera.com/mcp",
            "headers": {
                "Authorization": "<Optional: Bearer dvp_... token from DeployVera panel. Omit it to sign in with the browser (OAuth).>"
            }
        }
    }
}
NPM package deployvera-mcp
Claude Code
claude mcp add deployvera -e 'DEPLOYVERA_TOKEN=<your deployvera_token>' -- npx -y deployvera-mcp@0.4.0
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "deployvera": {
            "command": "npx",
            "args": [
                "-y",
                "deployvera-mcp@0.4.0"
            ],
            "env": {
                "DEPLOYVERA_TOKEN": "<your deployvera_token>"
            }
        }
    }
}

Variables d'environnement

  • DEPLOYVERA_TOKEN obligatoire secret DeployVera personal access token (dvp_...)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. DeployVera for AI agents
  2. Get a token (only for token-based setups)
  3. Install
  4. Tools
  5. Example prompts
  6. Approvals
  7. Security
  8. Links
  9. License

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, and manage environment variables. 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:

  1. Sign in to the DeployVera panel.
  2. Open Settings > AI agent access and create a token.
  3. Pick the scopes (read, deploy, env) and a lifetime (30, 90 or 365 days).
  4. Copy the token (dvp_...). It is shown once.

Use the smallest scope set that works. A read token cannot change anything.

Install

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 (~/.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

ToolScopeWhat it does
list_projectsreadProjects with status, live URL, repo/branch, last build
get_projectreadDetails, latest build, and whether the live commit is behind the branch
get_buildreadBuild status (latest by default); wait_seconds (0-120) polls until it ends
get_build_logsreadTail (default 200, max 1000) of the sanitized build log, or runtime log
explain_build_failurereadReason code, plain-English cause, fix steps and the last log lines
list_env_varsenvKeys and flags only. Values are never returned
set_env_varsenvBulk set {KEY: value}; optional build_time and apply (restart)
delete_env_varenvDelete a variable by key
deploydeployDeploy the branch head, or a specific commit_sha; returns the build id
rollbackdeployRedeploy the retained image of an earlier build
cancel_builddeployCancel a queued or running build

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."

Approvals

Some actions need your approval in the browser, whatever the token or login scopes:

  • rollback and delete_env_var always require it.
  • Optionally, approve every deploy can be switched on for a token or login, so deploy requires 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 by set_env_vars, scrubbed from error text. A value you type into a prompt is visible to that agent.
  • Tokens and browser logins cannot create projects, change billing, domains or account settings, or reach admin routes. Use the panel for those.
  • 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.

License

MIT. See LICENSE. Logo: DeployVera mark, all rights reserved by DeployVera.

Questions fréquentes

Qu'est-ce que DeployVera ?

See, deploy and debug your existing DeployVera projects from coding agents.

Comment installer DeployVera ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http deployvera 'https://mcp.deployvera.com/mcp' --header 'Authorization: <Optional: Bearer dvp_... token from DeployVera panel. Omit it to sign in with the browser (OAuth).>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour DeployVera ?

Oui. Il attend DEPLOYVERA_TOKEN, Authorization, à renseigner dans sa configuration.

DeployVera est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient DeployVera ?

Il est publié par deployvera. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.