Log inSubmit server
Brilliant Directories MCP logo

Brilliant Directories MCP

Connects AI clients to Brilliant Directories sites for managing members, content, leads, settings, and other REST API resources.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Brilliant Directories MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "brilliant-directories-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "--prefer-online",
        "brilliant-directories-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y --prefer-online brilliant-directories-mcp@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

The brilliant-directories-mcp MCP server connects AI clients to a Brilliant Directories site through the site's REST API. It exposes tools for managing members, posts, leads, reviews, categories, pages, forms, menus, widgets, tags, membership plans, and other available resources. Use it when an agent needs to read or update directory data, with access controlled by a Brilliant Directories API key. It can run through a hosted MCP endpoint or locally with Node.js and npx.

Use cases

  • Manage directory members through an AI client
  • Update posts, pages, forms, and menus
  • Review leads and customer feedback
  • Maintain categories, tags, widgets, and redirects
  • Control destructive access by disabling delete permissions

Key features

  • Brilliant Directories REST API access
  • Member and post management
  • Lead and review operations
  • Pages, forms, menus, and widget management
  • Category, tag, and membership plan management
  • Hosted or local MCP configuration

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

9/9 checks healthy over the last 43d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · brilliant-directories-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars18Stargazers on the source repository.
npm downloads6.4kPackage downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.

How Brilliant Directories MCP works

What brilliant-directories-mcp MCP server does

The brilliant-directories-mcp MCP server gives compatible AI clients an MCP interface to a Brilliant Directories website. It translates agent requests into calls to the site's REST API and returns the resulting data or operation status.

The available resource coverage includes members, single-image and multi-image posts, leads, reviews, top-level and subcategories, email templates, homepage and landing pages, 301 redirects, smart lists, widgets, menus, forms, tags, and membership plans. The exact operations available depend on what the Brilliant Directories API exposes and which permissions are enabled for the API key.

How it works

Two connection patterns are documented. The hosted option points an MCP client at https://brilliantmcp.com and sends the Brilliant Directories API key and site URL as request headers. The local option launches the npm package with npx, passing the API key and site URL as command-line arguments. Both paths provide the same documented tool surface.

The site URL must use the canonical form that loads in a browser, including its protocol and, where applicable, www. It must not have a trailing slash. Requests are authenticated with the API key created in Brilliant Directories Admin under Developer Hub.

Setup and configuration

Create an API key in Brilliant Directories before configuring the client. New keys allow member read and write operations by default, while other resource groups require Advanced Endpoints permissions. In Developer Hub, open the key's permissions, enable the required endpoint groups, and save the change. Delete actions can be disabled individually if the agent should not remove data.

The hosted configuration requires a JSON MCP entry with the url set to https://brilliantmcp.com and headers named X-Api-Key and X-BD-Site-URL. The local configuration uses npx -y --prefer-online brilliant-directories-mcp@latest followed by --api-key and --url values. Node.js is required only for the local path. After saving either configuration, fully quit and reopen the AI client so it reloads its MCP settings.

Tools and capabilities

The brilliant-directories-mcp MCP server supports agent-driven operations across the resource groups exposed by the Brilliant Directories REST API. Practical uses include listing or changing members, handling posts and images, working with leads and reviews, editing site pages, and maintaining administrative content such as forms, menus, widgets, tags, templates, redirects, and membership plans.

The server is documented for use with Claude Desktop, Claude Code, Cursor, Windsurf, Cline, and Codex Desktop. Claude Desktop requires the local stdio configuration rather than the hosted URL configuration.

Limitations and notes

Access is limited by the Brilliant Directories API key. A request for a resource without the corresponding Advanced Endpoints permission returns a 403 response, even when member operations work. Enabling permissions does not require rotating the key or restarting the AI client.

The server therefore should be evaluated against the specific endpoints and permissions needed by the intended workflow. Keep API keys in the client configuration securely, since they authorize operations on the connected site.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Brilliant Directories MCP

brilliant-directories-mcp is an MCP server that connects AI clients to a Brilliant Directories site through its REST API. Its tools manage members, posts, leads, reviews, categories, pages, forms, menus, widgets, tags, membership plans, and other exposed resources, using an API key and site URL.

Install it locally by configuring your MCP client to run `npx -y --prefer-online brilliant-directories-mcp@latest` with your API key and canonical site URL. Node.js is required for this option. Alternatively, use the hosted endpoint at `https://brilliantmcp.com` with the required headers.

Yes, brilliant-directories-mcp works with Cursor. Add either the hosted URL configuration with `X-Api-Key` and `X-BD-Site-URL` headers or the local npx configuration, then fully restart Cursor so it loads the MCP server.

A 403 usually means the API key lacks permission for the requested endpoint. Member read and write access is enabled by default, while other resources require Advanced Endpoints permissions in Brilliant Directories Developer Hub. Enable the needed resource or action and retry the request.

Yes, disable the delete actions in the API key's Advanced Endpoints permissions. The agent can still read, create, and update resources, but delete tool calls will receive a 403 response.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBrilliant Directories MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/brilliant-directories-mcp?style=directory)](https://allmcps.com/mcp/brilliant-directories-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/brilliant-directories-mcp"><img src="https://allmcps.com/api/badge/brilliant-directories-mcp?style=directory" alt="Brilliant Directories MCP on AllMCPs" /></a>