Brilliant

design.brilliantPublished by brilliant.designv0.1.6Updated Oct 24, 2026

Local MCP bridge: your coding agent designs on Brilliant's real vector canvas, fully on 127.0.0.1.

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

A local MCP bridge that lets a coding agent design on Brilliant's real vector canvas, running entirely on the local machine.

What you can do
Connect a coding agent to Brilliant's vector canvas so it can work on designs directly from the agent session. The bridge runs locally on 127.0.0.1, keeping the connection on the user's own machine. No individual tools are listed, so the exact design actions available are not documented in the supplied material.
When to use it
Useful when you already work in Brilliant and want a coding agent to make design changes on its vector canvas without leaving the agent workflow. It is a desktop-only bridge, so it suits local desktop setups rather than web or remote environments.
Requirements
A local process installed from the npm package @brilliant-hq/mcp over stdio. It is desktop only and not web executable. No authentication, environment variables or headers are declared.
Before you install
The bridge can act on your Brilliant designs, so changes made through the agent may alter existing work; review results before relying on them. No credentials are declared, but the server runs locally with access to your design session.

Installation

In SourceWeft

  1. Open Brilliant in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.6LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.