How to integrate Erpnext MCP with LlamaIndex

This guide walks you through connecting Erpnext to LlamaIndex 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 LlamaIndex 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.

Erpnext logoErpnext
Api Key

Erpnext is a free, open-source ERP platform built on the Frappe Framework. It streamlines business operations by integrating accounting, inventory, HR, and more in one place.

52 Tools

Introduction

This guide walks you through connecting Erpnext to LlamaIndex 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 LlamaIndex 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.

Also integrate Erpnext with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Erpnext
  • Connect LlamaIndex to the Erpnext MCP server
  • Build a Erpnext-powered agent using LlamaIndex
  • Interact with Erpnext through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Erpnext account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Erpnext

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Erpnext access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called erpnext_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["erpnext"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Erpnext actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, erpnext)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Erpnext tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Erpnext
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Erpnext tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Erpnext
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Erpnext, then start asking questions.

Complete Code

Here's the complete code to get you started with Erpnext and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["erpnext"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Erpnext actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Erpnext to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Erpnext tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Erpnext action and event your agent gets out of the box.

Add Comment

Tool to add a comment to a document in ERPNext/Frappe.

Add Tag

Tool to add a tag to a document in ERPNext.

Apply Workflow

Tool to apply a workflow action to a document in ERPNext/Frappe.

Cancel Document

Cancel a submitted document in ERPNext/Frappe to change its status from Submitted to Cancelled.

Create Document

Tool to create a new document of a specific DocType in ERPNext.

Create Timesheet

Tool to create a new Timesheet record in ERPNext.

Create Webhook

Tool to create a new webhook configuration in ERPNext.

Delete Document

Tool to delete a document using the Frappe client API.

Delete Document

Tool to delete a specific document by DocType and name.

Download file from ERPNext

Tool to download a file from ERPNext by its URL.

Download PDF Document

Tool to download a document as PDF from ERPNext with optional print format.

Get All Languages

Tool to get a list of all available languages in the ERPNext/Frappe system.

Get All Roles

Tool to get a list of all roles available in the ERPNext system.

Get Document

Tool to get a single document by DocType and name or filters from Frappe/ERPNext.

Get Document Count

Tool to get the count of documents matching specified filters in ERPNext/Frappe.

Get DocType Metadata

Tool to retrieve complete DocType metadata/schema including field definitions, field types, permissions, and configurations.

Get Document

Tool to retrieve a specific document by its DocType and name (ID).

Get Document with Metadata

Tool to retrieve a document with full metadata including attachments, comments, activity logs, and related information.

Get Exchange Rate

Tool to get the currency exchange rate between two currencies in ERPNext.

Get Fiscal Year

Tool to get fiscal year information for a given date in ERPNext.

Get Framework Version

Tool to get the Frappe framework version and all installed app versions.

Get Item Details

Tool to get detailed item information including pricing, taxes, and stock details from ERPNext.

Get List of Documents

Tool to retrieve a list of documents from ERPNext/Frappe with filtering, field selection, and pagination.

Get Logged User

Tool to get the email/ID of the currently authenticated user.

Get Party Details

Tool to get comprehensive customer or supplier details including addresses, contacts, and default financial settings.

Get Payment Entry

Tool to get payment entry details for an invoice or order from ERPNext.

Get Stock Balance

Tool to retrieve the current stock balance for a specific item in a warehouse.

Get Timezones

Tool to get a list of all available timezones in the ERPNext system.

Get User Roles

Tool to get roles assigned to a user.

Get Field Value

Tool to get specific field value(s) from a document in ERPNext.

Get Workflow Transitions

Tool to get available workflow transitions for a document.

Insert Document

Tool to insert a new document in ERPNext/Frappe using the client API.

Insert Multiple Documents

Tool to insert multiple documents at once into ERPNext/Frappe.

List DocTypes

Tool to get a list of all DocTypes available in the ERPNext system.

List ERPNext Documents

Tool to list documents of a specific DocType from ERPNext.

List Employees

Tool to retrieve a list of Employee records from ERPNext.

List Projects

Tool to retrieve a list of Project records from ERPNext.

List Timesheets

Tool to get a list of Timesheet records from ERPNext.

List Webhooks

Tool to list webhook configurations in ERPNext.

Make Delivery Note

Create a draft Delivery Note from an existing Sales Order in ERPNext.

Make Purchase Order

Create a draft Purchase Order from an existing Material Request in ERPNext.

Make Sales Invoice

Tool to create a Sales Invoice from an existing Sales Order in ERPNext.

Make Stock Entry

Tool to create a Stock Entry for material transfer, receipt, or issue in ERPNext.

Ping API

Tool to check if the ERPNext/Frappe API is reachable.

Rename Document

Tool to rename an ERPNext document by changing its unique ID/name.

Save Document with Action

Tool to save, submit, cancel, or update a document in ERPNext.

Save Document

Tool to save an existing ERPNext/Frappe document with changes.

Global Search

Tool to perform global text search across ERPNext documents.

Search Link Field Documents

Tool to search for documents to link in ERPNext/Frappe Link fields.

Set Value

Tool to set a specific field value on a document in ERPNext.

Submit Document

Submit a draft document in ERPNext/Frappe to change its status from Draft to Submitted.

Update ERPNext document

Tool to update a specific ERPNext document.

FAQ

Frequently asked questions

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.

Yes, you can. LlamaIndex 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.

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.

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.

Start with Erpnext.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Erpnext tool your agent needs.Free to start.

Start building
Erpnext MCP Integration with LlamaIndex | Composio