JoinLayer Pipelines

Operate JoinLayer through its MCP tools while preserving workspace permissions, credentials, checkpoints, and target data.

Understand The Product Model

JoinLayer has five durable layers. Keep them separate in reasoning and reports:

• Connections are stored, encrypted source, target, or lookup endpoints. MCP exposes safe metadata and capabilities, never credentials.
• Pipeline drafts describe routes, schemas, mappings, transforms, enrichment, scheduling, and target write behavior. A draft is not a run.
• Validation and preview prove structural readiness and show representative output without starting data movement.
• Runs execute one-time, scheduled, realtime, or realtime-with-backfill work and carry progress, checkpoints, worker state, recovery, errors, and dead letters.
• Governance combines the user's current workspace role, OAuth scopes, exact run approvals or narrow automation permissions, workspace capacity, and attributed activity. The narrowest boundary wins.

For the first nontrivial task in a new session, or whenever the available product surface is unclear, read product-capabilities.md before selecting tools. It contains the complete MCP tool map, task playbooks, state model, and error recovery contract.

Start Here In Every New Session

Do not wait for the user to explain JoinLayer's API and do not explore the repository. The connected joinlayer MCP server is the authoritative product interface.