Skip to content
Back to search

brilliant

MarketplaceWorks with Claude CodeGitHub

Brilliant MCP: connect Claude Code, Cursor, Codex and any MCP client to the Brilliant design canvas

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/brilliant-hq/brilliant-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/brilliant-hq/brilliant-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/brilliant-hq--brilliant-mcp/badge.svg)](/listings/brilliant-hq--brilliant-mcp)

HTML

<a href="/listings/brilliant-hq--brilliant-mcp"><img src="/api/listings/brilliant-hq--brilliant-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

| Client | One line | |---|---| | Claude Code | `claude mcp add brilliant -- npx -y @brilliant-hq/mcp` | | Cursor | `npx -y @brilliant-hq/mcp install cursor` | | VS Code | `code --add-mcp '{"name":"brilliant","command":"npx","args":["-y","@brilliant-hq/mcp"]}'` | | Codex | `codex mcp add brilliant -- npx -y @brilliant-hq/mcp` | | Gemini CLI | `gemini mcp add brilliant -- npx -y @brilliant-hq/mcp` | | Anything else | `npx -y @brilliant-hq/mcp install <client>` |

`install <client>` knows claude-code, cursor, vscode, codex, gemini, antigravity, windsurf, zed, opencode, amp and claude-desktop. Any other MCP client takes the standard stdio entry:

{ "mcpServers": { "brilliant": { "command": "npx", "args": ["-y", "@brilliant-hq/mcp"] } } }

Requires Node 20 or newer. No API key.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 24 lines
  1. {
  2. "name": "brilliant",
  3. "owner": {
  4. "name": "Brilliant",
  5. "email": "hello@brilliant.design"
  6. },
  7. "metadata": {
  8. "description": "Brilliant: design with your agent on a real vector canvas."
  9. },
  10. "plugins": [
  11. {
  12. "name": "brilliant-design",
  13. "source": "./plugin",
  14. "description": "Design with your agent on Brilliant's real vector canvas: screens, components and design systems you both edit.",
  15. "category": "design"
  16. },
  17. {
  18. "name": "brilliant",
  19. "source": "./plugin-hosted",
  20. "description": "Design pages, app screens, dashboards and posts as editable layers on Brilliant's hosted canvas. Works in Claude chat, Cowork and Claude Code.",
  21. "category": "design"
  22. }
  23. ]
  24. }
README.md · README · 186 lines
  1. # Brilliant Design: a design canvas for coding agents (MCP server)
  2. Design canvas for coding agents: real editable vectors, auto layout, components, export to code.
  3. ```
  4. npx -y @brilliant-hq/mcp install <client>
  5. ```
  6. **Your coding agent designs with you on a real vector canvas.** This is the local
  7. MCP server for [Brilliant](https://brilliant.design), the design tool whose canvas
  8. you and your agent both edit: the agent lays out the screen, you drag, retype and
  9. restyle it, and the agent sees your changes and keeps going.
  10. `@brilliant-hq/mcp` is a small local router. It connects any MCP client over stdio
  11. to a Brilliant tab in your browser or to the Brilliant desktop app, entirely on
  12. `127.0.0.1`. **Zero bytes of MCP or design data touch Brilliant's servers.**
  13. ## Install
  14. | Client | One line |
  15. |---|---|
  16. | Claude Code | `claude mcp add brilliant -- npx -y @brilliant-hq/mcp` |
  17. | Cursor | `npx -y @brilliant-hq/mcp install cursor` |
  18. | VS Code | `code --add-mcp '{"name":"brilliant","command":"npx","args":["-y","@brilliant-hq/mcp"]}'` |
  19. | Codex | `codex mcp add brilliant -- npx -y @brilliant-hq/mcp` |
  20. | Gemini CLI | `gemini mcp add brilliant -- npx -y @brilliant-hq/mcp` |
  21. | Anything else | `npx -y @brilliant-hq/mcp install <client>` |
  22. [![Add to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/install-mcp?name=brilliant&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBicmlsbGlhbnQtaHEvbWNwIl19)
  23. [![Install in VS Code](https://img.shields.io/badge/VS_Code-Install_Brilliant_MCP-0098FF?logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522brilliant%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522%2540brilliant-hq%252Fmcp%2522%255D%257D)
  24. `install <client>` knows claude-code, cursor, vscode, codex, gemini, antigravity,
  25. windsurf, zed, opencode, amp and claude-desktop. Any other MCP client takes the
  26. standard stdio entry:
  27. ```json
  28. { "mcpServers": { "brilliant": { "command": "npx", "args": ["-y", "@brilliant-hq/mcp"] } } }
  29. ```
  30. Requires Node 20 or newer. No API key.
  31. ## Codex plugin
  32. This repository is also a Codex plugin marketplace. The plugin lives in
  33. [`codex-plugin/brilliant`](./codex-plugin/brilliant) and adds a design skill, the hosted
  34. Brilliant tools (`https://brilliant.design/mcp`, no account) and this local server:
  35. ```
  36. codex plugin marketplace add brilliant-hq/brilliant-mcp
  37. codex plugin add brilliant@brilliant
  38. ```
  39. ## Gemini CLI extension
  40. This repository is also a Gemini CLI extension (`gemini-extension.json` at the root). It adds
  41. this local server and a context file, [`GEMINI.md`](./GEMINI.md), that tells Gemini when to
  42. design on the canvas and which call to make first:
  43. ```
  44. gemini extensions install https://github.com/brilliant-hq/brilliant-mcp
  45. ```
  46. ## Kiro power
  47. [`kiro-power`](./kiro-power) is a Kiro power in the Agent Plugins format: a manifest with the
  48. keywords that activate it (design, mockup, wireframe and more), a design skill and this local
  49. server. In Kiro, open the Powers panel, choose Add Custom Power, then Import power from GitHub,
  50. and give it `https://github.com/brilliant-hq/brilliant-mcp/tree/main/kiro-power`.
  51. ## First run
  52. Ask your agent for a design: "design a pricing page for this app". With no
  53. Brilliant open, the first tool call opens `brilliant.design` in your browser
  54. (Chrome, Edge or Firefox) and pairs it with your agent session; allow the one-time
  55. local network prompt. If the Brilliant desktop app is running, the server connects
  56. to it instead and opens nothing. Listing the tools never opens anything.
  57. ## What your agent can do
  58. The tools are Brilliant's own, served by the tab or the app; this package relays
  59. them unchanged. The main doors:
  60. - `init`: start a session and receive Brilliant's documentation for its tools.
  61. - `edit`: write designs, as HTML with inline CSS or as Blueprint, Brilliant's
  62. plain-text design format. Everything lands as editable vector layers.
  63. - `read`, `get_selection`: read canvases, design systems and what you selected.
  64. - `export`: PNG, JPEG, WebP, SVG, PDF, HTML and React.
  65. - `get_knowledge`: load design and format guidance on demand.
  66. - `generate_image`, `generate_svg`, `vectorize_image`, `remove_background`:
  67. image and vector generation inside a design.
  68. Every tool carries MCP annotations (a title, read-only and destructive hints), so
  69. your client can tell a read from a write before it calls.
  70. ## How it works
  71. - The server is a **relay**: MCP JSON-RPC crosses it verbatim. MCP semantics live
  72. in the Brilliant tab or desktop app, never here.
  73. - The first instance on a machine becomes the **leader** (one tab socket, one
  74. permission grant); every other MCP client's instance is a **follower** that
  75. forwards over loopback. Leadership reassigns when the leader exits.
  76. - The Brilliant **desktop app** is detected on `127.0.0.1:3333` to `3335` and
  77. covered by the same entry.
  78. The full wire contract is in [`PROTOCOL.md`](./PROTOCOL.md).
  79. ## Privacy
  80. This package makes no network calls of its own: no telemetry, no analytics, no
  81. update checks. It talks only to a `brilliant.design` tab you approve or to the
  82. Brilliant desktop app on your machine, over `127.0.0.1`.
  83. One thing does reach Brilliant's website: when the server opens the pairing tab,
  84. the link carries three attribution params, `utm_source=mcp-helper`, your MCP
  85. client's name (`utm_medium`, for example `claude-code`) and, if the install
  86. snippet set one, a door tag (`utm_content`, from `--src <tag>` or
  87. `BRILLIANT_MCP_SRC`). They tell us which install path people use. They say
  88. nothing about you, your machine or your designs, and the pairing token stays in
  89. the URL fragment, which a browser never sends to a server.
  90. It keeps a small state directory at `~/.config/brilliant/mcp-helper` (its ports, the pairings
  91. you approved and the last tool list), readable only by you.
  92. Brilliant itself, like any app, has its own data handling: the image tools run on
  93. Brilliant's servers when your agent calls them, and a cloud project syncs when you
  94. choose one. See the [privacy policy](https://brilliant.design/privacy).
  95. ## Security
  96. - Every listener binds the literal `127.0.0.1`: never `0.0.0.0`, never a scan of
  97. private ranges.
  98. - The tab socket validates `Origin: https://brilliant.design`, a loopback `Host`
  99. (against DNS rebinding), and a pairing token or an association you approved.
  100. - The pairing token is never served from any local endpoint; the state files are
  101. mode `0600`, and the web side never reads them.
  102. To report a vulnerability, see [`SECURITY.md`](./SECURITY.md).
  103. ## CLI
  104. ```
  105. npx @brilliant-hq/mcp # run the stdio MCP server (default)
  106. npx @brilliant-hq/mcp --src <tag> # run it, tagging the pairing link with an install door
  107. npx @brilliant-hq/mcp --version
  108. npx @brilliant-hq/mcp install <client> # add the server to <client>'s MCP config
  109. npx @brilliant-hq/mcp install <client> --dry-run # preview the change, write nothing
  110. npx @brilliant-hq/mcp install <client> --remove # remove it again
  111. ```
  112. `install` merges into the client's config without touching other servers, keeps
  113. JSONC comments, and `--remove` is its exact inverse.
  114. ## Development
  115. ```
  116. npm install
  117. npm test
  118. ```
  119. ## Docker
  120. The `Dockerfile` builds the same stdio server for registries that build and
  121. inspect it (`initialize`, `tools/list`):
  122. ```
  123. docker build -t brilliant-mcp .
  124. docker run -i --rm brilliant-mcp
  125. ```
  126. To design, run the server on your own machine with the commands under Install:
  127. it pairs with a Brilliant tab or the desktop app over `127.0.0.1`, which a
  128. container cannot reach.
  129. ## Pricing
  130. Canvas work by your own agents over MCP is unlimited on every Brilliant plan, the
  131. free plan included. Generated images and background removal draw on your
  132. Brilliant AI usage. Details: https://brilliant.design/pricing
  133. ## Licence
  134. The code in this repository is licensed under [Apache-2.0](./LICENSE). The licence
  135. covers this local server only: the Brilliant editor, engine and services are not
  136. open source, and the Brilliant name and logo are not licensed (see `NOTICE`).
  137. Docs: https://brilliant.design/docs/agents/overview

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.