How to integrate Erpnext MCP with Mastra AI

GET STARTED FOR FREE
Framework Integration Gradient
Erpnext Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Erpnext to Mastra AI using the Composio tool router. By the end, you'll have a working Erpnext agent that can list overdue tasks for all projects, create a new customer record, get all open purchase orders through natural language commands.

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

The Erpnext MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Erpnext account. It provides structured and secure access so your agent can perform Erpnext operations on your behalf.

Supported Tools & Triggers

Tools
Add CommentTool to add a comment to a document in ERPNext/Frappe.
Add TagTool to add a tag to a document in ERPNext.
Apply WorkflowTool to apply a workflow action to a document in ERPNext/Frappe.
Cancel DocumentCancel a submitted document in ERPNext/Frappe to change its status from Submitted to Cancelled.
Create DocumentTool to create a new document of a specific DocType in ERPNext.
Create TimesheetTool to create a new Timesheet record in ERPNext.
Create WebhookTool to create a new webhook configuration in ERPNext.
Delete DocumentTool to delete a document using the Frappe client API.
Delete DocumentTool to delete a specific document by DocType and name.
Download file from ERPNextTool to download a file from ERPNext by its URL.
Download PDF DocumentTool to download a document as PDF from ERPNext with optional print format.
Get All LanguagesTool to get a list of all available languages in the ERPNext/Frappe system.
Get All RolesTool to get a list of all roles available in the ERPNext system.
Get DocumentTool to get a single document by DocType and name or filters from Frappe/ERPNext.
Get Document CountTool to get the count of documents matching specified filters in ERPNext/Frappe.
Get DocType MetadataTool to retrieve complete DocType metadata/schema including field definitions, field types, permissions, and configurations.
Get DocumentTool to retrieve a specific document by its DocType and name (ID).
Get Document with MetadataTool to retrieve a document with full metadata including attachments, comments, activity logs, and related information.
Get Exchange RateTool to get the currency exchange rate between two currencies in ERPNext.
Get Fiscal YearTool to get fiscal year information for a given date in ERPNext.
Get Framework VersionTool to get the Frappe framework version and all installed app versions.
Get Item DetailsTool to get detailed item information including pricing, taxes, and stock details from ERPNext.
Get List of DocumentsTool to retrieve a list of documents from ERPNext/Frappe with filtering, field selection, and pagination.
Get Logged UserTool to get the email/ID of the currently authenticated user.
Get Party DetailsTool to get comprehensive customer or supplier details including addresses, contacts, and default financial settings.
Get Payment EntryTool to get payment entry details for an invoice or order from ERPNext.
Get Stock BalanceTool to retrieve the current stock balance for a specific item in a warehouse.
Get TimezonesTool to get a list of all available timezones in the ERPNext system.
Get User RolesTool to get roles assigned to a user.
Get Field ValueTool to get specific field value(s) from a document in ERPNext.
Get Workflow TransitionsTool to get available workflow transitions for a document.
Insert DocumentTool to insert a new document in ERPNext/Frappe using the client API.
Insert Multiple DocumentsTool to insert multiple documents at once into ERPNext/Frappe.
List DocTypesTool to get a list of all DocTypes available in the ERPNext system.
List ERPNext DocumentsTool to list documents of a specific DocType from ERPNext.
List EmployeesTool to retrieve a list of Employee records from ERPNext.
List ProjectsTool to retrieve a list of Project records from ERPNext.
List TimesheetsTool to get a list of Timesheet records from ERPNext.
List WebhooksTool to list webhook configurations in ERPNext.
Make Delivery NoteCreate a draft Delivery Note from an existing Sales Order in ERPNext.
Make Purchase OrderCreate a draft Purchase Order from an existing Material Request in ERPNext.
Make Sales InvoiceTool to create a Sales Invoice from an existing Sales Order in ERPNext.
Make Stock EntryTool to create a Stock Entry for material transfer, receipt, or issue in ERPNext.
Ping APITool to check if the ERPNext/Frappe API is reachable.
Rename DocumentTool to rename an ERPNext document by changing its unique ID/name.
Save Document with ActionTool to save, submit, cancel, or update a document in ERPNext.
Save DocumentTool to save an existing ERPNext/Frappe document with changes.
Global SearchTool to perform global text search across ERPNext documents.
Search Link Field DocumentsTool to search for documents to link in ERPNext/Frappe Link fields.
Set ValueTool to set a specific field value on a document in ERPNext.
Submit DocumentSubmit a draft document in ERPNext/Frappe to change its status from Draft to Submitted.
Update ERPNext documentTool to update a specific ERPNext document.

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

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

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

Create the Mastra agent

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

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

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

OpenAI Agents SDK

OpenAI Agents SDK

Use Erpnext MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Erpnext MCP with Claude Agent SDK

Google ADK

Google ADK

Use Erpnext MCP with Google ADK

LangChain

LangChain

Use Erpnext MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Erpnext MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Erpnext MCP with LlamaIndex

CrewAI

CrewAI

Use Erpnext MCP with CrewAI

Claude Code

Claude Code

Use Erpnext MCP with Claude Code

Codex

Codex

Use Erpnext MCP with Codex

FAQ

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

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

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

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