How to integrate Erpnext MCP with Claude Agent SDK

Framework Integration Gradient
Erpnext Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Erpnext to the Claude Agent SDK 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 Claude Agent SDK 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:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Erpnext
  • Configure an AI agent that can use Erpnext as a tool
  • Run a live chat session where you can ask the agent to perform Erpnext operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Erpnext account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Erpnext functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Erpnext
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["erpnext"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Erpnext
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Erpnext tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Erpnext
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Erpnext and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Erpnext
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["erpnext"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Erpnext tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Erpnext through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Erpnext MCP Agent with another framework

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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.