Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.joinlayer.app/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http app.joinlayer-mcp https://mcp.joinlayer.app/mcpRun in a terminal.
{ "mcpServers": { "app.joinlayer-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.joinlayer.app/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
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:
https://mcp.joinlayer.app/mcp
It is published as . The operating skill is available from , and this repository is the canonical source for the JoinLayer Codex and Claude Code marketplaces.
Operate secure JoinLayer data pipelines through delegated OAuth.
Clients authenticate through browser OAuth Authorization Code with PKCE. Never create, paste, or configure a JoinLayer bearer token manually.
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.
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.
Install the JoinLayer plugin from its public repository marketplace:
codex plugin marketplace add joinlayer/agent-toolkit
codex 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:
codex mcp add joinlayer --url https://mcp.joinlayer.app/mcp
codex mcp login joinlayer --scopes workspace:read,usage:read,connections:read,pipelines:read
Then start a fresh session and ask:
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 plugin marketplace add joinlayer/agent-toolkit
claude plugin install joinlayer@joinlayer --scope user
claude 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.
Agents supported by skills.sh can install only the operating skill:
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.
Report vulnerabilities privately as described in SECURITY.md.
python3.12 -m venv .venv
. .venv/bin/activate
pip install --requirement mcp-gateway/requirements.lock
PYTHONPATH=mcp-gateway python -m unittest mcp-gateway.tests.test_gateway
python 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:
python scripts/source_tree_digest.py --compare-root /path/to/private-platform
Apache-2.0. See LICENSE.
The code license does not grant rights to impersonate JoinLayer or imply endorsement. See TRADEMARKS.md.
© 2026 MCP Directory.
Operate secure JoinLayer data pipelines through delegated OAuth.
{ "mcpServers": { "app.joinlayer-mcp": { "url": "https://mcp.joinlayer.app/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
JoinLayer is reached over HTTP.
Last checked 2026-11-07. Operate secure JoinLayer data pipelines through delegated OAuth.