Coalesce MCP Server

If you already use Coalesce, the coalesce mcp server is the piece that lets your assistant work with it directly. MCP server for managing Coalesce Transform workspaces, nodes, pipelines, and runs.

What the server does

Each link below opens a short install guide with a click-to-install button (where supported) and the manual config.

Installation

The server ships on npm as coalesce-transform-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Credentials and setup notes

Configuration is passed through the environment: COALESCE_ACCESS_TOKEN, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by Coalesce-Software-Inc; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Coalesce's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.