Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
Lawang Onboard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
local
or remote
—
calls last 7d
What it does
Permission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'ONBOARD_TOKEN=${ONBOARD_TOKEN}' --transport stdio lawang-onboard-mcp '--' docker run -i --rm -e ONBOARD_TOKEN ghcr.io/gablooge/lawang-onboard -stdio
# 2 — ask your agent for something these tools do
# whoami, get, search and 6 more
It needs ONBOARD_TOKEN: this reads it from your environment, so export it first.
Lawang Onboard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (ONBOARD_TOKEN_CONTRACTOR, ONBOARD_TOKEN_EMPLOYEE, ONBOARD_TOKEN_MAINTAINER), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads ONBOARD_TOKEN (The token this client uses. Set it to the same value as one of the role tokens below; that role decides what you see) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx ONBOARD_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'ONBOARD_TOKEN=${ONBOARD_TOKEN}' --transport stdio lawang-onboard-mcp '--' docker run -i --rm -e ONBOARD_TOKEN ghcr.io/gablooge/lawang-onboard -stdioReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://lawang-onboard.samsulhadi.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http lawang-onboard-mcp https://lawang-onboard.samsulhadi.com/mcpFree on mcprush, and it runs from its publisher’s own image: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: ONBOARD_TOKEN — The token this client uses. Set it to the same value as one of the role tokens below; that role decides what you see.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return the caller's role name and scope list.
No parameter schema on file.
Retrieve a single corpus item by its ID. Returns an empty result if the item is not found or not visible to the caller; both cases are indistinguishable.
No parameter schema on file.
Search corpus items visible to the caller using BM25 ranking. Hidden items never affect results or scores.
No parameter schema on file.
List all files, docs, and ADRs visible to the caller, optionally limited to a path depth.
No parameter schema on file.
Return the number of hidden items per missing scope plus a total of hidden items, across the whole corpus.
No parameter schema on file.
Find files, commits, reviews, and ADRs related to a term, grouped by kind.
No parameter schema on file.
For a repository path, return commits that touched it, review comments on it, and ADRs or docs that mention it.
No parameter schema on file.
Return the visible parts of README.md, Makefile, and .github/workflows files.
No parameter schema on file.
Return open issues whose label areas are within the caller's scopes.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lawang Onboard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lawang Onboard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.