brilliant-directories-mcp
mcpkey · packageio.github.brilliantdirectories/brilliant-directories-mcp · v6.58.612
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
# once, as root:
# as_mcp DIR COMMAND...: runs COMMAND as the mcp user in DIR, its home, sandboxed as the
# units are: a package's install scripts can write to DIR only, as the server later can
as_mcp() {
local dir="$1"; shift
systemd-run --quiet --wait --pipe --collect --uid=mcp --gid=mcp \
-p WorkingDirectory="$dir" -p Environment=HOME="$dir" -p ReadWritePaths="$dir" \
-p NoNewPrivileges=true -p ProtectSystem=strict -p ProtectHome=true -p PrivateTmp=true \
-- "$@" </dev/null
}
install -d -m 0750 -o mcp -g mcp /var/lib/mcp/brilliant-directories
# brilliant-directories: its packages, installed whole before its unit starts (no session installs)
# npx takes a half-installed tree for installed: a rerun starts them afresh
systemctl stop mcp-my-agent-brilliant-directories.service 2>/dev/null || true
as_mcp /var/lib/mcp/brilliant-directories rm -rf /var/lib/mcp/brilliant-directories/.npm/_npx
as_mcp /var/lib/mcp/brilliant-directories npx --yes [email protected] -- true
as_mcp /var/lib/mcp/brilliant-directories npx --yes --package=supergateway@4 -- true
#!/usr/bin/env bash
# brilliant-directories (io.github.brilliantdirectories/brilliant-directories-mcp), recipe baremetal (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-brilliant-directories.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz
[Unit]
Description=MCP server brilliant-directories (toolset my-agent), generated by Hub
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/brilliant-directories
WorkingDirectory=/var/lib/mcp/brilliant-directories
ExecStart=/opt/mcp/my-agent/bin/brilliant-directories.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/brilliant-directories
[Install]
WantedBy=multi-user.target
generated from the record, not tested yet
docker run --rm -p 127.0.0.1:8101:8000 -e BD_API_KEY -e BD_SITE_URL node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y [email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T22:17:59+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
brilliant-directories:
image: node:22-alpine
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
ports:
- 127.0.0.1:8101:8000
volumes:
- npm-cache:/root/.npm
healthcheck:
test:
- CMD-SHELL
- wget -qO- http://127.0.0.1:8000/healthz || exit 1
interval: 30s
timeout: 5s
retries: 5
start_period: 2m
restart: unless-stopped
environment:
BD_API_KEY: ${BD_API_KEY}
BD_SITE_URL: ${BD_SITE_URL}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T22:17:59+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: brilliant-directories
namespace: mcp
labels: &id001
app: brilliant-directories
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: brilliant-directories
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: BD_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: BD_API_KEY
- name: BD_SITE_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: BD_SITE_URL
args:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport
streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint
/healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: brilliant-directories
namespace: mcp
spec:
selector:
app: brilliant-directories
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T22:17:59+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
brilliant-directories:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: brilliant-directories
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: BD_API_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: BD_API_KEY
- name: BD_SITE_URL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: BD_SITE_URL
args:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: BD_API_KEY, BD_SITE_URL. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsnpx -y [email protected] # env: BD_API_KEY, BD_SITE_URL
{
"mcpServers": {
"brilliant-directories": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BD_API_KEY": "${BD_API_KEY}",
"BD_SITE_URL": "${BD_SITE_URL}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add brilliant-directories -e "BD_API_KEY=${BD_API_KEY}" -e "BD_SITE_URL=${BD_SITE_URL}" -- npx -y [email protected]
{
"mcpServers": {
"brilliant-directories": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BD_API_KEY": "${BD_API_KEY}",
"BD_SITE_URL": "${BD_SITE_URL}"
}
}
}
}
{
"servers": {
"brilliant-directories": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BD_API_KEY": "${BD_API_KEY}",
"BD_SITE_URL": "${BD_SITE_URL}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.brilliantdirectories/brilliant-directories-mcp
- not probed yet: tools unpinned, ingest lists them
tools
Probe result: needs authdocker: credentials=placeholder: no MCP server found (:8000/mcp: HTTP 404: MCPError: MCP server process failed; :8000/: HTTP 404: MCPError: Not Found) …callbus-hub-worker","version":"0.1.0"}}} [supergateway] SessionAccessCounter.clear() f07acffb-d7bc-47be-82b3-3a380dc60094, caused by child process failure [supergateway] StreamableHttp connection closed (session f07acffb-d7bc-47be-82b3-3a380dc60094) [supergateway] Response finished f07acffb-d7bc-47be-82b3-3a380dc60094 [supergateway] Child stderr: Error: Could not parse BD_SITE_URL='<secret>' as a URL. [supergateway] MCP child failed: Error: Child stdout closed at Socket.<anonymous> (file://<path>:53:43) at Socket.emit (node:events:531:35) at endReadableNT (node:internal/streams/readable:1698:12) at process.processTicksAndRejections (node:internal/process/task_queues:89:21) [supergateway] MCP child request failed: Error: Child stdout closed at Socket.<anonymous> (file://<path>:53:43) at Socket.emit (node:events:531:35) at endReadableNT (node:internal/streams/readable:1698:12) at process.processTicksAndRejections (node:internal/process/task_queues:89:21) [supergateway] Child stderr: Error: Could not parse BD_SITE_URL='<secret>' as a URL. [supergateway] Child exited: code=1, signal=null [supergateway] Child stderr: Error: Could not parse BD_SITE_URL='<secret>' as a URL. [supergateway] Child exited: code=1, signal=null; baremetal: same crash as docker
runs · 1
the latest tests of this entry by the hub and its workers, newest first| date | worker | method | status | sandbox | reason |
|---|---|---|---|---|---|
| 2026-10-18 16:39 | local-mac-vm | docker | needs auth | gvisor | docker: credentials=placeholder: no MCP server found (:8000/mcp: HTTP 404: MCPError: MCP server process failed; :8000/: HTTP 404: MCPError: Not Found) …callbus-… |