How to integrate Centralstationcrm MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Centralstationcrm Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Centralstationcrm to Mastra AI using the Composio tool router. By the end, you'll have a working Centralstationcrm agent that can add new company to crm contacts, log a sales opportunity for a client, count total people in my crm, record a birthday for an existing contact through natural language commands.

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

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

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

The Centralstationcrm MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Centralstationcrm account. It provides structured and secure access to your customer relationship data, so your agent can perform actions like managing contacts, creating deals, updating company records, and tracking key interactions on your behalf.

  • Automated contact management: Quickly add new people to your CRM, update their details, and ensure your contact database stays current without manual entry.
  • Company and organization creation: Effortlessly create new company records so you can keep your account-based selling and organization tracking up-to-date.
  • Deal tracking and creation: Instantly log new sales opportunities by creating deals linked to your contacts or companies, helping your team stay on top of the pipeline.
  • Detailed relationship enrichment: Add addresses, assistants, avatars, and contact details to people in your CRM, making every customer profile richer and more actionable.
  • Milestone and history recording: Record important life events or milestones (like birthdays or anniversaries) for each person to boost relationship management and personalized outreach.

Supported Tools & Triggers

Tools
Check ConnectionTool to verify the connection status of the centralstationcrm api key.
Count PeopleTool to retrieve the total number of people in the account.
Create CompanyTool to create a new company record.
Create DealTool to create a new deal record.
Create PersonTool to create a new person record.
Create Person AddressTool to create a new address for a specific person.
Create Person AssistantTool to create a new assistant (assi) entry for a specific person.
Create Person AvatarTool to create a new avatar for a specific person.
Create Person Contact DetailTool to create a new contact detail for a specific person.
Create Person Historic EventTool to create a new historic event for a specific person.
Delete CompanyTool to delete a company record by id.
Delete personTool to delete a person record by id.
Delete Person AddressTool to delete a person's address by its id.
Delete Person AssiTool to delete an assi entry of a person.
Delete Person AvatarTool to delete a person's avatar by its id.
Delete Person Contact DetailTool to delete a contact detail of a person.
Delete Person Historic EventTool to delete a historic event of a person by its id.
Get API User MaildropTool to retrieve the current api user's maildrop for people and companies.
Get CompanyTool to retrieve details of a specific company by id.
Get DealTool to retrieve details of a specific deal by its id.
Get DealsTool to retrieve a paginated list of all deals.
Get PersonTool to retrieve details of a specific person by id.
Get Person AddressTool to retrieve a specific address of a person by address id.
Get Person AddressesTool to retrieve all addresses for a specific person.
Get Person AssiTool to retrieve a specific assi entry of a person by id.
Get Person AssisTool to retrieve all assistant entries for a specific person.
Get Person AvatarTool to retrieve a specific avatar of a person by avatar id.
Get Person AvatarsTool to retrieve all avatars for a specific person.
Get Person Contact DetailTool to retrieve a specific contact detail by id for a person.
Get Person Custom FieldsTool to retrieve all custom fields for a specific person.
Get Person Historic EventTool to retrieve a specific historic event of a person by id.
Get Person Historic EventsTool to retrieve all historic events for a specific person.
Get PersonsTool to retrieve a paginated list of all people.
Merge PersonTool to merge another person into an existing person by id.
Search RecordsSearch records
Search PeopleTool to retrieve people matching search criteria.
Stats PeopleTool to retrieve key statistics about people.
Update CompanyTool to update an existing company by id.
Update PersonTool to update an existing person by id.
Update Person AddressTool to update a specific address of a person.
Update Person AssiTool to update an assi entry of a person.
Update Person Contact DetailTool to update a specific contact detail of a person by id.
Update Person Historic EventTool to update a historic event of a person by id.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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 Centralstationcrm 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 Centralstationcrm

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

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

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "centralstationcrm-mastra-agent",
    instructions: "You are an AI agent with Centralstationcrm 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: { centralstationcrm: 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 Centralstationcrm 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 Centralstationcrm MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Centralstationcrm MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Centralstationcrm MCP with Claude Agent SDK

Google ADK

Google ADK

Use Centralstationcrm MCP with Google ADK

LangChain

LangChain

Use Centralstationcrm MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Centralstationcrm MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Centralstationcrm MCP with LlamaIndex

CrewAI

CrewAI

Use Centralstationcrm MCP with CrewAI

FAQ

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

With a standalone Centralstationcrm MCP server, the agents and LLMs can only access a fixed set of Centralstationcrm tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Centralstationcrm 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 Centralstationcrm tools.

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

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

Book a call↗Get started for free