How to integrate Mx technologies MCP with Mastra AI

GET STARTED FOR FREE
Framework Integration Gradient
Mx technologies Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Mx technologies to Mastra AI using the Composio tool router. By the end, you'll have a working Mx technologies agent that can create a manual account for a user, list account numbers for a specific member, fetch rewards for a connected member, get a configurable widget url for a user through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Mx technologies account through Composio's Mx technologies 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 Mx technologies tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Mx technologies 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 Mx technologies 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 Mx technologies MCP server, and what's possible with it?

The Mx technologies MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mx technologies account. It provides structured and secure access to financial data aggregation and account management features, so your agent can perform actions like creating accounts, managing members, fetching financial rewards, and handling account ownership on your behalf.

  • Automated account creation and management: Let your agent create new manual accounts, partner accounts, and user SSO accounts for seamless onboarding and testing.
  • Member aggregation and connection: Instruct your agent to create members and initiate aggregation of financial products across institutions, streamlining financial data collection.
  • Rewards and incentives tracking: Have your agent fetch and aggregate member rewards data after account connections, so you never miss out on incentives.
  • Secure access to account details: Direct your agent to list account owners, retrieve account numbers by member, and access configurable widget URLs for enhanced user interactions.
  • Credential and API management: Use your agent to retrieve API credentials for audience services, streamlining authentication flows and integrations.

Supported Tools & Triggers

Tools
Cancel Partner AccountTool to cancel (disable) a client account under a partner account.
Create accountTool to create a manual account for a given user.
Retrieve Audience API CredentialsTool to retrieve audience api credentials.
Create memberTool to create a member and start aggregating specified financial products.
Create Partner AccountTool to create a new client account under a partner account.
Create Partner Account User SSOTool to create a new partner account user with single sign-on enabled.
Fetch rewardsTool to initiate rewards aggregation for a specific member.
Get configurable widget URLTool to retrieve a configurable widget url for a user.
List Account Numbers by MemberTool to list account numbers for a specific member.
List account ownersTool to list account owners associated with a member's account.
List account owners by memberTool to list account owners for a specific member.
List accountsTool to list all accounts for a user.
List budgetsTool to list budgets for a specific user.
List categoriesTool to list all categories for a user.
List challengesTool to list mfa challenges for a member.
List Connect Widget URLsTool to list connect widget urls for a user.
List favorite institutionsTool to list partner favorite institutions, sorted by popularity.
List goalsTool to list goals for a specific user.
List institution credentialsTool to list credential fields required by a given institution.
List institutionsTool to list financial institutions supported by mx.
List member accountsTool to list accounts for a specific member.
List membersTool to list members associated with a specific user.
List rewardsTool to list rewards associated with a specific user and member.
List statements by memberTool to list statements for a member.
List taggingsTool to list all taggings for a specific user.
List tagsTool to list all tags for a user.
List transactionsTool to list transactions for a user.
List transactions by memberTool to list transactions for a member.
List usersTool to list users.
Read accountTool to retrieve details for a specific account.
Read account balanceTool to retrieve the available balance for a specific account.
Read categoryTool to retrieve a default category by guid.
Read FDX accountTool to return details for the specified fdx account.

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 Mx technologies 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 Mx technologies

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

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

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

OpenAI Agents SDK

OpenAI Agents SDK

Use Mx technologies MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Mx technologies MCP with Claude Agent SDK

Google ADK

Google ADK

Use Mx technologies MCP with Google ADK

LangChain

LangChain

Use Mx technologies MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Mx technologies MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Mx technologies MCP with LlamaIndex

CrewAI

CrewAI

Use Mx technologies MCP with CrewAI

Claude Code

Claude Code

Use Mx technologies MCP with Claude Code

Codex

Codex

Use Mx technologies MCP with Codex

FAQ

What are the differences in Tool Router MCP and Mx technologies MCP?

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

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

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