Brilliant Directories MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 6 325 installs a week from npm. Last commit 17 Oct 2026.
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.
We read the source, 1 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
# Defaults let the server start for tools/list introspection (Glama, MCP Inspector). # Real usage must override both with the customer's credentials: # docker run -e BD_API_KEY=... -e BD_API_URL=https://site.com IMAGE ENV BD_API_KEY=placeholder
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Brilliant Directories MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
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 mcp add brilliant-directories-mcp -e 'BD_API_KEY=<BD_API_KEY>' -e 'BD_SITE_URL=<BD_SITE_URL>' -- npx -y brilliant-directories-mcp
{
"mcpServers": {
"brilliant-directories-mcp": {
"command": "npx",
"args": [
"-y",
"brilliant-directories-mcp"
],
"env": {
"BD_API_KEY": "<BD_API_KEY>",
"BD_SITE_URL": "<BD_SITE_URL>"
}
}
}
}
[mcp_servers.brilliant-directories-mcp]
command = "npx"
args = ["-y", "brilliant-directories-mcp"]
env = { BD_API_KEY = "<BD_API_KEY>", BD_SITE_URL = "<BD_SITE_URL>" }
{
"mcpServers": {
"brilliant-directories-mcp": {
"command": "npx",
"args": [
"-y",
"brilliant-directories-mcp"
],
"env": {
"BD_API_KEY": "<BD_API_KEY>",
"BD_SITE_URL": "<BD_SITE_URL>"
}
}
}
}
{
"servers": {
"brilliant-directories-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"brilliant-directories-mcp"
],
"env": {
"BD_API_KEY": "<BD_API_KEY>",
"BD_SITE_URL": "<BD_SITE_URL>"
}
}
}
}
Put your own values in place of
<BD_API_KEY> (Your Brilliant Directories API key. Generate one in BD Admin → Developer Hub → Generate API Key), <BD_SITE_URL> (Your BD site URL, e.g. https://yoursite.com (BD_API_URL is also accepted as a legacy alias)).
The author’s registry entry marks them as required.
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Read and manage courses, members, orders, events, posts, and settings for Loopwise-powered sites.
Official MCP server for Automox. Manage devices, patches, and policies in natural language.
Official MCP server for Leadpipe intent and data APIs.
MCP server for Bitbucket API - manage repositories, pull requests, comments, pipelines and more
Unofficial MCP server for the Polish Fitatu app. Search foods and manage meals, recipes, and logs.
MCP server for SocialAPI — manage social media comments, DMs, reviews, and mentions across platforms
Official Todoist MCP server for AI assistants to manage tasks, projects, and workflows.
Answers built from our own checks of this server.