How to integrate Erpnext MCP with Google ADK

Framework Integration Gradient
Erpnext Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Erpnext to Google ADK 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 Google ADK 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 a Erpnext account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Erpnext
  • Build an agent that connects to Erpnext through MCP
  • Interact with Erpnext using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Erpnext via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["erpnext"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Erpnext operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

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

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["erpnext"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Erpnext operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Erpnext with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Erpnext using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Erpnext tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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 Google ADK?

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