Get started free
All integrations

ERPNext integration

An ERPNext or Frappe site over its generic REST API: list, read, create, update and delete documents of any DocType, count matching documents, call a whitelisted server method, and upload a file. The endpoints are generic rather than per module, so the same calls reach Customer, Sales Order, Item or any custom DocType. The site host is part of the connection.

9 toolsCustom authAPI docs

Common ERPNext use cases

  • submitting or cancelling a document
  • reading a full sales order including its item rows
  • attaching a generated document to an ERPNext record
  • creating a customer or a sales order from a workflow
  • removing a draft document a workflow created by mistake
  • reading the documents of a DocType that match a condition
  • writing a status or a reference back onto an ERPNext document
  • reaching functionality the generic document calls do not cover
  • checking whether anything matches before paging through a DocType
  • paging through a large DocType

What you can do with ERPNext

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 6 operations

  • GETcount_documents

    Returns how many documents of a DocType match a filter, without listing them.

  • POSTcreate_document

    Creates a document and returns it as stored, including its generated name.

  • DELETEdelete_document

    Deletes a document, provided nothing else links to it.

  • GETget_document

    Returns a full document, including the rows of its child tables.

  • GETlist_documents

    Returns the documents of one DocType under a data array.

  • PUTupdate_document

    Updates the fields you send on a document and returns the stored result.

Method, 2 operations

  • GETcall_method_get

    Calls a whitelisted server method that only reads, and returns its result.

  • POSTcall_method_post

    Calls a whitelisted server method that changes state and returns its result.

File, 1 operation

  • POSTupload_file

    Uploads a file to the site and returns the File document that was created.

Use ERPNext from Claude Code, Cursor or Codex

Connect ERPNext in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ERPNext operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect ERPNext

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect ERPNext once

    Add your ERPNext connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

ERPNext integration FAQ

What can you do with the ERPNext integration?
LiveContext exposes 9 operations on ERPNext, covering document, method and file. Common uses include submitting or cancelling a document, reading a full sales order including its item rows and attaching a generated document to an ERPNext record.

Popular integrations

Browse the whole catalog