Breezedeploy

io.github.przemekzurPublished by GitHub account przemekzurv0.4.0Updated Oct 24, 2026

Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant deploy a local folder, git repository, or Docker image to a live HTTPS URL through the Breezedeploy control plane.

What you can do
Breezedeploy is a local MCP server that connects an AI assistant to a Breezedeploy control plane so deployments can be triggered from chat. According to the registry description, it can deploy a local folder, a git repo, or a Docker image and return a live HTTPS URL. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want to publish a project or container image to a hosted HTTPS address without leaving the assistant, for example to preview or share a build. It is a desktop-only local process, so it is not suitable for browser-based or headless use.
Requirements
Runs locally over stdio, installed from the npm package breezedeploy-mcp, so Node.js is needed. Requires a Breezedeploy account and the secret CONTROL_PLANE_API_KEY, which the provider says is shown once at signup. The optional CONTROL_PLANE_URL variable points at a self-hosted control plane and defaults to the provider's panel. Network access to that control plane is required.
Before you install
The server needs CONTROL_PLANE_API_KEY, a credential that can act on your Breezedeploy account; store it as a secret and do not share it. Deploying publishes your folder, repository, or image to a publicly reachable HTTPS URL, so check what is included before running it. The default control plane is a third-party service, and the manifest declares no authentication beyond the API key.

Installation

In SourceWeft

  1. Open Breezedeploy in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.