Coalesce Transform

io.github.jessemarshallPublished by GitHub account jessemarshallv0.7.2Updated Oct 27, 2026

MCP server for managing Coalesce Transform workspaces, nodes, pipelines, and runs.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Local MCP server for managing Coalesce Transform workspaces, nodes, pipelines and runs, with optional Snowflake credentials for run tools.

What you can do
  • Manage Coalesce Transform workspaces, nodes and pipelines through the Coalesce API.
  • Trigger and cancel runs, with org ID used as a fallback for cancel-run.
  • Read, list, search, cache, analyze, review, diagnose and plan via read-only tools.
  • Use repo-backed tools and pipeline planning against a local repository path.
  • Load customizable AI skill resources from a configurable skills directory.
When to use it
Useful when an assistant should help with Coalesce Transform data pipeline work: inspecting workspaces and nodes, planning pipelines from a local repo, or starting and cancelling runs. A read-only mode lets you expose only inspection and analysis tools.
Requirements
Runs as a local npm package over stdio on a desktop machine. Needs a Coalesce access token (COALESCE_ACCESS_TOKEN or a token in the ~/.coa/config profile) and optionally a region-specific COALESCE_BASE_URL. Run tools need Snowflake settings: SNOWFLAKE_ACCOUNT, SNOWFLAKE_USERNAME, SNOWFLAKE_ROLE, SNOWFLAKE_WAREHOUSE, plus either SNOWFLAKE_PAT or a key pair (SNOWFLAKE_KEY_PAIR_KEY, SNOWFLAKE_KEY_PAIR_PASS).
Before you install
Requires a Coalesce bearer token and possibly a Snowflake private key path and passphrase; keep these out of shared configs. Run tools can start or cancel jobs in your data platform, and write/mutation tools are exposed unless COALESCE_MCP_READ_ONLY is set to true. Data is cached to a local directory, and requests go to the Coalesce API at the configured base URL.

Installation

In SourceWeft

  1. Open Coalesce Transform in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.