How to integrate Neutrino MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Neutrino logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Neutrino to Mastra AI using the Composio tool router. By the end, you'll have a working Neutrino agent that can detect profanity in user-submitted comments, convert 50 usd to eur instantly, geocode address to get latitude and longitude through natural language commands.

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

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

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

The Neutrino MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Neutrino account. It provides structured and secure access to Neutrino’s robust suite of APIs, so your agent can validate data, analyze geolocations, assess security risks, convert currencies, and clean content automatically on your behalf.

  • Real-time data validation and analysis: Have your agent validate email addresses, check mobile numbers, and analyze BIN (bank identification numbers) for accuracy and reliability.
  • Geolocation and address intelligence: Ask your agent to geocode addresses to coordinates, or perform reverse geocoding to turn latitude and longitude into real-world locations for smarter workflows.
  • Content safety and cleaning: Let your agent scan text for profanity using the Bad Word Filter or sanitize untrusted HTML to ensure safe, presentable content anywhere it’s needed.
  • Security and risk assessment: Automate reputation checks on hosts and domains, enabling your agent to proactively identify potential threats or block risky sources without manual effort.
  • Currency and unit conversion: Empower your agent to convert between different units or currencies on demand, streamlining financial or scientific operations with ease.

Supported Tools & Triggers

Tools
Add Watermark to ImageAdd a watermark to an image with customizable position, opacity, and output format.
Bad Word FilterTool to detect bad words and profanity in text.
BIN LookupPerform a BIN (Bank Identification Number) lookup to retrieve comprehensive card issuer information.
IP BlocklistCheck if an IP address is on a blocklist.
Convert ValueTool to perform unit and currency conversions.
Validate and analyze an email addressValidates and analyzes email addresses for syntax, domain validity, DNS/MX records, and detects freemail/disposable providers.
Verify Email AddressTool to verify and analyze the deliverability of an email address.
Geocode AddressTool to geocode an address.
Reverse GeocodeConvert geographic coordinates (latitude/longitude) into real-world address information.
HLR LookupPerform real-time HLR (Home Location Register) lookup to validate mobile numbers and retrieve detailed network information.
Host ReputationCheck if an IP address, domain, or URL is listed on DNS-based Blackhole Lists (DNSBLs).
HTML CleanTool to clean and sanitize untrusted HTML.
HTML RenderRender HTML content to PDF, PNG, or JPG format.
Resize ImageResize, crop, and convert images to PNG or JPG format.
IP InfoGet comprehensive geolocation and network information for an IPv4 or IPv6 address.
IP ProbeAnalyzes an IPv4 or IPv6 address to extract detailed network intelligence including geolocation, ISP/hosting provider information, ASN details, and security flags (VPN, proxy, TOR detection).
Domain LookupTool to perform a domain lookup to retrieve WHOIS, DNS records, domain registration information and detect potentially malicious or dangerous domains.
Phone ValidateTool to validate and lookup phone numbers.
QR CodeGenerate a QR code or Code 128 barcode as a PNG image.
Browser BotTool to automate browser interactions using a real Chromium browser.
SMS VerifyTool to send a unique security code via SMS.
UA LookupParse and analyze User-Agent strings to extract detailed browser, device, and operating system information.
URL InfoTool to parse, analyze, and retrieve content from the supplied URL.
Verify Security CodeVerify a security code generated by SMS Verify or Phone Verify APIs.

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

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

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

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Neutrino MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Neutrino MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Neutrino MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Neutrino MCP with Claude Cowork

Codex logo

Codex

Use Neutrino MCP with Codex

OpenClaw logo

OpenClaw

Use Neutrino MCP with OpenClaw

Hermes logo

Hermes

Use Neutrino MCP with Hermes

CLI logo

CLI

Use Neutrino MCP with CLI

Google ADK logo

Google ADK

Use Neutrino MCP with Google ADK

LangChain logo

LangChain

Use Neutrino MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Neutrino MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Neutrino MCP with LlamaIndex

CrewAI logo

CrewAI

Use Neutrino MCP with CrewAI

FAQ

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

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

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

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

Get started for freeGet a demo↗