Skip to content

docs: switch MCP install from bitbadges-builder-mcp to bitbadgesjs-sdk#35

Merged
trevormil merged 8 commits intomasterfrom
feat/mcp-in-sdk
Apr 14, 2026
Merged

docs: switch MCP install from bitbadges-builder-mcp to bitbadgesjs-sdk#35
trevormil merged 8 commits intomasterfrom
feat/mcp-in-sdk

Conversation

@trevormil
Copy link
Copy Markdown
Owner

@trevormil trevormil commented Apr 13, 2026

Summary

  • Rewrites 6 markdown sources + the generated `for-llms.txt` aggregate so every documented install of the MCP builder points at `bitbadgesjs-sdk` instead of the now-archived `bitbadges-builder-mcp` package.
  • Commands updated: `npm install -g …`, `npx …`, Claude Desktop `args` array, `claude mcp add …`.
  • URLs repointed: npm package link, GitHub source link → `bitbadgesjs/tree/main/packages/bitbadgesjs-sdk/src/mcp`.
  • Preserves the `bitbadges-builder-mcp` name as the bin (now `npx -p bitbadgesjs-sdk bitbadges-builder-mcp`). Existing Claude Desktop configs that reference server name `bitbadges-builder` don't have to change — only the install command users ran once.
  • `for-llms.txt` updated in the same pass since it's checked in; will self-regenerate correctly on the next build.

Why

`bitbadges-builder-mcp` has been folded into `bitbadgesjs-sdk`. See bitbadgesjs#144 for context.

Files touched

  • `overview/official-links.md`
  • `for-developers/getting-started.md`
  • `for-developers/ai-agents/README.md`
  • `for-developers/ai-agents/mcp-builder-tools.md`
  • `token-standard/bb-402/collection-recipes.md`
  • `x-tokenization/examples/skills/README.md`
  • `for-llms.txt`

Companion PRs

Test plan

  • `grep -rn 'bitbadges-builder-mcp' .` only returns preserved bin-name references inside `-p bitbadgesjs-sdk` commands
  • Once SDK PR merges + publishes, manually run `npm install -g bitbadgesjs-sdk` and confirm `bitbadges-builder-mcp` binary is on PATH
  • Re-run Claude Desktop config from the docs end-to-end against the new install

🤖 Generated with Claude Code

The bitbadges-builder-mcp package has been folded into bitbadgesjs-sdk
and the standalone repo is being archived. The MCP server is now shipped
as a bin entry on bitbadgesjs-sdk, so everything migrates to a single
install while preserving the `bitbadges-builder-mcp` command name (so
existing Claude Desktop configs keep working once the user reinstalls).

Rewrites:
- `npm install -g bitbadges-builder-mcp` → `npm install -g bitbadgesjs-sdk`
- `npx bitbadges-builder-mcp` → `npx -p bitbadgesjs-sdk bitbadges-builder-mcp`
- Claude Desktop args array switched to the `-p` form
- npm / GitHub URLs repointed at bitbadgesjs/tree/main/packages/bitbadgesjs-sdk/src/mcp

Touches 6 markdown sources under overview/, for-developers/,
token-standard/, x-tokenization/, plus the generated for-llms.txt
aggregate so the checked-in copy stays consistent until the next
regeneration.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
trevormil and others added 7 commits April 13, 2026 11:24
Part of the wave that renames the builder tool surface — "MCP" was
overloaded (wire protocol vs. tool identity) and the canonical brand
is "BitBadges Builder". See bitbadgesjs feat/fold-mcp-into-sdk for
the code-side rename.

Scope:
- for-developers/ai-agents/mcp-builder-tools.md → builder-tools.md
  (+ SUMMARY.md and cross-ref link updates)
- Install commands: `bitbadges-builder-mcp` bin → `bitbadges-builder`
  (inside `npx -p bitbadgesjs-sdk ...` and Claude Desktop args arrays)
- Section headings: "MCP Builder Tools" → "BitBadges Builder Tools",
  "MCP Quick Setup" → "Quick Setup",
  "MCP Tool Workflow" → "Builder Tool Workflow",
  "MCP Agent Workflow" → "Builder Agent Workflow",
  "## MCP Tools" → "## Builder Tools",
  "## MCP Resources" → "## Builder Resources"
- Prose: "The MCP server does X" → "The builder does X" (for our
  server; protocol-level refs to MCP clients/servers left alone)
- GitHub source URL: `bitbadgesjs-sdk/src/mcp` → `/src/builder`
- for-llms.txt updated in the same pass to keep the aggregate
  consistent until the next regeneration

Preserved (protocol-true references):
- `claude mcp add` — Claude Code's own CLI command, not ours
- `"mcpServers": {}` — Claude Desktop config key shape
- `.cursor/mcp.json` — Cursor's config filename
- `MCP-compatible client`, `that speak MCP` — accurate prose
- `GitBook MCP` and `docs.bitbadges.io/~gitbook/mcp` — external service
- `https://actions.zapier.com/settings/mcp/` — external URL

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Follows bitbadgesjs feat/fold-mcp-into-sdk @ b4b2b39a8c where the
standalone `build` command group was folded under `builder templates`
and `builder list/call` moved under `builder tools`. This commit
updates every docs reference to the new paths.

Scope:
- `bitbadges-cli build <template>` → `bitbadges-cli builder templates <template>`
  across the 18 template invocations (vault, subscription, bounty,
  crowdfund, auction, product-catalog, prediction-market,
  smart-account, credit-token, custom-2fa, quests, address-list,
  intent, recurring-payment, listing, bid, pm-sell-intent,
  pm-buy-intent).
- `bitbadges-cli builder list|call` → `bitbadges-cli builder tools list|call`
- `--dry-run --explain` → `--explain` (auto-review is now the default;
  `--dry-run` flag was removed in favor of `--json-only` opt-out)
- Renamed `for-developers/cli/build-commands.md` to
  `for-developers/cli/builder-templates.md`; `SUMMARY.md` cross-ref
  updated to "Builder Templates".
- `for-llms.txt` aggregate updated in the same pass to keep the
  checked-in copy consistent until the next regeneration.

Verified with grep: zero `bitbadges-cli build ` invocations remain;
remaining hits are the new `bitbadges-cli builder templates ` form.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Three small doc updates from the parity + consolidation pass:

- builder-templates.md: document the new `--seller <address>` flag on
  `builder templates auction` — it locks the mint-to-winner approval's
  initiatedByListId so only the seller can accept the winning bid.
  Defaults to `--creator`. Added to the flag table and the example.
- sdk-commands.md / bitbadges-sdk/cli.md: rewrite the `sdk review`
  fallback paragraph. The local path is now the unified
  `reviewCollection()` entry point (not the separate
  validateTransaction / auditCollection / verifyStandardsCompliance
  calls). Adds a short paragraph explaining that findings carry an
  `audience` field ('agent' | 'human' | 'both') and that the frontend
  sidebar uses `audienceFilter: 'human'` via ReviewContext to hide
  agent-oriented audit output the MCP validators already surface.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…eview_collection

Both tools were removed from the SDK registry. review_collection
bundles audit, standards compliance, and UX findings into one call.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
New for-developers/cli/builder-commands.md covers every non-templates
subcommand under the builder umbrella (tools, review, verify, validate,
simulate, explain, preview, doctor, session, resources). Replaces the
last audit_collection/verify_standards references with review_collection
in the agent docs. Adds a blockquote to the simulate endpoint docs
noting the new agent-JSON payload shape is accepted but internal for
now — external integrations should stay on the proto tx_bytes path.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Regenerated all 23 skill pages + README from the newly-ported
bitbadgesjs-sdk/scripts/gen-skill-docs.ts. Pulls SKILL_INSTRUCTIONS
from src/builder/resources/skillInstructions.ts in the SDK (previously
src/resources/skillInstructions.ts in bitbadges-builder-mcp).

Picked-up content changes from upstream skill text edits:
- Auction: burn approval now shows no approvalCriteria overrides,
  noForcefulPostMintTransfers: true in the invariants summary, and an
  explicit note that the mint-to-winner approval is auto-deleted
  post-settlement (protocol validator accepts its absence as valid).
- Prediction Market: summary calls out the noForcefulPostMintTransfers
  lock and the non-mint override-flag rule for redeem / settlement /
  transferable approvals.
- Crowdfund: summary calls out the same lock + rule, clarifies which
  approvals are Mint-side (keep overridesFromOutgoingApprovals: true)
  vs the refund approval (must not set override flags).
- Credit Token / Smart Token / Liquidity Pools / Products: minor
  PathMetadata shape corrections picked up from the skill text
  (image/name/description fields removed from the on-chain proto
  metadata; now live in the per-msg metadataPlaceholders sidecar).

No manual edits to skill pages — all changes flow through the
generator. To regenerate after future skill text updates:

  cd bitbadgesjs/packages/bitbadgesjs-sdk
  npx tsx scripts/gen-skill-docs.ts
@trevormil trevormil merged commit 005b4d0 into master Apr 14, 2026
2 checks passed
@trevormil trevormil deleted the feat/mcp-in-sdk branch April 14, 2026 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant