appbyggaren-mcp
Allows publishing static web apps by creating and managing Gitea repositories, including pushing source code, updating files, and optionally deleting repositories.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@appbyggaren-mcp make a page that counts down to the summer holidays"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
appbyggaren-mcp
An MCP server that lets an agent publish small static web apps: source into Gitea, build and TLS via Coolify. Five verbs, hard boundaries.
Built to give a household assistant a "mini Lovable" — "build me a page that counts down to the summer holidays" — without giving it the keys to the PaaS.
Why it exists
Coolify's own MCP server is read-only, and its API tokens are instance-wide
capabilities (read / write / deploy / root) with no per-project scoping.
Handing that token to a model means handing it every application on the instance,
including the ones you care about.
This server sits in between. It holds the write credentials; the model gets five verbs that cannot express anything outside the configured project, organisation and domain. The asymmetry is the whole design.
Related MCP server: coolify-mcp
Tools
Tool | Does |
| Apps published by this server, with status and URL |
| Status, URL and repository for one app |
| Create repo, push files, create the Coolify app, deploy |
| Replace files and redeploy |
| Last deployment log — for when a build fails |
| Remove the app; keeps the repo unless asked otherwise |
Apps are static sites served by nginx: HTML, CSS and client-side JS. No server-side runtime, no database.
Boundaries
Enforced in guards.py, on every mutating call:
Project — an application's project UUID is re-checked against the configured one before it can be touched. The UUID is the only thing the caller supplies, so it is never trusted.
Domain — publishing is limited to
<name>.<APPBYGGAREN_DOMAIN_SUFFIX>. An app re-pointed elsewhere in the Coolify UI drops out of scope and becomes immutable here.Organisation — repositories are only created under
GITEA_ORG.Names —
^[a-z0-9][a-z0-9-]{0,30}[a-z0-9]$, with a reserved list. The slug becomes a DNS label, a repo name and a container name, so it must survive all three.Payload — max 40 files, 2 MB total,
index.htmlrequired, and paths are normalised to reject traversal. Gitea's contents API takes the path verbatim, so../would otherwise escape the repository.
Configuration
All via environment variables — see .env.example. The Coolify,
Gitea and domain settings are required; everything else is optional.
Nothing about a particular deployment is baked into the source. Which hostnames are already taken, which domains count as internal, and which names are worth flagging are all properties of your installation — hard-coding them here would publish your DNS layout to anyone reading the repository.
Variable | Effect when unset |
| Only the generic baseline is reserved |
| The internal-hostname check does not run |
| No names are flagged |
|
|
The content scan is a filter, not a judgement
publish_app refuses when it finds personal numbers, email addresses, phone
numbers, private IPs, secrets, or anything you listed above. It will not notice
that "countdown to our holiday, 14 July" says when a house will be empty. Read
what the app actually says before publishing it.
Install
uv venv .venv && uv pip install --python .venv/bin/python .
.venv/bin/appbyggaren-mcp # stdio transportRegister with an MCP client (example: Hermes Agent):
hermes mcp add appbyggaren --command /opt/appbyggaren-mcp/.venv/bin/appbyggaren-mcpIf your client passes no environment to stdio children, reference the variables as
${VAR} placeholders in its config rather than inlining secrets.
Known Coolify quirks
/applications/public truncates the git URL. It stores only owner/repo and
leaves git_full_url, source_type and source_id null, assuming a hosted
provider. A self-hosted Gitea URL then never clones — and the failure is silent:
HTTP 201, no deployment recorded, no container, status exited:unhealthy, no error
anywhere. This server issues a PATCH with the full .git URL immediately after
creation and refuses to deploy if the stored value still looks truncated.
Certificates lag the deploy. Traefik requests the certificate when the router
appears, so the first seconds after publishing serve TRAEFIK DEFAULT CERT. That is
not a failure; it resolves on its own.
Development
uv pip install --python .venv/bin/python -e ".[dev]"
.venv/bin/pytest
.venv/bin/ruff check .Licence
MIT
Available Tools
8 toolscreate_appA
Publish a new static web app and return its generated name and URL.
files is a list of {"path": "index.html", "content": "<!doctype html>…"};
an index.html at the root is required.
The name is assigned by this server, not by you. It becomes a DNS label
in a zone that hosts real services, so it is generated here — you cannot
request one. Use description for the human-readable purpose; report the
returned name and URL back to the user verbatim.
The build is a static site served by nginx — HTML, CSS and client-side JS. There is no server-side runtime and no database.
Inputs: files (required), description, requested_by. Returns: result
delete_appA
Delete an app. The source repository is kept unless delete_repository is true.
Inputs: name (required), delete_repository. Returns: result
get_appA
Get status, URL and repository for one app.
Inputs: name (required). Returns: result
get_deploy_logsA
Return the most recent deployment log for an app — use when a build fails.
Inputs: name (required). Returns: result
list_appsA
List the apps published by this server, with status and URL.
Inputs: no named parameters. Returns: result
publish_appA
Make an app reachable from outside without a login.
Scans the repository first and refuses if it finds personal data, internal hostnames or secrets — a published app is readable by anyone.
The scan is a pattern filter, not a judgement. It cannot tell that "countdown to our holiday" reveals when the house is empty. Read what the app actually says before asking for this.
Inputs: name (required). Returns: result
unpublish_appB
Put an app back behind the login.
Inputs: name (required). Returns: result
update_appA
Replace files in an existing app and redeploy it.
Inputs: name (required), files (required), message. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct operation: CRUD for apps (create, get, list, update, delete), visibility control (publish/unpublish), and log retrieval. No overlapping purposes; get/list and publish/unpublish are clearly differentiated.
All tools follow a consistent verb_noun pattern in snake_case (delete_app, get_deploy_logs, list_apps, create_app, update_app, publish_app, unpublish_app). Verbs clearly indicate the action, and nouns stay within the app domain.
8 tools is well-scoped for a static web app management server, covering create, read, update, delete, publish/unpublish, and logs without redundancy or bloat.
Core lifecycle is fully covered (create, get, list, update, delete) plus visibility toggles and deployment logs. Minor gaps: only the most recent deploy log is available, and there is no tool to update app metadata like description.
Maintenance
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
Create, deploy, and operate MCP servers directly from your GitHub repositories.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to manage infrastructure, applications, databases, and services through the Coolify PaaS platform.14 npm4MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for Coolify infrastructure management, providing 45 tools for servers, applications, databases, deployments, and diagnostics via natural language.17 npmMIT
- AlicenseBqualityBmaintenanceMCP server for managing Coolify instances, enabling control of applications, databases, services, servers, and more via natural language.13657 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.8 npm2MIT