SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI codingdeploy-mcp

deploy-mcp

Deployment tracking and monitoring with live status badges.

Open website

About this tool

Purpose

deploy-mcp is a general-purpose deployment tracking tool for AI assistants. It allows developers to directly view the deployment status of configured platforms without interrupting the AI conversation, avoiding frequent window switching or jumping to each platform's dashboard. This project is open source and follows the Apache 2.0 license.

Main Capabilities

  • Multi-platform support: Can configure and track multiple deployment platforms such as Vercel, Netlify, Cloudflare Pages, etc. at the same time.
  • Deployment status queries: Check the deployment status of a specified project or site within the AI conversation, view the latest deployment, get deployment logs, and track deployment progress.
  • Project/site listing: List the projects or sites of all configured platforms, and view recent deployment records.
  • Deployment status badges: Generate real-time deployment status badges for public repositories, displayed via a shields.io endpoint wrapper. Supports configuring Webhooks to enable real-time badge updates.
  • Local token privacy: API tokens are stored only on the user's local machine, no telemetry data is collected, and only minimal read permissions are required.

How to Use

Configure the MCP service in your AI assistant and set the environment variables (tokens) for the corresponding platforms, then you can use it through natural language commands.

Supported AI assistant configuration locations include:

  • Claude Desktop: macOS is ~/Library/Application Support/Claude/claude_desktop_config.json, Windows is %APPDATA%\Claude\claude_desktop_config.json, Linux is ~/.config/Claude/claude_desktop_config.json;
  • VS Code (requires a GitHub Copilot subscription with MCP enabled): workspace .vscode/mcp.json, global ~/.vscode/mcp.json；
  • Cursor：~/.cursor/mcp.json, the settings path is Cursor Settings → MCP;
  • Windsurf:~/.codeium/windsurf/mcp_config.json, the settings path is Settings → Advanced Settings → Cascade;
  • Continue:~/.continue/config.json;
  • Cline (VS Code extension): MCP Servers icon → Advanced MCP Settings, and it also supports adding via natural language.

Token configuration examples for each platform:

  • Vercel:{ "env": { "VERCEL_TOKEN": "your-vercel-token" } }
  • Netlify：{ "env": { "NETLIFY_TOKEN": "your-netlify-token" } }
  • Cloudflare Pages：{ "env": { "CLOUDFLARE_TOKEN": "your-cloudflare-token-or-accountId:globalApiKey" } }

Cloudflare supports two token formats: API Token (requires additionally setting the CLOUDFLARE_ACCOUNT_ID environment variable) or Global API Key (theaccountId:globalApiKey all-in-one format).

Command examples (cross-platform common):

  • "Check my Vercel deployment for project-name"
  • "Show me Netlify deployment logs"
  • "Watch my Cloudflare Pages deployment progress"
  • "List all my Vercel projects"

The AI will automatically select the correct platform based on the platform explicitly mentioned in the command, matching of the project/site name, and the tokens available in the configuration.

Deployment Status Badges

The deploy-mcp.io endpoint returns JSON data for use by shields.io, and badges are displayed through shields.io's endpoint wrapper.

Webhook configuration methods:

  • Vercel: Configure the URL in Team Settings → Webhooks → Create Webhook https://deploy-mcp.io/webhook/{username}/{repo}/vercel, and select the Deployment Created, Ready, and Error events.
  • Netlify: Configure the URL in Site Settings → Build & deploy → Deploy notifications → Outgoing webhook https://deploy-mcp.io/webhook/{username}/{repo}/netlify, and select the Deploy started, succeeded, and failed events.

Note: The badge feature requires the repository to be public; private repository support is coming soon.

Use Cases

Suitable for developers who need to frequently monitor deployment status and want to quickly obtain deployment information without leaving the AI conversation interface. Especially suitable for teams or individuals who use multiple deployment platforms at the same time and need a unified view of deployment status.

Limitations

  • The badge feature currently only supports public repositories; private repository support is not yet available.
  • Each platform requires configuring the corresponding API token and meeting the corresponding read permission requirements.
  • For the specific supported token formats, permission requirements, and installation methods, please refer to the official repository documentation.

Related tools

Browse category