Brilliant MCP Server

by brilliant Your server? Claim it

local only

Brilliant runs on your own machine — the client starts it, so there is no endpoint to ping. 124 installs a week from npm.

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

Installs per day peak 592 · avg 53 · -62% w/w

a month agotoday

124

Installs / week

npm · @brilliant-hq/mcp

—

Stars

on GitHub

—

Last commit

0 releases in 90 days

—

License

language unknown

Nothing serious here today

Today is the operative word: we check Brilliant every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp -- npx -y @brilliant-hq/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@brilliant-hq/mcp"]

.cursor/mcp.json

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

.vscode/mcp.json

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

Alternatives to Brilliant

same job, measured the same way

Continuum

by pouyahasanamreji

Shared memory + orchestration for your coding agents. Local-first MCP, vector RAG.

local only

Memory Fabric

by elvirafa

File-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB.

586 installs/wk local only

SAME - Stateless Agent Memory Engine

by sgx-labs

Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.

40 installs/wk local only

Copilot Memory MCP

by labforgedev

Persistent semantic memory for AI agents using local ChromaDB vector search. No cloud required.

local only

MCP Qdrant

by infoinlet-marketplace

Read-only Qdrant vector DB for AI agents — collections, info, browse points, count, search.

18 installs/wk local only

Fusionpact Vectordb

by atul-fusionpact

Hybrid vector + reasoning retrieval, agent memory, multi-agent orchestration, MCP server, and RAG.

13 installs/wk local only

Srclight

by srclight

Deep code indexing for AI agents. FTS5 + embeddings + call graphs + git intelligence. Fully local.

2 671 installs/wk local only

SmartMemory

by smartmemory

Graph + vector memory for agents: recall, ingest, search, distill. Local or remote backend.

1 640 installs/wk local only

Brilliant — questions

Answers built from our own checks of this server.

Why is there no uptime for Brilliant?

Brilliant runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @brilliant-hq/mcp was installed 124 times last week.

How do I connect Brilliant?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @brilliant-hq/mcp straight from npm; nothing to host, nothing to sign up for.

How many people use Brilliant?

The npm package @brilliant-hq/mcp was installed 124 times in the last week. Week over week that is -62%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.