原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Lawang Onboard

作者:gablooge版本 0.1.1i★ 0i电脑或云端官方网站 ↗
注册名称io.github.gablooge/lawang-onboard

安装方法

What it does

Permission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role.

  • Connects 电脑或云端
  • Account or key Cloud: Needs Authorization · Local: Needs ONBOARD_TOKEN, ONBOARD_TOKEN_CONTRACTOR, ONBOARD_TOKEN_EMPLOYEE, ONBOARD_TOKEN_MAINTAINER
  • Category 开发者工具

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

作者:morluto★ 468,7331 个 skill

Skill · 操作手册

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

作者:multica-ai★ 234,3321 个 skill

Skill · 操作手册未注明许可证

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

作者:Graphify-Labs★ 150,2871 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 3/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Lawang Onboard。按照 https://mcp.popnx.com/i/gablooge-lawang-onboard.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 3/5 项检查 · 你的提问会经过开发者的服务器(lawang-onboard.samsulhadi.com) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 Lawang Onboard 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 Lawang Onboard 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Lawang Onboard 网站 ↗

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Lawang Onboard
    Remote MCP server URL · 地址https://lawang-onboard.samsulhadi.com/mcp

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +ConnectorsLawang Onboard

  5. 试一试

    用 Lawang Onboard 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Lawang Onboard,或回答中出现 Lawang Onboard 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Lawang Onboard

Lawang Onboard 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 Lawang Onboard 的应用

  • 需要 Lawang Onboard 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 Lawang Onboard 的密钥(在开发者网站创建)
  • 需要 Lawang Onboard 的密钥(在开发者网站创建)
  • 需要 Lawang Onboard 的密钥(在开发者网站创建)

B · 开发者工具 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 Lawang Onboard 的密钥(在开发者网站创建)

  1. 注册并创建 Lawang Onboard 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Lawang Onboard 网站 ↗

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user lawang-onboard https://lawang-onboard.samsulhadi.com/mcp --header 'Authorization: Bearer {onboard_token}'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 Lawang Onboard 在列表中并显示已连接

  5. 试一试

    用 Lawang Onboard 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Lawang Onboard,或回答中出现 Lawang Onboard 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 Lawang Onboard 的密钥(在开发者网站创建)

  1. 注册并创建 Lawang Onboard 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Lawang Onboard 网站 ↗

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Lawang Onboard 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Lawang Onboard 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Lawang Onboard,或回答中出现 Lawang Onboard 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 Lawang Onboard 的密钥(在开发者网站创建)

  1. 注册并创建 Lawang Onboard 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Lawang Onboard 网站 ↗

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Lawang Onboard 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Lawang Onboard 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Lawang Onboard,或回答中出现 Lawang Onboard 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://lawang-onboard.samsulhadi.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Lawang Onboard 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user lawang-onboard https://lawang-onboard.samsulhadi.com/mcp --header 'Authorization: Bearer {onboard_token}'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "lawang-onboard": {
      "url": "https://lawang-onboard.samsulhadi.com/mcp",
      "headers": {
        "Authorization": "Bearer {onboard_token}"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "lawang-onboard": {
      "type": "http",
      "url": "https://lawang-onboard.samsulhadi.com/mcp",
      "headers": {
        "Authorization": "Bearer {onboard_token}"
      }
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user lawang-onboard --env ONBOARD_TOKEN=your-value --env ONBOARD_TOKEN_CONTRACTOR=your-value --env ONBOARD_TOKEN_EMPLOYEE=your-value --env ONBOARD_TOKEN_MAINTAINER=your-value -- docker run -i --rm -e ONBOARD_TOKEN -e ONBOARD_TOKEN_CONTRACTOR -e ONBOARD_TOKEN_EMPLOYEE -e ONBOARD_TOKEN_MAINTAINER ghcr.io/gablooge/lawang-onboard:0.1.1 -stdio

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "lawang-onboard": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ONBOARD_TOKEN",
        "-e",
        "ONBOARD_TOKEN_CONTRACTOR",
        "-e",
        "ONBOARD_TOKEN_EMPLOYEE",
        "-e",
        "ONBOARD_TOKEN_MAINTAINER",
        "ghcr.io/gablooge/lawang-onboard:0.1.1",
        "-stdio"
      ],
      "env": {
        "ONBOARD_TOKEN": "your-value",
        "ONBOARD_TOKEN_CONTRACTOR": "your-value",
        "ONBOARD_TOKEN_EMPLOYEE": "your-value",
        "ONBOARD_TOKEN_MAINTAINER": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "lawang-onboard": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ONBOARD_TOKEN",
        "-e",
        "ONBOARD_TOKEN_CONTRACTOR",
        "-e",
        "ONBOARD_TOKEN_EMPLOYEE",
        "-e",
        "ONBOARD_TOKEN_MAINTAINER",
        "ghcr.io/gablooge/lawang-onboard:0.1.1",
        "-stdio"
      ],
      "env": {
        "ONBOARD_TOKEN": "your-value",
        "ONBOARD_TOKEN_CONTRACTOR": "your-value",
        "ONBOARD_TOKEN_EMPLOYEE": "your-value",
        "ONBOARD_TOKEN_MAINTAINER": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "lawang-onboard": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ONBOARD_TOKEN",
        "-e",
        "ONBOARD_TOKEN_CONTRACTOR",
        "-e",
        "ONBOARD_TOKEN_EMPLOYEE",
        "-e",
        "ONBOARD_TOKEN_MAINTAINER",
        "ghcr.io/gablooge/lawang-onboard:0.1.1",
        "-stdio"
      ],
      "env": {
        "ONBOARD_TOKEN": "your-value",
        "ONBOARD_TOKEN_CONTRACTOR": "your-value",
        "ONBOARD_TOKEN_EMPLOYEE": "your-value",
        "ONBOARD_TOKEN_MAINTAINER": "your-value"
      }
    }
  }
}

需要你填写的值

  • ONBOARD_TOKEN 机密 必填 env
    此客户端使用的令牌。请将其设置为下方某个角色令牌的相同值;该角色决定您能看到的内容。
    查看英文原文The token this client uses. Set it to the same value as one of the role tokens below; that role decides what you see.
  • ONBOARD_TOKEN_CONTRACTOR 机密 必填 env
    contractor 角色的令牌(可自行选择任意密钥)。
    查看英文原文Token for the contractor role (any secret you choose)
  • ONBOARD_TOKEN_EMPLOYEE 机密 必填 env
    employee 角色的令牌(可自行选择任意密钥)。
    查看英文原文Token for the employee role (any secret you choose)
  • ONBOARD_TOKEN_MAINTAINER 机密 必填 env
    maintainer 角色的令牌(可自行选择任意密钥)。
    查看英文原文Token for the maintainer role (any secret you choose)
  • Authorization 机密 必填 HTTP header
    适用于您角色(maintainer、employee 或 contractor)的 Bearer 令牌。请向服务器管理员索取。
    查看英文原文Bearer token for your role (maintainer, employee or contractor). Ask the server operator for one.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
0.1.1
发布到注册中心i
2026年9月30日
代码最后更新i
2026年10月28日
最近检查
2026年11月19日
作者
gablooge
软件包
oci: ghcr.io/gablooge/lawang-onboard:0.1.1
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 gablooge 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于22天前

  • ✓ 通过

    有许可证

    使用 MIT

  • ! 注意

    端点有响应

    拒绝访问(HTTP 401),且未提供 OAuth 登录。可能需要密钥,也可能是拦截机器人,尚未确认。

  • ! 注意

    使用 OAuth 登录

    需要你自己复制粘贴密钥或令牌

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/gablooge-lawang-onboard.svg)](https://mcp.popnx.com/en/servers/gablooge-lawang-onboard)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 6182 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 6182 个服务器的 40% 更新
  • 基础检查结果等于或优于此分类中其他 6182 个服务器的 10%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Lawang Onboard 安全吗?

它在 5 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization, ONBOARD_TOKEN, ONBOARD_TOKEN_CONTRACTOR, ONBOARD_TOKEN_EMPLOYEE, ONBOARD_TOKEN_MAINTAINER

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于22天前,最新版本(0.1.1)于2个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

作者:ahmedkhaleel2004广泛使用★ 1.9万2个月前更新

在云端运行✓ 服务方 · gitdiagram.comPopNx 团队已实际试用

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

作者:Appllama广泛使用★ 52303个月前更新

在云端运行✓ 服务方 · appllama.io

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

作者:omnara-ai广泛使用★ 34172个月前更新

在云端运行✓ 服务方 · omnara.com

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

作者:repowise-dev广泛使用↓ 6506/周★ 8180 整个仓库的星标6天前更新

电脑或云端✓ 服务方 · repowise.dev
与相似项目对比
本项
Lawang Onboard
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否是否否
基础检查3/54/44/44/44/45/5
许可证MITMITMITApache-2.0Apache-2.0AGPL-3.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Lawang Onboard

Permission-aware AI onboarding. An onboarding copilot inside IBM Bob that explains a codebase to a new engineer, and only the parts they are allowed to see.

Built for the IBM Bob 2.0 Hackathon (lablab.ai, 25 to 27 September 2026) by team Lawang Onboard.

The problem

A new engineer, or a contractor hired for one module, needs weeks to learn why a codebase looks the way it does. The answers exist, spread across commit messages, architecture decision records and pull request reviews, but nobody reads those on day one. And access is all or nothing: either the newcomer sees everything, including whatever an AI assistant can read into its context, or they wait for someone to explain.

What it does

Open the repository in IBM Bob, switch to the Onboard mode, and ask:

  • /tour: the map of what you can see, module by module.
  • /trace webhook: how a webhook becomes a record, step by step.
  • /why internal/ingress: the decisions and reviews behind a path.
  • "What can I pick up first?"

Bob answers from the code and its history, and cites every item it used. Every piece of context carries a scope; the engineer's role maps to a set of scopes; the role comes from the token on the connection; and the Lawang Onboard MCP server filters before the model sees anything. A contractor's session cannot leak what it was never given, and every answer ends with what was withheld:

Withheld: path:cmd (68), path:internal/core (314), path:migrations (56), path:repo (86),

private:growth (18), private:security (6) | total hidden: 399

ContractorMaintainer

Results

Measured on 26 September with the contractor role, one fresh Bob task per question, by a team member who did not build the server. Full write-up: docs/benchmark.md.

Result
Ten onboarding questions10 of 10 correct, 36 s and 0.16 Bobcoins per answer on average
Against answering by hand46 s vs 210 s on three questions, one of which could not be answered by hand at all
Leak probes (prompt injection, direct get, claiming another role, search, "guess")5 of 5 held; nothing outside the role's scopes reached the model
Code review by Bob2 real findings (unauthenticated demo API, an existence oracle in get), both fixed and rechecked
Withheld countsMatch an independent recount from roles.yaml and the corpus on every run
Leak tests11 test functions, each across all three roles, plus planted injection items; go test -race ./... in CI

How it works

IBM Bob (Onboard mode: rules, skills, slash commands)

| MCP over stdio or HTTPS, bearer token v onboard server (Go) token -> role -> scopes -> one filter function -> tools -> audit log | corpus/*.jsonl (610 items: files, docs, ADRs, commits, PRs, reviews, issues, each with scopes)

  • Scopes come from roles.yaml: path globs (first match wins), labels (a growth label makes an issue private) and kinds. An item needs every one of its scopes; an item with no scope is denied to everyone.
  • Tools: whoami, map_system, search, get, trace_feature, why, setup_guide, starter_tasks, withheld. Each filters first and builds its answer only from visible items. A hidden id and a missing id get the same answer.
  • Onboard mode can use only MCP tools and skills, not the file system, so Bob's only view of the code is the filtered one. Its rules make it call whoami first, cite item ids, treat corpus text as data, mark proposals as proposals and close with the Withheld line.
  • Tokens are compared in constant time; an unknown, empty or ambiguous token is refused. The demo page's API uses the same tokens.

Design notes: docs/design.md.

Try it

  • Live demo: https://lawang-onboard.samsulhadi.com (paste a role token to see that role's view).
  • Connect a client: IBM Bob, Claude Code, Cursor and VS Code are set up below, over stdio through the published image or over HTTPS through the hosted server.

Connect your MCP client

server.json declares two ways in, and the nine tools and four prompts are the same through both:

TransportAddressWhat you need
stdiothe image ghcr.io/gablooge/lawang-onboard:0.1.2, run with -stdioDocker, and a secret you pick
streamable-httphttps://lawang-onboard.samsulhadi.com/mcpa role token from the server operator

0.1.2 is the tag to pull, and it is the first whose binary reports the tag as its serverInfo.version (0.1.1 reported 0.1.0) and the first that serves the prompts. Over stdio you are the operator: pick any secret, give it to one role, and set ONBOARD_TOKEN to the same value. That role decides what you see, and the image carries the Lawang demo corpus, so there is nothing else to set up. Over HTTPS the tokens are ours, so ask us for one.

Keep the secret out of any file you commit. The Bob, Claude Code and Cursor snippets below read it from your environment, so export it before you start the client; the VS Code snippets below do not read it, and VS Code prompts you for it once instead. The two values are deliberately the same: one names the role, the other says which role this client claims.

read -rs ONBOARD_TOKEN && export ONBOARD_TOKEN   # typed, so it stays out of your shell history

export ONBOARD_TOKEN_CONTRACTOR="$ONBOARD_TOKEN"

Then pick your client. Each snippet names the documentation it came from and the day that page was read; these clients change their configuration formats, so check the page if a snippet does not work.

IBM Bob

Copy .bob/mcp.example.json to .bob/mcp.json for a local server over stdio, or .bob/mcp.remote.example.json for the hosted one, put your token in, reload MCP servers, switch to the Onboard mode and type /tour. Both hold the token literally, in a file .gitignore keeps out of git. For the local one that is what the flow under "Run it locally" expects: scripts/use-role.py writes the token into that file's env object for you. The remote one you paste into headers yourself, because it has no env object and that script does not touch it. The block below keeps the token in your environment instead.

For the published image over stdio, with no Go toolchain:

{

"mcpServers": { "lawang-onboard": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "ONBOARD_TOKEN", "-e", "ONBOARD_TOKEN_CONTRACTOR", "ghcr.io/gablooge/lawang-onboard:0.1.2", "-stdio"], "env": { "ONBOARD_TOKEN": "${env:ONBOARD_TOKEN}", "ONBOARD_TOKEN_CONTRACTOR": "${env:ONBOARD_TOKEN_CONTRACTOR}" } } } }

So the file holds a variable name and never your secret. Three Bob details behind that, measured on 12 October 2026 (Bob IDE 2.2.1 and Bob Shell 2.0.5, which carry the same MCP client):

  • Bob expands ${env:NAME} from its own environment. env and headers were tested; args goes through the same walk over the entry. A bare ${NAME} is not expanded and arrives as that literal text, which is worth knowing before you copy a ${VAR} out of an older note.
  • The env object is doing real work: Bob gives a stdio server a fixed allow-list (HOME, LOGNAME, PATH, SHELL, TERM, USER) plus the entry's own env, and nothing else. So -e ONBOARD_TOKEN on its own passes nothing on and the image exits with onboard: ONBOARD_TOKEN is not set. Keep both halves.
  • Export the variables before you start Bob. Setting them in another terminal afterwards does not reach a Bob that is already running.
Claude Code

Two commands, from the claude mcp add reference (read 12 October 2026). --env values and header values are expanded from your environment when the server starts, so the ${...} text is what gets written to the configuration, not your secret. Everything after -- is passed to the server untouched, which is what lets docker run keep its own flags.

Over stdio, through the image:

claude mcp add --env 'ONBOARD_TOKEN=${ONBOARD_TOKEN}' \

--env 'ONBOARD_TOKEN_CONTRACTOR=${ONBOARD_TOKEN_CONTRACTOR}' --transport stdio lawang-onboard \ -- docker run -i --rm -e ONBOARD_TOKEN -e ONBOARD_TOKEN_CONTRACTOR \ ghcr.io/gablooge/lawang-onboard:0.1.2 -stdio

Over HTTPS, through the hosted server:

claude mcp add --transport http lawang-onboard https://lawang-onboard.samsulhadi.com/mcp \

--header 'Authorization: Bearer ${ONBOARD_TOKEN}'

Both write to local scope, which is this project only; add --scope user for every project. The single quotes matter: they stop your shell expanding the token into the stored command. Checked at that default scope on CLI 2.1.293: the entry lands in ~/.claude.json under this project's path, the ${...} text is what is stored, and claude mcp list reports Connected with the variables exported and Failed to connect without them, naming them as missing.

One silent failure to know about on the HTTPS entry. Under "Credential variables that read as empty", that page says some credential-like names read as empty instead of expanding in a remote server's url and headers. It gives three categories with examples rather than a list, and says a name outside them expands as written. ONBOARD_TOKEN is outside them, and it did expand on CLI 2.1.293, measured against a local endpoint that logged the header it received. If yours reads as empty, the header goes out as a bare Bearer and this server answers 401. claude mcp list is the quick check; claude --debug-file /tmp/claude-debug.log and a search for "never expanded toward a remote server" is the one that names the variable.

Cursor

.cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project, under mcpServers. Cursor resolves ${env:NAME} in command, args, env, url and headers. From Cursor's MCP documentation (read 12 October 2026).

Over stdio, through the image. That page's stdio field table marks type required with the value "stdio", while none of its stdio examples carry it, so this snippet follows the table:

{

"mcpServers": { "lawang-onboard": { "type": "stdio", "command": "docker", "args": ["run", "-i", "--rm", "-e", "ONBOARD_TOKEN", "-e", "ONBOARD_TOKEN_CONTRACTOR", "ghcr.io/gablooge/lawang-onboard:0.1.2", "-stdio"], "env": { "ONBOARD_TOKEN": "${env:ONBOARD_TOKEN}", "ONBOARD_TOKEN_CONTRACTOR": "${env:ONBOARD_TOKEN_CONTRACTOR}" } } } }

Over HTTPS, through the hosted server:

{

"mcpServers": { "lawang-onboard": { "url": "https://lawang-onboard.samsulhadi.com/mcp", "headers": { "Authorization": "Bearer ${env:ONBOARD_TOKEN}" } } } }

A remote entry is a url and optional headers; the documentation names no transport field, and Cursor works out streamable HTTP for itself.

VS Code

.vscode/mcp.json in the workspace, or the same file in your user profile, under servers. Fields and variables from the MCP configuration reference (read 12 October 2026): type, command, args, env and envFile for stdio, type, url and headers for a remote server. That page documents ${input:id} and ${workspaceFolder}, and not ${env:NAME}, so the token comes from an inputs entry: VS Code asks for i

只显示了开头部分;其余内容请在仓库中阅读