Skip to content

v3.3.0

Choose a tag to compare

@github-actions github-actions released this 11 Sep 10:13
· 64 commits to main since this release
25586b3

What's Changed

Added

  • Move a resource between environments (#299). application, database and service take a move action, taking the target environment_uuid. "Promote this app from staging to production" now has an answer that is one call instead of recreating the resource and copying env vars across. Requires Coolify v4.2+; an older instance is told so by name rather than returning a bare 404. The confirmation says what a move actually does: containers keep running, and from the next deployment the resource uses the target environment's shared environment variables.
  • Scheduled volume backups (#305). storages gains backup_set, backup_delete and backup_run for application, database and service volumes (Coolify v4.2+). backup_delete removes the archives as well as the schedule, so it asks first, and points at backup_set with enabled: false for the "stop backing up but keep what I have" case. Note two upstream limits: Coolify has no endpoint to read a schedule back, so find_issues still cannot flag a volume with no backup; and backup_set replaces the whole schedule rather than merging, so omitted fields revert to their defaults.
  • COOLIFY_ACCESS_TOKEN_FILE: rotate the Coolify token without restarting (#398). A stdio server is spawned once per client session and a subprocess never sees a later change to its parent's environment, so rotating COOLIFY_ACCESS_TOKEN could not reach a running server. Point the new variable at a file and it is re-read whenever the file changes, taking effect on the next tool call. A 401 triggers exactly one retry, and only when a re-read actually produced a different token, so a rotation landing mid-call recovers while a genuinely bad token still fails on the first attempt. doctor reports the source, and for a file its path and age, never the value. Raised by a user who retired this server partly for this reason.
  • Audit log for every tool call and every refusal (#370). One JSON line per call carrying the tool, action, resource uuids, outcome, duration, and in HTTP mode the OAuth client id. On by default in HTTP mode, off over stdio, COOLIFY_MCP_AUDIT overrides either way. Refusals are distinguished from errors and carry a reason category, so "a human said no" reads differently from "the client could not be asked". Arguments and responses are never logged: identifiers come from a closed allowlist of key names, so a future argument carrying a secret cannot reach a log line without a deliberate edit. See the audit section in docs/http-mode.md.
  • Privacy policy (PRIVACY.md). Written against the code, stating what the server collects (nothing), where the token goes (your Coolify instance and nowhere else), the one other outbound request it makes, and what the audit log does and does not record. Linked from the README and declared in manifest.json, both of which the Connectors Directory requires of a local connector.
  • A display title on every tool (#406). Tools now carry the spec's top-level title alongside name, so a client can show a person "Emergency stop" where the model reads stop_all_apps. Titles live in a table typed Record<ToolName, string>, so a new tool without one is a compile error rather than a blank label. The Connectors Directory requires a title on every submitted tool.

Changed

  • HTTP mode's audit line now reports what happened rather than what was asked. It previously peeked at the request body before dispatch, which could only name the tool; it is now written after the call completes and carries the outcome and duration.
  • The Client ID Metadata Document fetch is bounded at 3 seconds (#340), rather than inheriting the 10 second default. Claude allows 10 seconds for the whole of discovery, registration and token exchange, so one hop cannot be allowed to spend all of it. The client_id is a URL the caller chooses, so a host that connects and then stalls is entirely under their control.
  • The published tool-list token figure is corrected from ~6,600 to ~8,300 (#406). The surface grew through 3.x and the README did not follow, because the budget gate sat ~1,400 tokens above the number the docs advertised and so never tripped. The gate no longer holds a number of its own: it reads the figure out of the README and derives its ceiling from it, bounded in both directions so neither the payload nor the published claim can drift away from the other. Titles account for ~300 of the increase; the rest was already there and unreported.

Fixed

  • A loopback client can pick its own callback port (#340). redirect_uri was matched by exact string equality, so a native client that registers http://127.0.0.1/callback and then calls back on the ephemeral port it actually bound was rejected mid-redirect with a generic invalid_request. RFC 8252 requires the port to be free at request time for loopback redirects, and it now is. The relaxation applies only to loopback: a remote https callback differing by port is still a different endpoint and is still refused.

  • README answers "why not Coolify's own MCP server?" directly, with a comparison against the built-in /mcp and the official CLI, and recommends the built-in outright for single-instance read-only use.

  • Test fixtures, docs examples and one README example prompt now use IANA-reserved example.com names instead of live third-party domains, and the blast-radius example reads the same way in the changelog as it does in docs/security.md. No behaviour change.

Upgrading from 3.2

  • Drop-in for stdio users. No config changes and no new required
    variables. The tool count is unchanged at 45; three existing tools gained
    actions rather than new tools appearing.
  • HTTP mode now writes an audit line per tool call by default. It is one
    JSON line on stderr carrying the outcome, and it replaces the older
    pre-dispatch line that could only name the tool. Anything parsing on the
    audit key still matches, but the timing and the field set changed. Set
    COOLIFY_MCP_AUDIT=false to turn it off.
  • move and the volume backup actions need Coolify v4.2+. On an older
    instance they name the version requirement rather than returning a bare 404. Everything else works from v4.0.
  • Tools now carry a display title. Clients that show one will start
    showing it; clients that do not are unaffected. This is why the published
    tool-list figure moved.

📦 View on npm

🖱️ One-click Claude Desktop install: download coolify-mcp.mcpb below and drag it into Settings → Extensions.