Brilliant Directories

@brilliant-directories what fields are available in our member directory, and which ones are required when adding new members?

The user table includes 47 fields. Required fields for new members: email (unique identifier), password (minimum 8 characters), and subscription_id (determines access level). Optional fields include: first_name, last_name, company_name, phone, website_url, bio (supports HTML), profile_image_url, address fields (street, city, state, zip, country), social_media_handles (linkedin, twitter, facebook), and 12 custom fields you've configured for industry specializations. The subscription_id must match an active plan in your site's configuration.

This example shows the MCP's schema-discovery capability — useful before bulk imports or form builds. The field list reflects your specific Brilliant Directories configuration, so actual available fields vary by site. Requires read access to the users table via your API key.

@brilliant-directories create a new member account for sarah.chen@example.com with the Premium subscription and set her company name to 'Chen Consulting Group'

Created user record for sarah.chen@example.com (user_id: 8472). Assigned subscription_id 3 (Premium tier, grants access to advanced search and messaging features). Set company_name to 'Chen Consulting Group'. A temporary password was generated and would typically be sent via your site's welcome email automation. The new member profile is now visible in your directory's search results, pending any moderation rules you've configured for new accounts.

This write operation demonstrates member onboarding automation. The MCP creates the database record but doesn't trigger Brilliant Directories' native email workflows — coordinate with your site's notification settings. Subscription IDs are site-specific; confirm valid values with Get User Fields first. This action is irreversible without the Delete User tool.

@brilliant-directories pull all review fields, then draft a monthly summary email highlighting our top-rated members based on recent feedback

Retrieved 18 review fields including: reviewer_name, rating (1-5 scale), review_text, review_date, member_id (reviewed party), status (pending/approved/rejected), and helpful_count. Based on this schema, here's a draft summary: 'This month's standout members: Martinez Legal (4.9 avg, 12 reviews) praised for responsiveness; TechBridge Solutions (4.8 avg, 9 reviews) noted for innovative approaches; Green Consulting (4.7 avg, 15 reviews) highlighted for thoroughness. All ratings reflect approved reviews from verified clients since March 1st.' Customize tone and add member profile links before sending.

This synthesis example pairs the MCP's data-fetching with AI reasoning to generate stakeholder communications. The review schema varies by your Brilliant Directories configuration (some sites add custom fields like 'project_type'). Requires read access to the reviews table; ensure your API key permissions include review data.

When Brilliant Directories MCP fits directory-based member portals

A 3-person coaching business runs a member directory on Brilliant Directories and wants to sync new Stripe subscriptions into user accounts without manual CSV uploads. This MCP is the right call if you're already locked into Brilliant Directories as your platform and need programmatic user creation tied to payment events. The Create User tool handles email, password, and subscription ID in one shot, which covers the 80% case for onboarding flows. The constraint: you're limited to 6 tools, so complex workflows like bulk lead imports or review moderation will require multiple API calls and custom logic. If your directory has under 500 active members and onboarding happens a few times a week, this MCP saves you from building a custom integration. Beyond that scale, evaluate whether Brilliant Directories itself is the bottleneck.

Using Get Lead Fields for CRM handoff prep

A solo consultant collects leads through a Brilliant Directories form and wants to push qualified contacts into HubSpot with the right field mappings. The Get Lead Fields tool is useful here because it returns the exact schema of your leads table, so you can write a one-time mapping script that won't break when you add custom fields in the Brilliant Directories admin. This is a narrow win: it's faster than manually documenting your schema, but it doesn't move the leads for you. You still need a separate integration to read lead records and push them downstream. If you're running this sync daily and your lead volume is under 50 per day, the MCP gives you schema stability without vendor lock-in to a no-code tool. If you're syncing hourly or handling hundreds of leads, you need a dedicated iPaaS connector, not an MCP.

When Delete User makes sense for compliance-driven offboarding

A 5-person SaaS team uses Brilliant Directories to manage a partner network and needs to purge user records within 30 days of cancellation to meet GDPR retention policies. The Delete User tool handles this if your offboarding logic is simple: one user ID in, record gone, optionally wipe uploaded images. This works when churn is low (under 10 users per month) and you're triggering deletions from a manual review step or a scheduled script. The trade-off: the MCP doesn't give you bulk delete or audit logging, so if you're processing dozens of deletions weekly or need a compliance trail, you'll outgrow this fast. For small teams with straightforward data retention rules and low churn, this MCP closes the loop without paying for a full data governance platform.