Use
COMPOSIOFOR YOU
Give Claude, Codex, or any harness secure access to 1700+ tools
CLI
One command to add tools and auth to your coding agent
Build
DEVELOPER PLATFORM
SDKs, tools, and auth for agents and backend apps
MCP GATEWAY
One managed MCP endpoint for all your tools and agents
ENTERPRISE
SSO, governance, and audit controls for deploying agents org-wide
Features
TRIGGERS
Start background agents from events across your connected apps
FIREWALLNEW
Blocks instructions hidden in tool results before your agent reads them
INSTANTNEW
Audio, video, search, browser and data tools, with no keys to manage
OPTIMIZATION
Lower cost per completed task with optimised tools and skills
FOR AGENTS
CLAUDE CODEX OPENCLAW CURSOR HERMES
BUILT FOR
OFFICE WORK SALES MARKETING PRODUCT & DESIGN CUSTOMER SUPPORT ENGINEERING HR & RECRUITING FINANCE & OPS E-COMMERCE CONTENT & MEDIA IT & SECURITY
ALL USE CASES
DOCS

How to integrate Brilliant directories MCP with Mastra AI

Connect Mastra AI to Brilliant directories MCP. Add a new member with company details, delete user and remove their uploaded images, and more using natural language, with authentication handled for you.

Get started for free Get a demo

Brilliant directories

Api Key

Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface.

44 Tools

Managed auth

Connect Brilliant directories without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Book a call

Explore the MCP Gateway

Introduction

This guide walks you through connecting Brilliant directories to Mastra AI using the Composio tool router. By the end, you'll have a working Brilliant directories agent that can create and search members, manage leads, publish data posts, search reviews, and update widgets through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Brilliant directories account through Composio's Brilliant directories MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Brilliant directories with

Claude Code Claude Cowork OpenAI Agents SDK Claude Agent SDK Codex OpenClaw Hermes Atomic Agent Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI Pydantic AI AutoGen

TL;DR

Here's what you'll learn:

Set up your environment so Mastra, OpenAI, and Composio work together
Create a Tool Router session in Composio that exposes Brilliant directories tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Brilliant directories tool definitions and attach them as a toolset
Build a Mastra agent that can reason, call tools, and return structured results
Run an interactive CLI where you can chat with your Brilliant directories agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

MCP Client: Built-in support for Model Context Protocol servers
Toolsets: Organize tools into logical groups
Step Callbacks: Monitor and debug agent execution
OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Brilliant directories MCP server, and what's possible with it?

The Brilliant directories MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Brilliant directories account. It provides structured and secure access to your membership community and business directory platform, so your agent can perform actions like managing users, retrieving data categories, and automating lead and review workflows on your behalf.

User creation and management: Easily instruct your agent to create new users with detailed profiles or delete existing members, streamlining your directory's onboarding and maintenance.
Deep data category access: Ask your agent to fetch all available data categories from your site, making it simple to organize content or power dynamic site navigation experiences.
Lead field discovery and automation: Let your agent retrieve the full structure of your leads table, helping you automate lead capture, validation, or enrichment workflows with up-to-date field metadata.
Review field extraction and insights: Direct your agent to pull all available review fields, enabling smarter review management, analytics, or custom reporting based on your site’s feedback system.
User data field exploration: Have your agent fetch and analyze all user-related fields, supporting advanced user segmentation, targeted updates, or personalized communications.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Node.js 18 or higher
A Composio account with an active API key
An OpenAI API key
Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key.
You need credits or a connected billing setup to use the models.
Store the key somewhere safe.

Composio API Key

Log in to the Composio dashboard.
Go to Settings and copy your API key.
This key lets your Mastra agent talk to Composio and reach Brilliant directories through MCP.

Install dependencies

bash

npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

@composio/core is the Composio SDK for creating MCP sessions
@mastra/core provides the Agent class
@mastra/mcp is Mastra's MCP client
@ai-sdk/openai is the model wrapper for OpenAI
dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your requests to Composio
COMPOSIO_USER_ID tells Composio which user this session belongs to
OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});

What's happening:

dotenv/config auto loads your .env so process.env.* is available
openai gives you a Mastra compatible model wrapper
Agent is the Mastra agent that will call tools and produce answers
MCPClient connects Mastra to your Composio MCP server
Composio is used to create a Tool Router session

Create a Tool Router session for Brilliant directories

typescript

async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["brilliant_directories"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Brilliant directories MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "brilliant_directories" for Brilliant directories access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript

const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);

What's happening:

MCPClient takes an id for this client and a list of MCP servers
The headers property includes the x-api-key for authentication
getTools fetches the tool definitions exposed by the Brilliant directories toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "brilliant_directories-mastra-agent",
    instructions: "You are an AI agent with Brilliant directories tools via Composio.",
    model: "openai/gpt-5",
  });

What's happening:

Agent is the core Mastra agent
name is just an identifier for logging and debugging
instructions guide the agent to use tools instead of only answering in natural language
model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript

let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        brilliant_directories: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

messages keeps the full conversation history in Mastra's expected format
agent.generate runs the agent with conversation history and Brilliant directories toolsets
maxSteps limits how many tool calls the agent can take in a single run
onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Brilliant directories and Mastra AI:

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["brilliant_directories"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      brilliant_directories: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "brilliant_directories-mastra-agent",
    instructions: "You are an AI agent with Brilliant directories tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { brilliant_directories: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Brilliant directories through Composio's Tool Router. You can extend this further by:

Adding other toolkits like Gmail, Slack, or GitHub
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows

TOOLS

Supported Tools

Every Brilliant directories action and event your agent gets out of the box.

Create Album Photo

Tool to add a new album photo to a user's portfolio in Brilliant Directories.

Create Data Category

Creates a new data category (post type) in the Brilliant Directories website database.

Create Data Post

Tool to create a new Single Image Post (member post) in the Brilliant Directories database.

Create Lead

Tool to create a new lead in the Brilliant Directories database.

Create Portfolio Group

Creates a new multi-image portfolio post in the Brilliant Directories database.

Create Unsubscribe

Tool to add an unsubscriber to the database and unsubscribe a member from email campaigns.

Create User

Creates a Brilliant Directories user or member account with email, a password of at least six characters, and a membership plan ID, plus optional personal, contact, address, profile, and status fields.

Create Users Click

Tool to add a new user clicked link tracking record to the database.

Create Widget

Tool to create a new widget in the Brilliant Directories website database.

Delete Album Photo

Tool to delete an album photo and its related data from the database.

Delete Data Category

Tool to permanently delete a post type (data category) and all related data from the database.

Delete Lead

Tool to delete a lead and their related data from the database.

Delete Portfolio Group

Tool to delete a multi-image post (portfolio group) and its related data from the database.

Delete Unsubscribe Record

Tool to delete an unsubscribe record and its related data from the database.

Delete User

Deletes a Brilliant Directories user and related data, with an option to delete the member's uploaded image files.

Delete Users Click

Tool to delete a user clicked link and their related data from the database.

Delete Widget

Tool to delete a widget and its related data from the database.

Get Album Photo

Retrieves an album image by photo ID, returning supported metadata such as title, description, file paths, timestamps, and status.

Get Data Categories Fields

This tool retrieves all available custom fields for Data Categories (Post Types) in a Brilliant Directories website.

Get Data Category

Retrieves configuration data for a single Brilliant Directories post type by data ID, including identifying fields and search configuration.

Get Data Post

Retrieves a single image or video member post by post ID, returning supported post content, author, category, and associated user information.

Get Lead

Retrieves a lead by ID from Brilliant Directories, returning supported contact, inquiry, location, category, and other lead details.

Get Lead Fields

Returns a fixed list of lead field names, types, labels, and required and system-field flags after an API connectivity check.

Get Portfolio Group

Retrieves a multi-image post by group ID, returning supported post fields such as description, location, tags, image references, and property details when available.

Get Review

Tool to retrieve complete review data from Brilliant Directories based on review_id.

Get Reviews Fields

Returns a fixed set of review field definitions, including names, types, descriptions, and required flags.

Get Unsubscribe Record

Tool to retrieve a single unsubscriber record by ID.

Get User by ID

Tool to retrieve comprehensive data for a single user by their user_id.

Get User Data

Retrieves comprehensive user data from the Brilliant Directories database by searching for a specific property value.

Get User Clicked Link

Tool to retrieve click tracking data for a single user clicked link based on the click_id.

Get User Transactions

Retrieves payment and transaction history for a member using both user_id and client_id.

Get Widget

Retrieves the data of a single widget based on the widget_id.

Match Leads

Tool to match a batch of emails or user IDs to a specific lead record.

Search Reviews

Search reviews and their related data from the database.

Search Users

Search for users/members in the Brilliant Directories database with advanced filtering options.

Update Album Photo

Updates an existing album photo record in the Brilliant Directories database.

Update Data Category

Tool to update an existing post type (data category) record in Brilliant Directories.

Update Data Post

Updates a single image post and related data by post ID, including content, status, and metadata.

Update Lead

Updates an existing lead record in the Brilliant Directories website database.

Update Portfolio Group

Tool to update a multi-image post (portfolio group) record in the Brilliant Directories database.

Update Unsubscribe

Updates an existing unsubscribe list record in the Brilliant Directories database.

Update User

Updates an existing user record in the Brilliant Directories website database.

Update User Click Record

Updates a user clicked link record and their related data from the database.

Update Widget

Tool to update an existing widget record in the Brilliant Directories database.

FRAMEWORKS

How to build Brilliant directories MCP Agent with another framework

Claude Code

Use Brilliant directories MCP with Claude Code

Claude Cowork

Use Brilliant directories MCP with Claude Cowork

OpenAI Agents SDK

Use Brilliant directories MCP with OpenAI Agents SDK

Claude Agent SDK

Use Brilliant directories MCP with Claude Agent SDK

Codex

Use Brilliant directories MCP with Codex

OpenClaw

Use Brilliant directories MCP with OpenClaw

Hermes

Use Brilliant directories MCP with Hermes

Atomic Agent

Use Brilliant directories MCP with Atomic Agent

Google ADK

Use Brilliant directories MCP with Google ADK

LangChain

Use Brilliant directories MCP with LangChain

Vercel AI SDK

Use Brilliant directories MCP with Vercel AI SDK

LlamaIndex

Use Brilliant directories MCP with LlamaIndex

CrewAI

Use Brilliant directories MCP with CrewAI

Pydantic AI

Use Brilliant directories MCP with Pydantic AI

AutoGen

Use Brilliant directories MCP with AutoGen

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

HubSpot

Oauth2Api Key

HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.

Pipedrive

Oauth2Api Key

Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.

Salesforce

Oauth2S2s Oauth2

Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships.

Apollo

Api Key

Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place.

FAQ

Frequently asked questions

With a standalone Brilliant directories MCP server, the agents and LLMs can only access a fixed set of Brilliant directories tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Brilliant directories and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Brilliant directories tools.

Yes, absolutely. You can configure which Brilliant directories scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Brilliant directories data and credentials are handled as safely as possible.

Start with Brilliant directories.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Brilliant directories tool your agent needs.Free to start.

Start building

How to integrate Brilliant directories MCP with Mastra AI

Connect Brilliant directories without auth hassles

Introduction

Also integrate Brilliant directories with

TL;DR

What is Mastra AI?

What is the Brilliant directories MCP server, and what's possible with it?

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Brilliant directories

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Brilliant directories MCP Agent with another framework

Claude Code

Claude Cowork

OpenAI Agents SDK

Claude Agent SDK

Codex

OpenClaw

Hermes

Atomic Agent

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

Pydantic AI

AutoGen

Explore Other Toolkits

HubSpot

Pipedrive

Salesforce

Apollo

Frequently asked questions

What are the differences in Tool Router MCP and Brilliant directories MCP?

Can I use Tool Router MCP with Mastra AI?

Can I manage the permissions and scopes for Brilliant directories while using Tool Router?

How safe is my data with Composio Tool Router?

Start with Brilliant directories.It takes 30 seconds.