Coalesce Transform
Let your agent list workspaces, edit transform nodes, and trigger or cancel Coalesce pipeline runs from chat while you build the warehouse layer.
Overview
io.github.Coalesce-Software-Inc/coalesce-transform is an MCP server for the Build phase that manages Coalesce Transform workspaces, nodes, pipelines, and runs via stdio tools authenticated to the Coalesce cloud API.
What is this MCP server?
- npm package coalesce-transform-mcp (server version 0.9.3) with stdio transport
- Manage Coalesce Transform workspaces, nodes, pipelines, and runs from MCP tools
- Auth via COALESCE_ACCESS_TOKEN or ~/.coa/config profiles (COALESCE_PROFILE)
- Region-aware COALESCE_BASE_URL defaulting to https://app.coalescesoftware.io
- Optional COALESCE_REPO_PATH for repo-backed tooling against local transform projects
- npm identifier coalesce-transform-mcp
- Documented environment variables include COALESCE_ACCESS_TOKEN, COALESCE_PROFILE, COALESCE_BASE_URL, COALESCE_ORG_ID, CO
Community signal: 2 GitHub stars.
What problem does it solve?
Toggling between the Coalesce UI and your agent breaks flow when you need to inspect nodes, kick off runs, or cancel jobs while iterating on warehouse logic.
Who is it for?
Solo builders shipping analytics-backed SaaS who already use Coalesce Transform and want agent-driven pipeline and workspace operations.
Skip if: Teams with no Coalesce tenant or builders who only need generic SQL linting without Coalesce APIs.
What do I get? / Deliverables
After configuration, your agent can operate Coalesce workspace resources and runs through MCP instead of manual UI-only steps.
- stdio MCP bridge to your Coalesce Transform tenant
- Agent-callable workspace, node, pipeline, and run operations
- Faster backend iteration on transform projects with optional repo-backed context
Recommended MCP Servers
Journey fit
Build fits because you use it while constructing and changing analytics pipelines, not while doing launch SEO or support macros. Backend aligns with warehouse transform logic, nodes, pipelines, and operational runs managed through the Coalesce API.
How it compares
Coalesce SaaS control-plane MCP, not a local dbt CLI skill or generic database browser.
Common Questions / FAQ
Who is io.github.Coalesce-Software-Inc/coalesce-transform for?
It is for developers and data-focused solo founders on Coalesce Transform who want MCP tools for workspaces, nodes, pipelines, and runs inside their coding agent.
When should I use io.github.Coalesce-Software-Inc/coalesce-transform?
Use it during Build while designing and operating warehouse backends—editing transform structures, running pipelines, and coordinating deploy-related actions from the agent.
How do I add io.github.Coalesce-Software-Inc/coalesce-transform to my agent?
Install coalesce-transform-mcp from npm, set COALESCE_ACCESS_TOKEN or a ~/.coa/config profile, optionally COALESCE_BASE_URL and COALESCE_REPO_PATH, then add the stdio server entry in your MCP client.