How to integrate Fireberry MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Fireberry logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Fireberry to Mastra AI using the Composio tool router. By the end, you'll have a working Fireberry agent that can add new lead to contacts table, list all open deals in pipeline, fetch picklist options for deal stage through natural language commands.

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

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

Also integrate Fireberry with

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 Fireberry tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Fireberry 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 Fireberry 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 Fireberry MCP server, and what's possible with it?

The Fireberry MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fireberry CRM account. It provides structured and secure access to your CRM data, so your agent can perform actions like creating records, querying customer information, and managing picklists on your behalf.

  • Automated record creation: Let your agent swiftly add new entries to any Fireberry table, such as contacts, leads, or deals, using structured data you provide.
  • Smart CRM data retrieval: Ask your agent to query records with powerful filtering, sorting, and pagination—perfect for finding the exact customer or deal you need.
  • Picklist value management: Effortlessly fetch all available options for any picklist (dropdown) field, making data entry and workflow automation simpler and error-free.
  • Custom module support: Enable your agent to work with any Fireberry module, so you can handle specialized business processes or custom workflows.

Supported Tools & Triggers

Tools
Create a CompetitorTool to create a new competitor in Fireberry.
Create a Fireberry contactTool to create a new contact in Fireberry CRM.
Create an Activity LogCreate a new Activity Log record in Fireberry.
Create a date fieldTool to create a new date field in a Fireberry object/table.
Create a Fireberry lookup fieldTool to create a lookup field in Fireberry CRM.
Create a new Fireberry accountTool to create a new account in Fireberry CRM.
Create an ArticleTool to create a new article in Fireberry.
Create a Fireberry assetCreates a new asset (account product) in Fireberry.
Create an OpportunityTool to create a new opportunity in Fireberry CRM.
Create an Order ItemTool to create a new order item in Fireberry CRM.
Create a noteCreate a new note record in Fireberry.
Create a phone callCreates a new phone call record in Fireberry's call log.
Create a Fireberry productTool to create a new product in Fireberry.
Create a ProjectTool to create a new project in Fireberry CRM.
Create a TaskTool to create a new task in Fireberry CRM.
Create a TicketTool to create a new ticket (case) in Fireberry CRM.
Create a URL fieldTool to create a new URL field in a Fireberry object/table.
Create a CampaignTool to create a new campaign in Fireberry.
Create a CRM OrderTool to create a new CRM Order in Fireberry.
Upload file to Fireberry recordTool to upload a file to a specific record in Fireberry.
Create a Fireberry meetingTool to create a new meeting (activity) in Fireberry.
Create a new Fireberry recordCreates a new record in a specified Fireberry table/module.
Delete an AccountTool to delete an account from Fireberry using its GUID.
Delete a CompetitorTool to delete a competitor in Fireberry by its GUID.
Delete a contractTool to delete a contract in Fireberry by its GUID.
Delete an Activity LogDelete an activity log by its GUID.
Delete a custom fieldTool to delete a custom field from a Fireberry object/table.
Delete an ArticleTool to delete an article from Fireberry by its GUID.
Delete a Fireberry assetDelete an asset from Fireberry by its unique identifier.
Delete an OpportunityTool to delete an opportunity in Fireberry by its GUID.
Delete an Order ItemTool to delete an order item in Fireberry by its GUID.
Delete a NoteTool to delete a note from Fireberry using its GUID.
Delete a Phone CallTool to delete a phone call record from Fireberry using its GUID.
Delete a projectTool to delete a project from Fireberry using its GUID.
Delete a taskTool to delete a task in Fireberry by its GUID.
Delete a ticketTool to delete a ticket (case) from Fireberry using its GUID.
Delete a Business UnitTool to delete a Business Unit in Fireberry using its GUID.
Delete a Fireberry campaignTool to delete a campaign from Fireberry.
Delete a ContactTool to delete a contact from Fireberry using its GUID.
Delete a CRM UserTool to delete a CRM user from Fireberry using its GUID.
Delete a MeetingTool to delete a meeting activity from Fireberry by its GUID.
Delete a productTool to delete a product in Fireberry by its GUID.
Get an AccountTool to retrieve a specific account record by its GUID.
Get a CRM OrderTool to retrieve a specific CRM Order from Fireberry by its GUID.
Get All AccountsTool to retrieve all accounts from Fireberry CRM with pagination support.
Get All Activity Logs (v2)Tool to retrieve all activity logs from Fireberry using v2 API endpoint with pagination support.
Get all articles from FireberryTool to retrieve all articles from Fireberry with pagination support.
Get All AssetsTool to retrieve all assets (account products) from Fireberry with pagination support.
Get All Business Units (v2)Tool to retrieve all business units from Fireberry using v2 API endpoint with pagination support.
Get All CampaignsTool to retrieve all campaigns from Fireberry with pagination support.
Get All Competitors (v2)Tool to retrieve all competitors from Fireberry with pagination support.
Get All ContactsTool to retrieve all contacts from Fireberry with pagination support.
Get All ContractsTool to retrieve all contracts from Fireberry with pagination support.
Get All Custom Object RecordsTool to retrieve all records from a specified custom object in Fireberry with pagination support.
Get All MeetingsTool to retrieve all meetings (activities) from Fireberry CRM with pagination support.
Get All Notes (Detailed)Tool to retrieve all notes from Fireberry with detailed field schema and pagination support.
Get All ObjectsTool to retrieve all object type metadata from Fireberry.
Get All Order ItemsTool to retrieve all order items from Fireberry with pagination support.
Get All OrdersTool to retrieve all orders from Fireberry with pagination support.
Get All Phone CallsTool to retrieve all phone call records from Fireberry with pagination support.
Get All Projects (v2)Tool to retrieve all projects from Fireberry with pagination support.
Get All TasksTool to retrieve all tasks from Fireberry with pagination support.
Get All TicketsTool to retrieve all ticket records (cases) from Fireberry with pagination support.
Get All UsersTool to retrieve all CRM users from Fireberry with pagination support.
Get a MeetingTool to retrieve a specific meeting/activity record by its unique identifier (GUID).
Get an Activity LogTool to retrieve a specific activity log record from Fireberry by its GUID.
Get an ArticleTool to retrieve a specific article from Fireberry by its GUID.
Get an AssetTool to retrieve a specific asset record by its GUID.
Get an ObjectTool to retrieve metadata for a specific object by its ID.
Get an Object's FieldsTool to retrieve metadata about fields for a specific object type in Fireberry.
Get an OpportunityTool to retrieve a specific opportunity record by its GUID.
Get an Order ItemTool to retrieve a specific order item record by its GUID.
Get a NoteTool to retrieve a specific note record by its GUID.
Get a phone call recordTool to retrieve a specific phone call record from Fireberry by its GUID.
Get a ProductTool to retrieve a specific product record by its GUID.
Get a ProjectTool to retrieve a specific project from Fireberry by its GUID.
Get a TaskTool to retrieve a specific task record by its GUID.
Get a TicketTool to retrieve a specific ticket (case) record by its GUID.
Get Campaign by IDTool to retrieve a single campaign by its GUID.
Get a CompetitorTool to retrieve a specific competitor record by its GUID.
Get a ContactTool to retrieve a specific contact record by its GUID.
Get Custom Object RecordTool to retrieve a specific custom object record by its GUID and object code.
Get Field DetailsTool to retrieve detailed metadata for a specific field in a Fireberry object/table.
Get Object Field ValuesTool to retrieve picklist field values from the metadata endpoint.
Get Items for an OrderTool to retrieve all items for a specific order from Fireberry.
Get Picklist Field ValuesTool to retrieve picklist field values from Fireberry metadata API.
Get Picklist ValuesTool to retrieve all possible picklist (dropdown) values for a specific field by querying records and extracting unique values.
Get Related RecordsTool to retrieve related records for a specific object in Fireberry.
Get Fireberry Task by IDTool to retrieve a single task record by its unique ID (GUID).
Get a Fireberry user by IDTool to retrieve a single user by their unique ID from Fireberry.
List All OpportunitiesTool to retrieve all opportunities from Fireberry CRM with pagination support.
List All ProductsTool to retrieve all products from Fireberry CRM with pagination support.
Fireberry: Query RecordsQuery and retrieve records from a Fireberry module with optional filtering, sorting, and pagination.
Query Fireberry records with filtersQuery records in any Fireberry object with advanced filtering, sorting, and pagination.
Update a Business UnitTool to update an existing business unit in Fireberry.
Update Fireberry AccountUpdates an existing account record in Fireberry with new field values.
Update a Fireberry CompetitorUpdates an existing competitor record in Fireberry by GUID.
Update a Fireberry contactTool to update an existing contact in Fireberry CRM.
Update a ContractTool to update an existing contract in Fireberry.
Update an Activity LogUpdate an existing Activity Log record in Fireberry.
Update a Date FieldTool to update a date field configuration in Fireberry.
Update a Date & Time FieldTool to update a Date & Time field's properties in Fireberry.
Update a Formula FieldTool to update a formula field in Fireberry CRM.
Update an HTML FieldTool to update an HTML field configuration in Fireberry.
Update a Fireberry MeetingTool to update an existing meeting (activity) in Fireberry.
Update a Fireberry articleUpdates an existing article in Fireberry.
Update an AssetUpdate an existing asset (accountproduct) in Fireberry.
Update an Email Address FieldTool to update the configuration of an email address field in Fireberry.
Update an OpportunityTool to update an existing opportunity in Fireberry CRM.
Update an Order ItemTool to update an existing order item in Fireberry.
Update a Number FieldTool to update a number field configuration in Fireberry.
Update a Phone Number FieldTool to update a phone number field configuration in Fireberry.
Update a ProductTool to update an existing product in Fireberry.
Update a ProjectTool to update an existing project in Fireberry CRM.
Update a Text Area FieldTool to update a Text Area field's properties in Fireberry.
Update a Text FieldTool to update a text field configuration in Fireberry.
Update a TicketTool to update an existing ticket (case) in Fireberry.
Update a URL FieldTool to update a URL field configuration in Fireberry.
Update a UserTool to update an existing user in Fireberry CRM.
Update a Fireberry CampaignTool to update an existing campaign in Fireberry by its GUID.
Update a CRM OrderTool to update an existing CRM order in Fireberry.
Update a phone call recordTool to update an existing phone call record in Fireberry.
Update a Task (V2)Tool to update an existing task using Fireberry v2 API.

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:

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

Step-by-step Guide

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 Fireberry 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 Fireberry

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

  const composioMCPUrl = session.mcp.url;
  console.log("Fireberry MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "fireberry" for Fireberry 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 Fireberry toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "fireberry-mastra-agent",
    instructions: "You are an AI agent with Fireberry 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: {
        fireberry: 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 Fireberry 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 Fireberry 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: ["fireberry"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "fireberry-mastra-agent",
    instructions: "You are an AI agent with Fireberry 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: { fireberry: 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 Fireberry 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

How to build Fireberry MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Fireberry MCP?

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

Can I use Tool Router MCP with Mastra AI?

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 Fireberry tools.

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

Yes, absolutely. You can configure which Fireberry 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.

How safe is my data with Composio Tool Router?

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 Fireberry data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.