Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Lawang Onboard

by gabloogeversion 0.1.1i★ 0iComputer or cloudOfficial site ↗
Registry nameio.github.gablooge/lawang-onboard

How to install

What it does

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

  • Connects Computer or cloud
  • Account or key Cloud: Needs Authorization · Local: Needs ONBOARD_TOKEN, ONBOARD_TOKEN_CONTRACTOR, ONBOARD_TOKEN_EMPLOYEE, ONBOARD_TOKEN_MAINTAINER
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

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

by morluto★ 468,7331 skills

Skill · How-to guide

andrej-karpathy-skills

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

by multica-ai★ 234,3321 skills

Skill · How-to guideNo license stated

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.

by Graphify-Labs★ 150,2871 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering8/8The cloud endpoint answered at the last check
Usage score20/100

Quality: Passed 3/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Lawang Onboard. Follow https://mcp.popnx.com/i/gablooge-lawang-onboard.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/5 checks · What you ask goes through the maker’s server (lawang-onboard.samsulhadi.com) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 5 min

You need a Lawang Onboard key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Sign up and create a Lawang Onboard key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Lawang Onboard site ↗

  2. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameLawang Onboard
    Remote MCP server URL · Addresshttps://lawang-onboard.samsulhadi.com/mcp

    Under Request headers, add this name and value

    Header nameAuthorization
    ValueBearer <paste your key here>

    Paste the key only into the app’s field, never into a chat or to anyone

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  4. Turn it on in a chat

    +ConnectorsLawang Onboard

  5. Try it

    Use Lawang Onboard and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Lawang Onboard or shows a Lawang Onboard tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Lawang Onboard yet

Lawang Onboard needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify

What you can do instead

A · Use an app that can connect Lawang Onboard

  • You need a Lawang Onboard key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
  • You need a Lawang Onboard key (create it on the maker’s site)
  • You need a Lawang Onboard key (create it on the maker’s site)
  • You need a Lawang Onboard key (create it on the maker’s site)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code · about 5 min

You need a Lawang Onboard key (create it on the maker’s site)

  1. Sign up and create a Lawang Onboard key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Lawang Onboard site ↗

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

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

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Type /mcp in Claude Code

    You should see Lawang Onboard listed as connected

  5. Try it

    Use Lawang Onboard and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Lawang Onboard or shows a Lawang Onboard tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 5 min

You need a Lawang Onboard key (create it on the maker’s site)

  1. Sign up and create a Lawang Onboard key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Lawang Onboard site ↗

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Fill in your key

    In the Lawang Onboard settings, Authorization is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Open the AI chat in Cursor in Agent mode

  5. Try it

    Use Lawang Onboard and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Lawang Onboard or shows a Lawang Onboard tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 5 min

You need a Lawang Onboard key (create it on the maker’s site)

  1. Sign up and create a Lawang Onboard key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Lawang Onboard site ↗

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Fill in your key

    In the Lawang Onboard settings, Authorization is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  4. Open the AI chat in VS Code in Agent mode

  5. Try it

    Use Lawang Onboard and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Lawang Onboard or shows a Lawang Onboard tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://lawang-onboard.samsulhadi.com/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Lawang Onboard💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

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}"
      }
    }
  }
}

Installed on your computer

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"
      }
    }
  }
}

Values you fill in

  • ONBOARD_TOKEN secret required 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 secret required env
    Token for the contractor role (any secret you choose)
  • ONBOARD_TOKEN_EMPLOYEE secret required env
    Token for the employee role (any secret you choose)
  • ONBOARD_TOKEN_MAINTAINER secret required env
    Token for the maintainer role (any secret you choose)
  • Authorization secret required HTTP header
    Bearer token for your role (maintainer, employee or contractor). Ask the server operator for one.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Connection
Computer or cloud
Transport
stdio, streamable-http
Latest versioni
0.1.1
Published to registryi
Sep 30, 2026
Code last changedi
Oct 28, 2026
Last checked
Nov 19, 2026
Maker
gablooge
Packages
oci: ghcr.io/gablooge/lawang-onboard:0.1.1
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

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

Run on your computer in

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

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account gablooge, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 22 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • ! Caution

    Endpoint responds

    Refused access (HTTP 401) without offering OAuth sign-in. It may need a key, or it may be blocking bots; not confirmed.

  • ! Caution

    Sign-in with OAuth

    Needs a key or token that you copy and paste yourself

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

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

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 0% of the other 6182 servers in this category
  • Published to the registry more recently than 40% of the other 6182 servers in this category
  • Basic checks equal to or better than 10% of the other 6182 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Lawang Onboard safe?

It passed 3 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization, ONBOARD_TOKEN, ONBOARD_TOKEN_CONTRACTOR, ONBOARD_TOKEN_EMPLOYEE, ONBOARD_TOKEN_MAINTAINER

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed 22 days ago, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

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

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

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

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

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

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
Lawang Onboard
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/54/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Only the beginning is shown; read the rest in the repo