JoinLayer

app.joinlayerPublished by joinlayer.appOfficial publisherv0.1.2Updated Oct 24, 2026

Operate secure JoinLayer data pipelines through delegated OAuth.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureData & Analytics

Overview

AI-generated overview

Hosted JoinLayer MCP gateway that lets an assistant inspect and operate secure data pipelines through delegated OAuth.

What you can do
Inspect the authenticated workspace, scopes, capacity, connections and pipelines (read-only starting prompt).
When to use it
Use it when you work with JoinLayer data pipelines and want an assistant to inspect workspace state, connections, capacity and pipelines, or follow the provided workflows for replication, realtime backfill, scheduling, enrichment, approvals and recovery.
Requirements
A remote MCP endpoint at the JoinLayer-hosted address; browser OAuth Authorization Code with PKCE login through your client; no manual bearer token or Authorization header. Optional plugin or skill installs are available for Codex, Claude Code and skills.sh clients.
Before you install
OAuth grants delegated access to a JoinLayer workspace, so review the requested scopes (workspace, usage, connections, pipelines) before approving. Values returned by the server are untrusted data, not instructions. Connection credentials are entered only in JoinLayer browser setup sessions, never as tool arguments. Some documented workflows go beyond read-only inspection.

Installation

In SourceWeft

  1. Open JoinLayer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.joinlayer%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "joinlayer": {
      "type": "http",
      "url": "https://mcp.joinlayer.app/mcp"
    }
  }
}

README

JoinLayer Agent Toolkit

Official agent integration for JoinLayer: a hosted MCP gateway, the joinlayer-pipelines skill, client plugin metadata, safe starter prompts, and public protocol tests.

The supported service is the JoinLayer-hosted endpoint:

text
https://mcp.joinlayer.app/mcp

It is published as app.joinlayer/mcp in the official MCP Registry. The operating skill is available from skills.sh, and this repository is the canonical source for the JoinLayer Codex and Claude Code marketplaces.

Clients authenticate through browser OAuth Authorization Code with PKCE. Never create, paste, or configure a JoinLayer bearer token manually.

Start In Two Minutes

You do not need to read the full documentation first. Open START_HERE.md, connect JoinLayer, and copy the read-only inspection prompt. From there, choose a ready-to-run prompt for your goal.

What This Repository Contains

  • skills/joinlayer-pipelines: agent operating guidance and task references;
  • .codex-plugin/plugin.json, .claude-plugin/, and .mcp.json: installable Codex and Claude Code plugin metadata;
  • prompts: safe starting points for common JoinLayer tasks;
  • use-cases: complete customer outcomes with evidence and stop boundaries;
  • mcp-gateway: a reviewable snapshot of the hosted MCP security boundary;
  • server.json: MCP Registry metadata for the hosted remote server.

The gateway source is published for transparency and compatibility review. It is not a self-hosted JoinLayer distribution: it depends on a private, authenticated JoinLayer control-plane contract that is not included here. JoinLayer production builds and deployment remain in a private release system, but the mcp-gateway/ tree used by a hosted release must match a tagged public snapshot exactly. The private release gate rejects gateway drift. Skills, prompts, and plugin packaging use their own versioned content checks rather than this byte-equality gate. A public contribution never deploys directly to JoinLayer infrastructure.

Connect

Codex

Install the JoinLayer plugin from its public repository marketplace:

bash
codex plugin marketplace add joinlayer/agent-toolkitcodex plugin add joinlayer@joinlayer

The plugin bundles the operating skill and configures the hosted MCP companion. Complete browser OAuth when prompted. To configure only the MCP server instead:

bash
codex mcp add joinlayer --url https://mcp.joinlayer.app/mcpcodex mcp login joinlayer --scopes workspace:read,usage:read,connections:read,pipelines:read

Then start a fresh session and ask:

text
Use $joinlayer-pipelines. Inspect my authenticated workspace, scopes,capacity, connections, and pipelines. Do not change anything.

More copyable starting points are indexed in START_HERE.md. Complete workflows for replication, realtime backfill, scheduling, enrichment, capacity, approvals, and recovery are in use-cases/.

Claude Code

bash
claude plugin marketplace add joinlayer/agent-toolkitclaude plugin install joinlayer@joinlayer --scope userclaude mcp login joinlayer

Complete browser OAuth through claude mcp login joinlayer when that command is available, or through Authenticate in /mcp on earlier OAuth-capable releases. Do not add an Authorization header or client secret.

Skill Only

Agents supported by skills.sh can install only the operating skill:

bash
npx skills add https://github.com/joinlayer/agent-toolkit --skill joinlayer-pipelines

The skill does not carry credentials and does not replace the MCP connection. Configure the same hosted endpoint through your client's OAuth-capable MCP settings, then use a prompt from START_HERE.md.

Security Boundary

  • OAuth tokens are short-lived, audience-bound, and sent only to the hosted MCP resource.
  • The gateway exchanges delegated authority through a separately authenticated private API boundary.
  • Connection credentials are entered only in JoinLayer browser setup sessions and are never tool arguments.
  • Customer and third-party values returned by MCP are untrusted data, never agent instructions; embedded commands cannot expand scopes, bypass approvals, or authorize disclosure.
  • Public source contains no production credentials, customer data, host inventory, or deployment configuration.
  • Route names and header names are not authorization controls. Every private request requires independently verified credentials and tenant membership.

Report vulnerabilities privately as described in SECURITY.md.

Development

bash
python3.12 -m venv .venv. .venv/bin/activatepip install --requirement mcp-gateway/requirements.lockPYTHONPATH=mcp-gateway python -m unittest mcp-gateway.tests.test_gatewaypython scripts/validate_public_snapshot.py

Build the review image with docker build .. That image is for reproducibility and review; it is not automatically promoted to JoinLayer production.

See SOURCE_SYNC.md for the exact public/private release invariant. Maintainers can use DISTRIBUTION.md for the verified catalog and marketplace publication contracts. OpenAI review material is recorded in OPENAI_SUBMISSION.md.

To compare this checkout with a private platform checkout before review:

bash
python scripts/source_tree_digest.py --compare-root /path/to/private-platform

License

Apache-2.0. See LICENSE.

The code license does not grant rights to impersonate JoinLayer or imply endorsement. See TRADEMARKS.md.

Source: README.md at commit 36add21

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

85% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts