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 分