{"report":{"v":1,"package":"@bridge-ds/mcp","version":"0.17.0","ranAt":"2026-11-16T11:34:01.034Z","install":{"ok":true,"integrity":"sha512-kHoj3+sxYTDvqesm/L3FfSbcgaF72mBKphsoN94nEIYfKeBB0T5duzk9hPxLMbYl9cTuMgCQGjoepZwdzFKdWQ==","deps":101,"scripts":[],"bins":["bridge-mcp"],"license":"FSL-1.1-MIT","engines":"node >=20.19.0","repository":"git+https://github.com/the-bridge-company/ai-design-system-demo.git","bin":"bridge-mcp"},"start":{"ok":true,"ms":330,"serverName":"bridge","serverVersion":"0.17.0","protocol":"2025-06-18","stderr":"bridge-mcp 0.17.0: local repo / (not a git repo). Read-only on GitHub: suggestions, requests, reviews, merges and pull requests need GITHUB_TOKEN (or a gh sign-in when the server starts). Not a git repo: no local branches.\nbridge-mcp: No GitHub token: GITHUB_TOKEN and BRIDGE_GITHUB_TOKEN are not set and gh is not signed in. Bridge reads GitHub without a token (60 requests an hour) and cannot write there. Set GITHUB_TOKEN where the server runs, or run gh auth login, then restart the server.\n"},"tools":[{"name":"bridge_get_config","description":"Where the design system lives and what Bridge may do: source (local path or GitHub repo), write access, token tiers, modes (brand/theme/density...) and the full bridge.config.json. Call first in a new repo.","params":[]},{"name":"bridge_whoami","description":"Who this session acts as: the person's name, their role in the team (Admin, Reviewer, Can edit or Reader), how they signed in (GitHub login, or email member with the address masked), the team, and in one line what a save means for them (through Bridge as them, or with their own GitHub access). Call it when the person asks which account Bridge uses, or before a first save when unsure.","params":[]},{"name":"bridge_get_claude_design_system","description":"The Bridge Library as a Claude Design System, at the version Bridge serves now: the version, a manifest (path, size, sha256 and download url of each file, published under project/), the team's Design System artifact when Bridge knows it, what to do (\"create\", \"update\" or \"none\"), the files that changed since the team last published, and the steps. Call it when the person asks to add or update the Library in Claude Design, and before building with the Library in a claude.ai artifact or any page that cannot install npm packages (load its files from \"base\"). Create the artifact once; after that always republish ONLY the changed files to the same artifact URL, then re-run the install in the canvases that use it. Set \"inline\" to get the text of small files in the answer.","params":["inline"]},{"name":"bridge_set_claude_design_system_url","description":"Saves, for the team, the address of its Design System artifact in Claude Design and the version just published to it, so the next bridge_get_claude_design_system lists only the files that changed and Studio Settings says when an update is ready. Admins and leads only (Bridge checks). Call it right after creating or republishing the artifact.","params":["url","version"]},{"name":"bridge_list_tokens","description":"List tokens with their resolved CSS value in one mode. Filter by tier (primitive, brand, semantic, density, component...), $type, or path prefix. Paginated (limit/offset).","params":["tier","type","prefix","mode","limit","offset"]},{"name":"bridge_get_token","description":"Everything about one token: CSS variable, type, tier, description, the files that define it, resolved value in every mode (brand x theme x density, collapsed where equal) with its alias chain, tokens that alias it, and components whose CSS uses it (directly or through a component token).","params":["path"]},{"name":"bridge_search_tokens","description":"Find tokens by words in the path or description (\"danger text\", \"focus ring\"), by CSS variable, or by value (\"#c2410c\", \"16px\": exact and near colors). Use before writing UI code or proposing a new token.","params":["query","type","limit"]},{"name":"bridge_check_contrast","description":"Run the repo's WCAG contrast gate (every pair in every brand x theme). Pass `edits` to preview a change: returns the pairs that move and any new failure, without writing anything. Pass `pairs` to check ad-hoc fg/bg pairs.","params":["edits","pairs","mode","includePassing"]},{"name":"bridge_validate_tokens","description":"Validate tokens: DTCG 2025.10 shape per $type, names, broken and circular aliases in every mode, alias type mismatches, missing layer files, and mode parity (a semantic token must exist in both light and dark). Pass `edits` to validate a change before proposing it.","params":["edits","includeWarnings"]},{"name":"bridge_list_components","description":"List design system components with family, one-line summary (what it is for) and figma: the Figma component and its link, or \"not linked to Figma yet\". Use before building UI: prefer an existing component over new markup. For a claude.ai artifact or any page that cannot install npm packages, call bridge_get_claude_design_system and load the Library from its base URL; never invent token values.","params":["family","withSummaries"]},{"name":"bridge_get_component","description":"One component: props parsed from TypeScript (type, default, description, allowed values), usage docs (summary, whenToUse, whenNotToUse, dos/donts with examples, accessibility, contentGuidelines, anatomy), CSS variables it uses, story names, and figma: its Figma component and link from bridge.components.json, or \"not linked to Figma yet\". For a claude.ai artifact or any page that cannot install npm packages, call bridge_get_claude_design_system and load the Library from its base URL; never invent token values.","params":["name","include"]},{"name":"bridge_draft_docs","description":"Start or refresh a component's docs.json. Returns what the code tells (props table from TypeScript, tokens its stylesheet reads, tokens it reads through another component's stylesheet, anatomy from the CSS module classes, contrast checks those tokens take part in, a changelog line, existing prose kept, the keys still missing), the target path, and a prompt for you to write the missing prose in the repo conventions. Nothing is written: save the result with \"draftedBy\": \"claude\" and \"needsReview\": true so a reviewer accepts it in Bridge Studio.","params":["name","branch","page"]},{"name":"bridge_get_design_language","description":"The design language doc (principles, color, type, space, density, radius, elevation, motion, icons, voice, accessibility). Without `section`: table of contents. With it: that section (\"4\", \"Color\", \"voice-and-tone\"), or \"all\".","params":["section"]},{"name":"bridge_get_guidelines","description":"Rules for agents in this repo (AGENTS.md): always / ask before / never lists, token conventions, risk tiers, and what Bridge enforces. Pass `section` for one section verbatim, or \"all\".","params":["section"]},{"name":"bridge_propose_token_change","description":"Propose token edits as a reviewable change. Applies edits with minimal JSON diffs, validates, runs the contrast gate before/after, computes the risk tier and semver bump, writes a changeset and a designer-friendly PR body. Blocked (nothing written) if it adds validation errors or breaks a contrast pair. Suggest mode (the default unless bridge.config.json says \"changes\": \"direct\"): files a suggestion, a GitHub issue with the exact edits, the checks and the tier, status \"suggested\" with its number; owners approve it and a developer applies it (bridge_apply_suggestion). Direct mode: local repo, commits to a new local bridge/* branch without touching your working tree (never pushes); GitHub with token, new branch + draft PR labelled \"source: mcp\" and its tier. With branch or pr it writes to that branch whatever the mode. Never writes to main. Use dryRun to preview. Tell the user token changes are Tier 3.","params":["title","summary","edits","dryRun","branch","pr","jira","product","changes"]},{"name":"bridge_list_brands","description":"Brands of the repo: slug, name, default, primary action color and theme override files.","params":[]},{"name":"bridge_plan_brand","description":"Dry run of a new brand: the brand token file (generated primary and neutral ramps, radius and font roles), copied theme overrides, the bridge.config.json change, every contrast pair for the new brand in light and dark (ok, or the failing pairs), validation issues, the risk tier (always Tier 3, minor) and the PR body. Writes nothing.","params":["slug","name","from","primary","neutral","accent","link","radius","fonts","notes"]},{"name":"bridge_propose_brand","description":"Propose a new brand as a reviewable change. Same plan as bridge_plan_brand; blocked (nothing written) when an input is invalid or a contrast pair fails. Local repo: commits to a new local bridge/brand-<slug> branch without touching your working tree (never pushes). GitHub with token: new branch + draft PR labelled \"source: mcp\", \"tier: 3\" and \"tokens\". Never writes to main. Suggest mode (the default unless bridge.config.json says \"changes\": \"direct\"): one suggestion issue with the brand files instead, applied by a developer once approved. Tell the user a new brand is Tier 3: it needs design and tech owner approval.","params":["slug","name","from","primary","neutral","accent","link","radius","fonts","notes","dryRun","changes"]},{"name":"bridge_list_reviews","description":"Open pull requests on the repo (flagging the ones Bridge opened) and, locally, the bridge/* proposal branches.","params":["state","onlyBridge"]},{"name":"bridge_get_review","description":"Review a token change: designer-readable diff table, contrast before -> after, new validation errors, downstream impact, computed risk tier (and a warning if labelled lower), and for PRs the CI status, approvals and roles: who may approve design, approve tech and ship, with GitHub teams named and their size, and any team that cannot be read with the fix. Pass `pr` (GitHub) or `branch` (local proposal branch).","params":["pr","branch"]},{"name":"bridge_review_pr","description":"Post a review on a PR as the token owner: comment, approve or request changes, with a body. Kept for older prompts: bridge_review_branch does the same in designer words (an approval may have no text). Needs GITHUB_TOKEN. Only do this when the user asked for it; merging is a separate step (bridge_merge_branch), only when the person asks.","params":["pr","event","body"]},{"name":"bridge_get_history","description":"History of the design tokens: merged token-changing PRs and commits (local git: first parent of HEAD; GitHub: PR merge commits), newest first, each with author, date, why (changeset summary, PR or commit body), version it shipped in, risk tier, semver bump, breaking flag and change counts, plus the timeline of design system versions. Filter by token (path or group prefix), author, tier, version, breaking, dates or text.","params":["token","author","tier","version","breaking","since","until","query","limit","includeChanges"]},{"name":"bridge_get_token_history","description":"Every recorded change of one token, newest first, renames followed: value before and after per mode (raw and resolved CSS), who, when, the PR and why. Use before restoring a value or answering \"when did this change and why\".","params":["path","limit"]},{"name":"bridge_plan_revert","description":"What undoing a merged token change takes, computed against the CURRENT base branch (not a blind git revert): the inverse edits, conflicts where a token changed again later (with the later PR), changes already undone, contrast before and after, new validation errors, risk tier, files and the PR body (\"Revert: <title>\", links the original PR). Or pass restore to put one token back to an older value. Writes nothing.","params":["target","restore","resolutions","restoreConflicts","includeBody","limit","offset"]},{"name":"bridge_propose_revert","description":"Plans the revert (or restore) like bridge_plan_revert, then: local repo, commits to a new local bridge/* branch without touching your working tree (never pushes); GitHub with token, new bridge/* branch and a PR labelled revert and its tier (draft for Tier 2 and 3). Blocked when it would add validation errors or break a contrast pair. Never writes to main. Suggest mode (the default unless bridge.config.json says \"changes\": \"direct\"): one suggestion issue with the files instead, applied by a developer once approved. Show the user the plan and its conflicts first.","params":["target","restore","resolutions","restoreConflicts","dryRun","changes"]},{"name":"bridge_scaffold_component","description":"Generate a new component folder per the repo checklist: Name.tsx (forwardRef, typed props), Name.module.css (existing tokens only), stories with AllStates, docs.json with the reference component's keys, a keyboard + axe test when interactive, index.ts. Locally writes the files (never overwrites); remotely returns them. New components are Tier 2: confirm with the user first.","params":["name","family","summary","element","interactive","basePrimitive","write"]},{"name":"bridge_visual_impact","description":"Screenshots what a design system change touches, before and after, and pixel-diffs them. Picks the impacted stories from the changed token values (CSS variables each component reads) and changed component files, plus the app screens (admin back office, both tenants), in every brand and theme. Builds Storybook and the app at both refs, so a full run takes minutes and needs Chrome; plan: true answers in seconds with the selection only. Returns counts, the largest changes with paths to before | after | diff composites, and the manifest path. Local repos only.","params":["base","head","out","only","plan","threshold","maxStoriesPerComponent"]},{"name":"bridge_audit","description":"Measure how a product codebase uses this design system (local only). Reads CSS, SCSS, Less, TS/JS, TSX/JSX, and Astro, Vue and Svelte files (template markup, frontmatter and <script> blocks, <style> blocks). Finds hardcoded colors, spacing, radii, shadows, durations, z-index and fonts in style sheets, style attributes, style/sx/styled objects, CSS-in-JS and Tailwind classes, each with the closest token (colors by deltaE across every mode) and a confidence; and in JSX and template markup, DS components versus foreign UI libraries (MUI, react-admin, Radix, shadcn/ui...), native elements a DS component should render, and re-created DS components. Hidden inputs and elements inside <noscript> do not count. A `bridge-audit-ignore-next-line: reason` comment on the line above leaves one exception out; an allowlist file lists known file:line exceptions; both need a reason and stay listed under `ignored`. Returns token and component adoption, counts by category, top files and top fixes; for a single file (or findings: true) the findings with line numbers.","params":["path","baseline","label","limit","findings","allowlist"]},{"name":"bridge_list_requests","description":"Component change requests: GitHub issues labeled component-change (from Figma, Bridge Studio, the CLI or an AI tool). Each row has the number, component, kind, title, status (requested: open, no pull request; in-progress: an open pull request says \"Closes #n\"; done: closed as completed or by a merged pull request; declined: closed otherwise), url and linked pull requests.","params":["status","component","limit"]},{"name":"bridge_get_request","description":"One request, ready to implement: the parsed request (component, kind, summary, changes asked, Figma link, images), its status and linked pull requests, the component files found under the components directory, the agent rules file, and `brief`: the prompt to implement it in this repo. Then work on a branch named agent/request-<n> and open a pull request whose body says \"Closes #<n>\". If the request is unclear, comment on the issue instead of guessing.","params":["number","branch"]},{"name":"bridge_list_build_requests","description":"Build requests: structure changes pushed from Figma (a new variant, option, layout or component) that developers build, as GitHub issues labeled component-change and bridge-build, plus library branches from Figma waiting for a developer. Read only: developers split and track the work in GitHub or Jira, Bridge reads it. Each row has the number, component, title, status (requested: nobody assigned; picked-up: assigned; in-progress: a linked draft pull request; in-review: a linked pull request ready for review; shipped: merged or closed as completed; not-planned), who builds it, its age, stale (requested for more than 7 days), the linked pull request and the Jira key.","params":["filter","component","limit"]},{"name":"bridge_get_build_request","description":"One build request, ready to build: what the designer sent (the request, before and after images, props needed, the spec when the issue keeps it), the status timeline, the linked pull request, the Jira key, the component files and `brief`, the prompt to build it in this repo. Build it on a branch named agent/build-<n> and open a pull request whose body says \"Closes #<n>\". The design is approved in Figma: build what it shows, comment on the issue when something is unclear.","params":["number"]},{"name":"bridge_create_request","description":"File a component change request as a GitHub issue labeled component-change (source: mcp), in the same format as Figma and Bridge Studio requests. Use it for component work (new component, variant, prop, structure, visual, token binding, bug) that someone should implement in code; token value changes go through bridge_propose_token_change instead. Needs GITHUB_TOKEN with issues write. dryRun returns the issue without creating it. Only create one when the user asked for it.","params":["component","kind","title","summary","changes","figmaUrl","exploration","product","dryRun"]},{"name":"bridge_pending_drafts","description":"Change texts a designer asked their own Claude to write from the DS Bridge Figma plugin (\"Draft with my Claude\"), waiting on the bridge-requests branch. Call it when the user says \"Draft my Bridge changes\". Returns the pending sessions (newest first) with each item: scope (request: a component change request; push: a pull request description of token edits; docs: component docs sections from Bridge Studio, with a brief holding the full prompt), component, kind, the change table, token edits, the designer's notes, the deterministic starting draft, the change lines to write (one per component change, with an id, its changes and a starting line), a brief, and the before and after image links; the images themselves follow as image content when small enough. Look at the before and after images, then write what changes for developers and why it matters for people who use the component. Sentence case, start the title with a verb, no em dash, no invented numbers, names or reasons: if the reason is unknown, leave it out. Write one short sentence per change line from the images: what changed for developers (the part, the variant, the values you can read), for example \"Icon added after the label in primary sm: Pencil, 16px\", and the title of the request it becomes, for example \"Add an icon after the label\". Then call bridge_write_drafts with one result per item id: title at most 70 characters, summary at most 3 sentences, lines (one per change line id) with a line of at most 120 characters and a title of at most 70. Docs items: read the brief. Sections to check (the code changed after they were written) go in the answer ONLY when something in them is no longer true for the code (a wrong or removed prop, a removed state, changed behavior), fixed with the writer's wording kept elsewhere; leave accurate ones out (a missing key means unchanged, \"docs\": {} when all are accurate). Otherwise write only the sections its task names (summary a string; whenToUse, whenNotToUse, accessibility, contentGuidelines lists of strings; dos and donts lists of {\"title\", \"text\"}) from the facts it quotes, never a prop, variant or keyboard behavior that is not in the code, never anatomy; answer with \"docs\": {sections}. A selection task rewrites one passage: answer with \"replacement\": \"the passage\". No title or summary for docs items.","params":["sessionId","images"]},{"name":"bridge_write_drafts","description":"Write the titles, summaries and change lines (or, for docs items, the docs sections or the rewritten passage) you drafted for a session from bridge_pending_drafts. Docs results show up on the Library page marked \"Drafted by Claude\" for review, cleaned to the docs.json shapes (no em dash; only the sections the item asks for). The DS Bridge Figma plugin fills change texts in within seconds, marked \"Drafted by Claude, review before sending\"; it never overwrites text the designer typed meanwhile. Each change line becomes the main line of its component row and the first line of its request; its title becomes that request's title. Texts are cleaned to the contract (no em dash, titles at most 70 characters without a trailing period, summary at most 3 sentences, each line at most 120 characters). Results without lines, or lines without a title, still work. Needs GITHUB_TOKEN with contents write. Writes only the session file on the bridge-requests branch, never main.","params":["sessionId","results"]},{"name":"bridge_start_exploration","description":"Start an exploration: a branch explore/<slug> from the default branch with a note file, and a DRAFT pull request labeled exploration. When the designer says they want to explore, try or prototype something, start one right away: take the name from what they said, never ask them for a purpose, a brief or a use case. For a product with its own repository (bridge.config.json products[].repo, see bridge_list_products), the branch and the draft pull request are created IN THAT PRODUCT REPOSITORY by default, so developers check it out in their own environment; the library arrives there as the npm package (npm i @bridge-ds/react@<snapshot> for unreleased library changes). A product with a design team's copy (products[].design.repo) gets it in that copy instead, never in the developers' repository; anyone on the team who can edit starts it there, also a designer who joined with their email (Bridge writes for them). Otherwise (a product folder of the design system repo, the demo workspace) it is created in the design system repository with per-branch previews and a snapshot package. If Bridge cannot reach the product repository, the error says so: tell the designer plainly that an admin needs to connect that product to Bridge, and only start it in the design system repository (where: \"library\") if they choose that. Never merged as is: a person says \"Done exploring\" (bridge_promote_exploration) to hand it to developers. GitHub with GITHUB_TOKEN: branch and draft pull request. Local without a token: a local branch only, nothing pushed. dryRun previews it.","params":["name","purpose","useCase","experimental","product","where","mockup","mockupName","dryRun"]},{"name":"bridge_list_explorations","description":"Explorations (pull requests on explore/* branches) of the design system repository and of every product with its own repository (bridge.config.json products[].repo, one read each; a product repository Bridge cannot reach is left out, bridge_list_products says which): ref (\"#12\", or \"shop#12\" in a product repository: pass it as is to the other exploration tools), repo, name, purpose, status (active: running; ready: done exploring, waiting for code; building: developers push to it; shipped: merged; promoted: sent to review the older way; closed), archived, author, last update, for open ones the preview links Vercel reports (url null while it has not reported one yet) and the install command a product staging branch uses, read from the preview comment on the pull request (state building until the snapshot of the latest commit is published, never a guessed command), and the component requests implemented on each. Archived ones are left out unless archived is true. Locally, also explore/* branches without a pull request.","params":["state","archived","mine"]},{"name":"bridge_continue_exploration","description":"Pick an exploration up where it was left, when the person says \"Continue Bridge exploration #12\" (Studio's Continue line; shop#12 for a product with its own repository) or asks to continue one by name. Resolves it, switches the local checkout of its repository to its explore/ branch when nothing is uncommitted (checkout: false leaves the working tree alone; remote: the write tools take \"branch\"), and returns where it stands: stage (not-started: nothing built beyond the Bridge note; exploring; handed: done exploring or later), whereItStands (one or two plain sentences), the last 3 activity events, the changed files, the missing pieces when recorded, the lines to continue it in an AI tool, and startFrom when it starts from a page of a live product (a product added from its address): then follow next, which says to open that page in the browser and rebuild it with the library only before exploring. It also returns notes, the handover the last person left (\"Where it stands\": context, decisions, edge cases per component, open questions, next step): read them first, keep the decisions already taken, and start from notes.nextStep. Start your answer with where it stands, without technical words, then propose that next step or ask what to do next. Read only on GitHub.","params":["exploration","checkout"]},{"name":"bridge_exploration_to_figma","description":"What Claude needs to rebuild an exploration in a new page of the team's Figma file, when the person says put or send this exploration in Figma (Studio's line: \"Put Bridge exploration shop#12 in Figma\"). Reads only: Bridge never writes to Figma and holds no Figma token. You build it afterwards with your own Figma connector (use_figma, Plugin API). Returns the Figma file (or, when the team has none, a sentence for the designer pointing to Settings, Figma file), the page name, the source of the changed screens, each Library component they use with its bridge.components.json link (node, key when known, property map, how to reach it), components with no link, the product's own components, the preview to look at, which ids work in which file, the recipe and the gaps to report. End with the page link and the gaps; save the link with bridge_save_exploration notes.figmaPage while it is still being explored. For Can edit and Admin, email members included.","params":["exploration"]},{"name":"bridge_save_exploration","description":"Save prototype code on an exploration: one commit with the files you send on its explore/<name> branch, so its preview updates in a few minutes. Use it after each step you build, sending every changed file whole (content, or contentBase64 for an image or a font; delete: true removes one). It works without a GitHub access of your own: Bridge saves through the person's Bridge account, also for a designer who joined with their email (Can edit or Admin; a Reader saves nothing). For them any file goes in a product exploration; in an exploration of the design system repository itself only design files (tokens, docs, assets), since its leads change the library. git push stays for whoever has their own access to the repository. Never the main branch, never a merge or a force; CI settings (.github), hosting settings (vercel.json, .vercel) and node_modules are refused. At most 200 files and 2 MB per save. Only when the person asked to build or change something on that exploration. With each save, also send notes (the exploration's \"Where it stands\", the handover for whoever carries on, another designer or another AI tool): the decisions taken in this step, the edge cases you covered or found still open per component (state, covered, a short note), new open questions and answeredQuestions, and nextStep, in plain words a designer reads, no code. Send only what changed: lists are added to, a text section replaces the old one, and what a person wrote by hand stays. Notes alone (files left out) save too. Pass notes only through notes, never write the note file (.bridge/explorations/<name>.md) yourself. Also pass screen: the route of the screen you changed in the product, as its address inside the preview (path, query and hash: /#/orders/12, /settings/billing, /?workspace=new#/), so Studio's Open the preview and its picture land on the change instead of the home page; pass it again when the change moves to another screen.","params":["exploration","message","files","notes","screen","mockupName"]},{"name":"bridge_promote_exploration","description":"\"Done exploring\" on an exploration (explore/<name>), as in Studio (the tool keeps its old name). It never closes, merges or marks the draft ready for review: the pull request stays open so its preview link keeps working for the designer, the DS lead, stakeholders and developers. The pieces you pass (ids from bridge_missing_pieces; ask the person which ones) each become a request for the DS lead with a link to the preview; pieces left out are not proposed. For an exploration in a product's own repository (shop#42) the requests are filed in the design system repository, where the DS lead works, and link back to the product pull request; its status keeps following that pull request. Then the exploration label and note go and ready-for-devs comes: developers take the branch (git fetch origin, then git checkout explore/<name>) as a starting point, never as code ready to ship. The exploration's notes go with it: their decisions, edge cases and open questions become the design spec in the developers' task. Their pushes read \"Being built\", the merge \"Shipped\". Said again later, it only sends newly picked pieces. dryRun shows what it would send. Needs GITHUB_TOKEN (contents, pull requests and issues: write). Only when the person asked.","params":["exploration","pieces","dryRun"]},{"name":"bridge_archive_exploration","description":"Archive an exploration, as in Studio: the archived label on its still open pull request hides it from the default lists, home and counts (bridge_list_explorations with archived: true lists them). The preview link keeps working. unarchive: true brings it back. Prefer it to bridge_close_exploration, which removes the preview. Needs GITHUB_TOKEN (pull requests or issues: write). Only when the person asked.","params":["exploration","unarchive"]},{"name":"bridge_close_exploration","description":"Close an exploration without merging it. Its branch stays on GitHub, but closing removes its preview prerelease and visual images: archive it instead (bridge_archive_exploration) unless the person explicitly wants it closed. Needs GITHUB_TOKEN (pull requests: write). Only when the person asked.","params":["exploration"]},{"name":"bridge_missing_pieces","description":"Check a product branch (an exploration started for a product) against the library: the adoption audit on each product file it changes, at its start and at its head, keeps what the branch added. New hardcoded values become token pieces beside the closest token, values written on a library component become a variant of it (\"Badge: overdue tone\"), components from another UI library with no library equivalent become new components. Values equal to a token and components the library has are fixes, not pieces. With record: true, saves the result in the branch description, where Bridge Studio shows it (needs GITHUB_TOKEN, pull requests: write). Run it when a designer finishes exploring with you, then offer to open a library branch for each piece.","params":["pr","record"]},{"name":"bridge_open_library_branch","description":"Turn one recorded missing piece into a library branch linked to the product branch, as Bridge Studio does: a token piece opens a token change (same gate and body as bridge_propose_token_change, a draft for design and tech review) and the product branch takes its preview; a variant opens a library exploration with the brief to build it (build it there, then bridge_use_library_preview); a new component opens a component request. Both sides link: the library side says \"Needed by\" the product branch (label needed-by-product), the product branch records it. Suggest mode (the default unless bridge.config.json says \"changes\": \"direct\"): a token piece becomes a suggestion and a variant a component request, no branch; needs Issues write. Direct mode needs GITHUB_TOKEN (contents, pull requests and issues: write). dryRun shows what it would open. Only when the person asked.","params":["pr","piece","usePreview","dryRun","changes"]},{"name":"bridge_product_branch","description":"A product branch as Studio shows it: the summary sentence, each linked library branch with its status and reviewers, what its preview means for the product branch and the next action, and the pieces with no library branch yet.","params":["pr"]},{"name":"bridge_use_library_preview","description":"The product branch takes the latest commits of the library branch of a piece (Bridge merges it in), so the product preview shows the real library change before it ships. A conflict is left to a developer. Needs GITHUB_TOKEN (contents: write). Only when the person asked.","params":["pr","piece"]},{"name":"bridge_switch_to_published","description":"Once its library branches shipped, bring main into the product branch (GitHub update branch): it stops carrying the library change and uses the shipped one. Token conflicts go through bridge_update_from_main. Needs GITHUB_TOKEN (contents and pull requests: write). Only when the person asked.","params":["pr"]},{"name":"bridge_figma_changes","description":"The library branches the DS Bridge Figma plugin opened for components changed in Figma (label from-figma), with where each stands: an exact token change (no AI, contrast gated), or a branch carrying the spec, waiting for Claude AI to draft the code, then drafted by Claude AI and reviewed by a person.","params":["state"]},{"name":"bridge_get_figma_change","description":"One library branch sent from Figma: its spec (variant matrix, properties, bound variables per variant, layers, what code gave Figma before, the exact token swaps) and the brief to draft the code on that branch. Check out the branch, write the TSX, CSS module, examples, docs and changeset, run npm run specs and the tests, push, then call bridge_mark_figma_change_drafted.","params":["pr"]},{"name":"bridge_mark_figma_change_drafted","description":"After you pushed the code for a component change from Figma to its branch: mark its pull request ready for review, label it drafted-by-claude (no longer waiting-for-claude) and say so in its description, in one step, for a person to review. When GitHub refuses ready for review, the labels stay as they were and the error says why. Refused while the branch only carries the spec. Needs GITHUB_TOKEN (pull requests: write).","params":["pr"]},{"name":"bridge_push_figma_component","description":"What the DS Bridge plugin Push tab does, from a structured diff of a Figma component (the v 1 spec shape: component, figmaName, coded, kind, title, summary, changes, rebinds, needsCode, unknown, variantAxes, properties, bindings, anatomy). An exact token swap on a component token used nowhere else opens a token change (contrast gated, reviewed like any token change); anything that needs code opens a draft branch with the spec, waiting for Claude AI; detached layers, raw values and variables the library lacks are listed with what to do and never sent. Suggest mode (the default unless bridge.config.json says \"changes\": \"direct\"): a token suggestion or a component spec suggestion instead of a branch, Issues write only. dryRun shows the route. Direct mode needs GITHUB_TOKEN (contents and pull requests: write). Only when the person asked.","params":["diff","dryRun","changes"]},{"name":"bridge_figma_gaps","description":"The components whose Figma build differs from their story (Differs) or cannot be checked (Can't check, with the reason), from the latest Check fidelity run of the DS Bridge plugin (the story shots are the referee), else from the measure's own check; a status fix in figma-fixes.json shows with its reason. Read only.","params":["measured","fidelity","fixesFile"]},{"name":"bridge_get_gap_case","description":"One component's gap case: per differing variant, its story, args, state, shot and every difference with the part id, property, expected (code) and actual (Figma) and the delta in px. Read only.","params":["component","measured","fidelity","fixesFile"]},{"name":"bridge_propose_component_map","description":"Proposes bridge.components.json entries that link Library components to their Figma components, and opens them for review like other Bridge changes (a suggestion, or a draft pull request in direct mode; never main). Read the Figma side first with the Figma connector: open the team's Figma file (bridge_get_config, figma.file) and list its components and component sets with their node ids and variant properties, and their keys whenever your connector gives them (.key in the Plugin API): without a key, a link only works inside that same Figma file. Matches by name, then by variant properties; ambiguous matches are listed, never guessed, and links a person already made are kept. dryRun shows the file and the matches. Only when the person asked.","params":["components","file","summary","dryRun","changes"]},{"name":"bridge_list_products","description":"The products of this design system (bridge.config.json \"products\": name, repo or folder, preview link pattern, framework; for a product with its own repository, connection: connected, read-only or not-connected, where not-connected means its explorations are left out of the lists until an admin installs the Bridge GitHub App there; access says in one sentence whether this person can start and save its explorations, trust it over connection) and the one the current folder or repo belongs to, which tools that start work use when no product is given. Ask the person which product when it is not obvious.","params":[]},{"name":"bridge_what_needs_me","description":"The review queue, as Studio counts it (open branches, without running explorations and the release automation), each with its status in designer words, and first the ones where the person acts now: an approval they can give, their own branch blocked, ready for them to merge. Needs GITHUB_TOKEN to know who \"me\" is; without it, the queue only.","params":["limit"]},{"name":"bridge_branch_status","description":"One branch in review as Studio shows it: its product, status (draft, in review, needs design or tech approval, blocked by tests, conflict, ready to merge, merged, closed), approvals (Tier 1: one owner approval; a branch that applies an approved suggestion carries its approvals), tests, how it stands against main, whether the person may merge it (the same verdict as the Merge button and status chips in Studio), and the next step. For the token diff and contrast, use bridge_get_review.","params":["pr"]},{"name":"bridge_list_comments","description":"The conversation on a branch and its line comment threads, with the ids to reply to (bridge_comment with replyTo).","params":["pr"]},{"name":"bridge_try_branch","description":"Try a branch before it merges: the preview link of each product Vercel reported for it (the admin demo opens with the Bridge toolbar on, as \"Try it in the product\" in Studio), the other previews, and \"Share with a product team\": the install command a product team runs in a staging branch, or why there is none yet, with a ready-to-paste message. Never a guessed link. Writes nothing.","params":["pr"]},{"name":"bridge_combine_branches","description":"Combined preview of 2 to 4 token branches, as \"Try together\" in Studio: each branch's own token edits on the latest main, the tokens two branches set differently (pick one per key with picks), and the links that open the combination (the admin demo with the Bridge toolbar, the library views). Branches that change code are refused. Writes nothing.","params":["prs","picks"]},{"name":"bridge_get_settings","description":"What Studio Settings shows that is safe to read: who approves design and tech (GitHub teams named with their size), who may merge, the owner override (who, what reason), whether main is protected, the products, the preview apps and the visual impact mode. Never tokens or secrets.","params":[]},{"name":"bridge_figma_coverage","description":"Which components are in Figma, in Studio's words (Yes, Drafted, Auto layout, Not yet with the reason), and whether code images exist for the fidelity check the DS Bridge Figma plugin runs (its scores live in Figma).","params":["component"]},{"name":"bridge_send_for_review","description":"Ask for review: a draft branch becomes ready for review, as \"Mark as ready\" in Studio. Its author only. Needs GITHUB_TOKEN (pull requests: write).","params":["pr"]},{"name":"bridge_back_to_draft","description":"Take a branch out of review back to draft, as in Studio's More menu. Its author only. Needs GITHUB_TOKEN (pull requests: write).","params":["pr"]},{"name":"bridge_review_branch","description":"Approve, request changes or comment on a branch, as the review box in Studio, on the version the person saw, under their GitHub account. Request changes and comment need a text that says what to change; an approval may have none. Only when the person asked. Needs GITHUB_TOKEN (pull requests: write).","params":["pr","decision","body"]},{"name":"bridge_ask_someone_else","description":"Ask the other people who can give the missing approvals to review a branch, as \"Ask someone else to review\" in the Studio review queue, and take the person off its requested reviewers. Never the person or the author. Only when the person asked; dryRun says who would be asked. Needs GITHUB_TOKEN (pull requests: write).","params":["pr","dryRun"]},{"name":"bridge_comment","description":"Post a comment on a branch, or reply in the thread of a line comment (replyTo: its id from bridge_list_comments). Needs GITHUB_TOKEN (pull requests: write).","params":["pr","body","replyTo"]},{"name":"bridge_merge_branch","description":"Merge a branch into main through the same gate as Studio's Merge button: tests pass, the approvals its tier needs (Tier 1: one owner approval; Tier 2 and 3: design and tech; a branch that applies an approved suggestion with Closes #n carries its approvals while the suggestion stays approved and the tier is not higher), no changes requested, no conflict, not a draft or an exploration, and the person holds the right to ship (governance.rights). When it is blocked, the error says by what. Owner override: pass overrideReason when only approvals are missing and the person is an owner named in governance.override.allowed; the reason is always required (at least minReasonLength characters, 20 by default) and posted on the branch first. Only when the person explicitly asked to merge; dryRun checks without merging. Needs GITHUB_TOKEN (contents and pull requests: write); GitHub's own branch rules still apply.","params":["pr","overrideReason","dryRun"]},{"name":"bridge_close_branch","description":"Close a branch without merging it, as in Studio's More menu. Its work stays on GitHub and it can be reopened. Explorations close with bridge_close_exploration. Only when the person asked. Needs GITHUB_TOKEN (pull requests: write).","params":["pr"]},{"name":"bridge_reopen_branch","description":"Reopen a closed branch, with Studio's rule: its author or an owner with write access, and only while its work is still on GitHub. Needs GITHUB_TOKEN (pull requests: write).","params":["pr"]},{"name":"bridge_update_from_main","description":"Bring the latest main into a branch, as \"Update from main\" in Studio. Nothing conflicts: GitHub updates it. Only token files conflict: the tokens changed on both sides come back with keys; pass choices (\"mine\" keeps the branch value, \"theirs\" uses main's; tokens with a default keep the branch value) and Bridge commits the resolution. Code conflicts stay with a developer on GitHub. dryRun shows what would happen. Needs GITHUB_TOKEN (contents and pull requests: write).","params":["pr","choices","dryRun"]},{"name":"bridge_save_docs","description":"Save a component's usage guidance (docs.json sections: summary, whenToUse, whenNotToUse, dos, donts, accessibility, contentGuidelines, anatomy, preview) the way the Library edit mode does: merged into the docs on the branch, cleaned and checked (a summary, no empty items, no em dash). Without pr: a new branch sent for review (docs only: one owner approval, patch release note), with an optional Jira key and product. With pr: one commit on that open branch. Suggest mode (the default unless bridge.config.json says \"changes\": \"direct\"), without pr: a docs suggestion issue instead of a branch (Issues write only). dryRun returns the file. Direct mode needs GITHUB_TOKEN (contents and pull requests: write). Prose you drafted carries \"draftedBy\": \"claude\" and \"needsReview\": true so a reviewer accepts it in Studio.","params":["component","docs","pr","title","notes","jira","product","dryRun","changes"]},{"name":"bridge_list_suggestions","description":"Suggestions in the repo: GitHub issues labeled bridge-suggestion, each an exact change (tokens, docs, a component spec, a brand, a revert, settings) that the owners approve and a developer applies. Each row has the number, title, kind, tier, status (needs-review, changes-requested, approved, applying, applied, declined, outdated) and linked pull requests. Statuses here come from labels, except that an open one whose change no longer applies to main reads outdated; bridge_get_suggestion counts the approvals.","params":["status","state","kind","limit"]},{"name":"bridge_get_suggestion","description":"One suggestion: the change (tokens before and after, docs, component spec, files), the checks when suggested, links, its version (payloadSha: what approvals bind to), who approved it, which approvals are missing for its tier, reviews that no longer count (an older version, or not an owner), whether the machine-readable block was edited by hand, linked pull requests, and for a component spec the brief to implement it.","params":["number"]},{"name":"bridge_create_suggestion","description":"File any change as a suggestion from its payload (schema bridge.suggestion/1: kind, title, summary, and tokens edits, docs, componentSpec or files). Missing schema, source, date, base commit and checks are filled. The paths are checked against what the kind may change and the guardrail files before anything is sent. For token, docs, brand, revert and Figma changes prefer their own tools, which plan and check the change first. Needs GITHUB_TOKEN with Issues write. dryRun returns the issue. Only when the person asked.","params":["payload","labels","dryRun"]},{"name":"bridge_review_suggestion","description":"Approve, request changes on, comment on or decline a suggestion, as the person whose GitHub token the server has. Approvals and requested changes count only from the owners in bridge.config.json (read from the default branch) and only on the version reviewed: pass payloadSha from bridge_get_suggestion so a newer version is never approved by mistake. Request changes and decline need a message. Decline closes the issue as not planned. \"override\": the owner override (docs/GOVERNANCE.md): an owner governance.override allows approves their own suggestion as owner when nobody else can review it, with the reason in message (at least the minimum length); it is recorded on the suggestion. Needs GITHUB_TOKEN (Issues: read and write). Only when the person asked, with the decision they asked for.","params":["number","event","message","role","payloadSha"]},{"name":"bridge_apply_suggestion","description":"Apply a Bridge suggestion to today's code (\"Apply Bridge suggestion #42\"). Bridge checks the paths, the approvals of the owners on its current version, re-applies token edits on the current tokens, merges files, re-runs validation, contrast and the tier, and stops on a conflict, a missing approval or a check that would fail. Local repo: mode \"dry-run\" (the plan and the diff, nothing written; run it first), \"branch\" (default: one commit on a new local branch, working tree untouched, never pushes), \"write\" (into the working tree, refused over uncommitted changes) or \"patch\" (a git format-patch text). Remote repo: the plan and the files to write yourself. Once a branch or files exist, it records on the issue that it is being applied (needs Issues write). Then push and open a pull request whose body says \"Closes #<n>\", and call bridge_link_suggestion. acceptEdited and forceUnapproved only when the person asked.","params":["number","mode","acceptEdited","forceUnapproved","base","branch"]},{"name":"bridge_link_suggestion","description":"Record the pull request (or branch, or commit) that applies a suggestion: a comment on the issue and the \"suggestion: applying\" label. Warns when the pull request does not say \"Closes #<n>\": add it so the suggestion closes when it merges. Needs GITHUB_TOKEN (Issues: read and write).","params":["number","pr","branch","commit"]}],"toolsHash":"11b1b22cb9ee8d3c85a8f0757941357dd55d9918a12f3c3155bee8b149397177","wrote":[],"callsAt":"2026-11-16T11:34:07.801Z","calls":[{"tool":"bridge_get_config","ok":false,"ms":27,"bytes":0,"error":"tool reported an error: Error: No DTCG token files found (JSON files with \"$value\"). Write bridge.config.json by hand."},{"tool":"bridge_whoami","ok":false,"ms":33,"bytes":0,"error":"tool reported an error: Error: No DTCG token files found (JSON files with \"$value\"). Write bridge.config.json by hand."},{"tool":"bridge_get_claude_design_system","ok":true,"ms":281,"bytes":64893},{"tool":"bridge_list_tokens","ok":false,"ms":16,"bytes":0,"error":"tool reported an error: Error: No DTCG token files found (JSON files with \"$value\"). Write bridge.config.json by hand."},{"tool":"bridge_list_components","ok":false,"ms":14,"bytes":0,"error":"tool reported an error: Error: No DTCG token files found (JSON files with \"$value\"). Write bridge.config.json by hand."}],"host":{"commit":"eaaffffaf52255d1b77dc4aacffdfaf353f0c12c","run":"https://github.com/itsHaddad/bragproof/actions/runs/43857070216"},"network":{"names":["registry.npmjs.org"],"conns":[],"callNames":["bridge.floriangouloubi.com"],"callConns":[]}},"summary":{"outcome":"started","needs":[],"contacts":[],"flags":[],"tools":79,"wrote":0,"callsTried":5,"callsAnswered":1,"callContacts":["bridge.floriangouloubi.com"]},"history":[{"package":"@bridge-ds/mcp","version":"0.17.0","ranAt":"2026-11-16T11:34:01.034Z","outcome":"started","tools":79,"contacts":0,"flags":0,"serious":0,"toolsHash":"11b1b22cb9ee8d3c85a8f0757941357dd55d9918a12f3c3155bee8b149397177"}],"page":"https://bragproof.smaverk.com/r/%40bridge-ds/mcp"}