Coalesce Transform
Manage Coalesce Transform workspaces, nodes, pipelines, and runs from your agent instead of clicking through the deploy UI.
Overview
Coalesce Transform MCP is a MCP server for the Build phase that manages Coalesce Transform workspaces, nodes, pipelines, and runs.
What is this MCP server?
- MCP tools for Coalesce workspaces, nodes, pipelines, and run lifecycle
- Auth via COALESCE_ACCESS_TOKEN or ~/.coa/config profile with optional COALESCE_BASE_URL regions
- Repo-backed operations when COALESCE_REPO_PATH points at your local Coalesce project root
- Npm coalesce-transform-mcp v0.7.2 stdio package for agent-driven data engineering
- Package version 0.7.2
- Npm identifier coalesce-transform-mcp
- Default COALESCE_BASE_URL https://app.coalescesoftware.io (US)
Community signal: 2 GitHub stars.
What problem does it solve?
Toggling between the Coalesce web app and your editor slows pipeline changes and makes run control hard to automate from the agent.
Who is it for?
Builders already on Coalesce who want MCP-driven pipeline and run operations tied to a local repo checkout.
Skip if: Greenfield projects with no Coalesce tenant, or teams that only need generic SQL linting without Coalesce APIs.
What do I get? / Deliverables
With token and repo path configured, your agent can inspect and drive Coalesce resources and runs from the same session as your code.
- Agent-driven visibility and control of Coalesce pipelines and runs
- Configured regional base URL and org context for cancel-run operations
- Integrated data engineering workflow inside your MCP client
Recommended MCP Servers
Journey fit
Data transformation orchestration is core backend build work when your product or analytics stack runs on Coalesce. Backend covers pipeline definitions, workspace operations, and run control for warehouse-native transforms.
How it compares
Coalesce platform control plane via MCP, not a generic database browser or dbt-only CLI skill.
Common Questions / FAQ
Who is Coalesce Transform MCP for?
Data engineers and solo builders using Coalesce Transform who want agents to manage workspaces, nodes, pipelines, and runs.
When should I use Coalesce Transform MCP?
Use it while building or maintaining transformation pipelines when you need run status, cancellations, or repo-backed edits from your coding agent.
How do I add Coalesce Transform MCP to my agent?
Install coalesce-transform-mcp, set COALESCE_ACCESS_TOKEN or a ~/.coa/config profile, optional COALESCE_REPO_PATH and COALESCE_BASE_URL, then register stdio in your MCP client.