brandpilot-mcp

MCPcommunitylive
v0.3.1UnknownMITUpdated 4d agonpmGitHub

MCP server for BrandPilot: with a workspace API key it proxies the hosted BrandPilot MCP (brands, design context, repo rules pack, Claude Design kit); without one it serves the public design-system tools - from Claude Code, Codex, Cursor or any MCP client

Endpoint healthlive
checked 16h ago · 289ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
16Downloads/wk
4d agoLast update
Reads these credentials
  • BRANDPILOT_API_KEYAPI keyoptional

    Workspace API key (bp_live_...) from BrandPilot. When set, the server proxies to the hosted BrandPilot MCP and serves its full tool list.

  • DESIGNFLOW_HANDOFF_KEYAPI keyoptional

    Deprecated legacy design handoff key, retired on 2027-01-31; use BRANDPILOT_API_KEY. Ignored when BRANDPILOT_API_KEY is set.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.3.1
Sourcenpm+mcp-registry
npmbrandpilot-mcp
GitHubaquaminh/brandpilot-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv0.3.1 · todayHow well does this scan work?
EvalsNone
IndexedOct 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev0.3.1 · 9h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_systemsNo description published

This tool published no description. Forge does not invent one.

get_system_adoptionNo description published

This tool published no description. Forge does not invent one.

get_system_tokensNo description published

This tool published no description. Forge does not invent one.

get_agent_promptNo description published

This tool published no description. Forge does not invent one.

get_design_handoffNo description published

This tool published no description. Forge does not invent one.

get_design_prompt_packNo description published

This tool published no description. Forge does not invent one.

import_design_artifactsNo description published

This tool published no description. Forge does not invent one.

finish_external_designAccept all pending external-import drafts in one stroke (default false)

Accept all pending external-import drafts in one stroke (default false)

No input schema was published for this tool.

1 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for BrandPilot: with a workspace API key it proxies the hosted BrandPilot MCP (brands, design context, repo rules pack, Claude Design kit); without one it serves the public design-system tools - from Claude Code, Codex, Cursor or any MCP client

Keywords
mcpmodel-context-protocolbrandpilotdesign-system
Alternatives
Comparing tool surfaces…

Tools exposed

8 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-17 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in design tools