JoinLayer

app.joinlayer由 joinlayer.app 發布官方發布者v0.1.2更新於 Oct 24, 2026

Operate secure JoinLayer data pipelines through delegated OAuth.

已驗證Streamable HTTP可網頁執行雲端與基礎設施資料與分析

概覽

AI 產生的概覽

託管的 JoinLayer MCP 閘道，讓助理透過委派 OAuth 檢視並操作安全的資料管線。

可以做什麼
檢視已驗證的工作區、權限範圍、容量、連線與管線（唯讀起始提示）。
適用情境
當你使用 JoinLayer 資料管線，並希望助理檢視工作區狀態、連線、容量與管線，或依提供的流程處理複製、即時回填、排程、資料擴充、核准與復原時使用。
執行需求
需要連線至 JoinLayer 託管的遠端 MCP 端點；透過用戶端完成瀏覽器 OAuth 授權碼加 PKCE 登入；不需手動設定 bearer token 或 Authorization 標頭。Codex、Claude Code 與 skills.sh 用戶端可選安裝外掛或技能。
安裝前請注意
OAuth 會授予對 JoinLayer 工作區的委派存取權，核准前請核對所要求的權限範圍（工作區、用量、連線、管線）。伺服器回傳的值為不可信資料，而非指令。連線憑證只在 JoinLayer 瀏覽器設定工作階段中輸入，絕不作為工具參數。部分文件流程不只限於唯讀檢視。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 JoinLayer，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/app.joinlayer%2Fmcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "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.

來源：README.md，提交 36add21

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v0.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分