mcpField
C
coalesce-transform

coalesce-transform

Local
github.com/jessemarshallDatabases

About coalesce-transform

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"jessemarshall-coalesce-transform": {
"command": "npx",
"args": [
"-y",
"coalesce-transform-mcp"
],
"env": {
"COALESCE_ACCESS_TOKEN": "<COALESCE_ACCESS_TOKEN>",
"COALESCE_PROFILE": "<COALESCE_PROFILE>",
"COALESCE_BASE_URL": "<COALESCE_BASE_URL>",
"COALESCE_ORG_ID": "<COALESCE_ORG_ID>",
"COALESCE_REPO_PATH": "<COALESCE_REPO_PATH>",
"COALESCE_CACHE_DIR": "<COALESCE_CACHE_DIR>",
"COALESCE_MCP_AUTO_CACHE_MAX_BYTES": "<COALESCE_MCP_AUTO_CACHE_MAX_BYTES>",
"COALESCE_MCP_LINEAGE_TTL_MS": "<COALESCE_MCP_LINEAGE_TTL_MS>",
"COALESCE_MCP_MAX_REQUEST_BODY_BYTES": "<COALESCE_MCP_MAX_REQUEST_BODY_BYTES>",
"COALESCE_MCP_READ_ONLY": "<COALESCE_MCP_READ_ONLY>",
"COALESCE_MCP_SKILLS_DIR": "<COALESCE_MCP_SKILLS_DIR>",
"SNOWFLAKE_ACCOUNT": "<SNOWFLAKE_ACCOUNT>",
"SNOWFLAKE_USERNAME": "<SNOWFLAKE_USERNAME>",
"SNOWFLAKE_KEY_PAIR_KEY": "<SNOWFLAKE_KEY_PAIR_KEY>",
"SNOWFLAKE_PAT": "<SNOWFLAKE_PAT>",
"SNOWFLAKE_KEY_PAIR_PASS": "<SNOWFLAKE_KEY_PAIR_PASS>",
"SNOWFLAKE_WAREHOUSE": "<SNOWFLAKE_WAREHOUSE>",
"SNOWFLAKE_ROLE": "<SNOWFLAKE_ROLE>"
}
}
}
}
Run commandnpx -y coalesce-transform-mcp
Environment variables to set
COALESCE_ACCESS_TOKENSecretBearer token from the Coalesce Deploy tab. Optional when `~/.coa/config` provides a `token`.
COALESCE_PROFILESelects which `~/.coa/config` profile to load. Defaults to default.
COALESCE_BASE_URLRegion-specific base URL. Defaults to https://app.coalescesoftware.io (US).
COALESCE_ORG_IDFallback org ID for cancel-run. Also readable from `orgID` in the active ~/.coa/config profile.
COALESCE_REPO_PATHLocal repo root for repo-backed tools and pipeline planning. Also readable from `repoPath` in the active ~/.coa/config profile.
COALESCE_CACHE_DIRBase directory for the local data cache. When set, cache files are written here instead of the working directory. Also readable from `cacheDir` in the active ~/.coa/config profile.
COALESCE_MCP_AUTO_CACHE_MAX_BYTESJSON size threshold before auto-caching to disk. Defaults to 32768.
COALESCE_MCP_LINEAGE_TTL_MSIn-memory lineage cache TTL in milliseconds. Defaults to 1800000.
COALESCE_MCP_MAX_REQUEST_BODY_BYTESMax outbound API request body size. Defaults to 524288.
COALESCE_MCP_READ_ONLYWhen `true`, hides all write/mutation tools during registration. Only read, list, search, cache, analyze, review, diagnose, and plan tools are exposed. Defaults to false.
COALESCE_MCP_SKILLS_DIRDirectory for customizable AI skill resources. When set, reads context resources from this directory and seeds defaults on first run. Users can augment or override any skill.
SNOWFLAKE_ACCOUNTSnowflake account identifier (e.g., `abc12345.us-east-1`). Required by the local `coa` CLI and `coa doctor`; not used by the MCP's REST run path. (required for run tools)
SNOWFLAKE_USERNAMESnowflake account username (required for run tools)
SNOWFLAKE_KEY_PAIR_KEYSecretPath to PEM-encoded private key (required if SNOWFLAKE_PAT not set)
SNOWFLAKE_PATSecretSnowflake Programmatic Access Token (alternative to key pair)
SNOWFLAKE_KEY_PAIR_PASSSecretPassphrase for encrypted keys
SNOWFLAKE_WAREHOUSESnowflake compute warehouse (required for run tools)
SNOWFLAKE_ROLESnowflake user role (required for run tools)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmcoalesce-transform-mcp0.7.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.