Other · Local MCP server
Brilliant Directories MCP
Official MCP server for Brilliant Directories - manage members, posts, leads, reviews, and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.brilliantdirectories/brilliant-directories-mcp- Version
- 6.58.610
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- brilliantdirectories (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/brilliantdirectories) · how
- Repository
- github.com/brilliantdirectories/brilliant-directories-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | brilliant-directories-mcp | 6.58.610 | stdio |
How to connect Brilliant Directories MCP
Brilliant Directories MCP runs locally from a Node.js package published to the npm registry: brilliant-directories-mcp version 6.58.610. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y brilliant-directories-mcp@6.58.610. It reads these environment variables: BD_API_KEY (required, secret) and BD_SITE_URL (required); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"brilliant-directories-mcp": {
"command": "npx",
"args": [
"-y",
"brilliant-directories-mcp@6.58.610"
],
"env": {
"BD_API_KEY": "<secret>",
"BD_SITE_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| BriefGateClient intake: files, copy and logins from clients, from the browser or your AI agent. | Remote & Local · HTTP, stdioLive check: sign-in required |
| BrightmootShared projects for people and AI agents: plans, contributions, questions and reviews. Beta. | Remote · HTTPLive check: sign-in required |
| BrightspaceD2L Brightspace MCP server: grades, due dates, assignments, announcements and files. Any school. | Local · stdio |
| Brightspace D2l MCPD2L Brightspace for AI agents: due dates with submission status, grades and course content. | Local · stdio |
| Bristlecone LogicMicro-settled web content extraction and JSON schema validation utilities for AI agents via XRPL. | Local · stdio |
| Brivvy MCPBrivvy MCP (OAuth): on-brand AI content, voice rules, templates, glossary. | Remote · HTTPLive check: sign-in required |
| Brix Digital SignageManage digital signage screens: health, content, casts, emergency messages, proof of play. | Remote · HTTPLive check: sign-in required |
| Brixa StudioYour design, automated endlessly. Design anywhere, Brixa freezes it as a template, publishes forever. | Remote · HTTPLive check: sign-in required |