How to integrate Netsuite MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Netsuite logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Netsuite to Mastra AI using the Composio tool router. By the end, you'll have a working Netsuite agent that can generate monthly profit and loss report, list overdue invoices for all customers, create new sales order for a client through natural language commands.

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

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

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

The Netsuite MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Netsuite account. It provides structured and secure access to your business data, so your agent can perform actions like creating invoices, managing inventory, tracking customer records, and automating financial workflows on your behalf.

  • Automated invoice creation and management: Let your agent generate, send, and update invoices for customers, streamlining your accounts receivable process.
  • Real-time inventory control: Ask your agent to check stock levels, update inventory records, and manage supply chain transactions seamlessly.
  • Customer and vendor record management: Have the agent create, update, or retrieve customer and vendor profiles, keeping your CRM data fresh and accurate.
  • Financial reporting and analytics: Direct your agent to pull balance sheets, profit & loss statements, or transaction histories for up-to-date business insights.
  • Order processing automation: Enable your agent to create sales orders, manage purchase orders, and track fulfillment status across your operations.

Supported Tools & Triggers

Tools
Get Async Job StatusRetrieves the current status of an asynchronous NetSuite REST job.
Get Async Job TaskRetrieves the task reference (task ID and URL) for an asynchronous job in NetSuite.
Async Get Job Task ResultTool to retrieve the payload result of a completed async task.
Create CustomerCreates a new customer record in NetSuite.
Create Customer PaymentCreates a customer payment record in NetSuite.
Create EmployeeCreates a new employee record in NetSuite.
Create InvoiceTool to create a new invoice record.
Create ItemCreates a new item record in NetSuite via REST API.
Create Journal EntryTool to create a new journal entry record.
Create JWT Client AssertionTool to build a JWT client assertion for NetSuite OAuth2 client credentials.
Create Purchase OrderTool to create a new purchase order record.
Create RecordCreates a new NetSuite record of any type (customer, vendor, invoice, sales order, etc.
Create Sales OrderTool to create a new sales order record in NetSuite.
Create VendorCreates a new vendor record in NetSuite.
Create Vendor BillTool to create a new vendor bill record.
Delete CustomerTool to delete a customer record by ID.
Delete Customer PaymentDelete a customer payment record from NetSuite by its ID.
Delete EmployeeDeletes an employee record from NetSuite by its internal ID.
Delete InvoiceTool to delete an invoice record by ID.
Delete ItemTool to delete an item record by its type and ID.
Delete Item FulfillmentTool to delete an Item Fulfillment record.
Delete Item ReceiptTool to delete an item receipt record by ID.
Delete Journal EntryTool to delete a journal entry record by ID.
Delete Purchase OrderTool to delete a purchase order record by ID.
Delete Sales OrderTool to delete a sales order by internal ID.
Delete Vendor PaymentTool to delete a vendor payment record by ID.
Execute DatasetTool to execute a SuiteAnalytics dataset and return paged results.
Get CustomerTool to retrieve a customer record by internal ID.
Get Customer PaymentTool to retrieve a customer payment record by ID.
Get Data Center URLsTool to discover account-specific service domains.
Get EmployeeTool to retrieve an employee record by ID.
Get Governance LimitsRetrieve NetSuite account and integration concurrency governance limits.
Get InvoiceTool to retrieve an invoice record by internal ID.
Get ItemTool to retrieve an item record by internal ID.
Get Item FulfillmentTool to retrieve an item fulfillment record by internal ID.
Get Item ReceiptTool to retrieve an item receipt record by internal ID.
Get Journal EntryTool to retrieve a journal entry by internal ID.
Get Purchase OrderRetrieves complete details of a purchase order by its internal ID using the NetSuite REST API.
Get Record MetadataRetrieves the complete metadata schema for a NetSuite record type, including all field definitions, data types, constraints, and descriptions.
Get Reference Select FieldRetrieves the complete record referenced by a select-type field on a parent record.
Get Sales OrderTool to retrieve a sales order record by internal ID.
Get Server TimeTool to retrieve NetSuite server time in UTC.
Get Sublist CollectionTool to retrieve a sublist collection from a parent record.
Get Sublist LineTool to retrieve a specific line from a sublist of a record.
Get SubrecordRetrieves a specific subrecord from a parent NetSuite record.
Get VendorTool to get a single vendor record by internal ID.
Get Vendor BillRetrieve a vendor bill record by its internal ID.
Get Vendor PaymentRetrieves a single vendor payment record by its internal ID from NetSuite.
List Customer PaymentsTool to list customer payment records.
List DatasetsTool to list SuiteAnalytics Workbook datasets.
List EmployeesTool to list employee records.
List IntegrationsTool to list integration applications.
List InvoicesTool to list invoice records.
List Item FulfillmentsTool to list item fulfillment records.
List Item ReceiptsTool to list item receipt records.
List Journal EntriesTool to list journal entry records.
List Metadata CatalogTool to list all record types and their metadata.
List Purchase OrdersTool to list purchase order records.
List RecordsTool to list record instances.
List Sales OrdersTool to list sales order records.
List Vendor PaymentsTool to list vendor payment records.
OAuth2 Authorize Account DomainTool to construct an OAuth2 authorization URL for a NetSuite account-specific domain.
OAuth2 Authorize System DomainInitiates the OAuth2 authorization code flow using NetSuite's system domain endpoint.
Get OAuth2 JWKS KeysTool to retrieve OAuth2 JWKS public keys.
OAuth2 LogoutTool to revoke an ID token and its associated access and refresh tokens.
Revoke OAuth2 Refresh TokenRevokes a NetSuite OAuth2 refresh token and all associated access tokens, immediately invalidating them.
Exchange OAuth2 Authorization Code for TokensExchange an OAuth2 authorization code for access and refresh tokens using the NetSuite token endpoint.
OAuth2 Token Client CredentialsTool to obtain an OAuth2 access token via client credentials grant.
OAuth2 Token RefreshTool to refresh an OAuth2 access token.
Run SuiteQL QueryTool to execute a SuiteQL query.
Transform RecordTransform an existing NetSuite record into another record type (e.
Update CustomerUpdates an existing NetSuite customer record using PATCH semantics - only fields included in the 'data' parameter are modified.
Update Customer PaymentTool to update an existing customer payment by ID.
Update EmployeeTool to update an employee record by ID.
Update InvoiceUpdates an existing NetSuite invoice record by ID using the PATCH method.
Update ItemTool to update an item record by ID.
Update Item FulfillmentTool to update an Item Fulfillment record by ID.
Update Item ReceiptTool to update an item receipt record by ID.
Update Journal EntryTool to update a journal entry record by ID.
Update Purchase OrderTool to update a purchase order record by ID.
Update Sales OrderUpdates an existing NetSuite sales order record by ID using PATCH semantics.
Update VendorTool to update a vendor record by ID.
Update Vendor BillTool to update a vendor bill record by ID.
Update Vendor PaymentTool to update a vendor payment record by ID.
Upsert Record by External IDTool to create or update a record by external ID.

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

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

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

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

FAQ

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

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

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

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