
ERPNext MCP Server
Enables comprehensive interaction with ERPNext systems through natural language, providing secure access to any document type (customers, items, invoices, etc.) with enterprise-grade permission controls and audit logging.
README
ERPNext MCP Server
A comprehensive Model Context Protocol (MCP) server for ERPNext that provides generic, doctype-agnostic access to any ERPNext document type with robust permission controls, audit logging, and enterprise-grade security.
🏗️ Architecture Overview
graph TB
A[Claude/LLM Client] --> B[MCP Protocol]
B --> C[ERPNext MCP Server]
C --> D[Permission Manager]
C --> E[ERPNext Client]
C --> F[Cache Manager]
C --> G[Rate Limiter]
E --> H[ERPNext API]
D --> I[Audit Logger]
subgraph "Permission System"
D --> J[Doctype Permissions]
D --> K[Field-Level Control]
D --> L[Operation Validation]
D --> M[Condition Checking]
end
subgraph "ERPNext Integration"
E --> N[Generic CRUD]
E --> O[Search & Filter]
E --> P[Schema Discovery]
end
Core Components
- 🔧 Generic Client: Works with any ERPNext doctype (Customer, Item, Sales Order, etc.)
- 🛡️ Permission System: Multi-layer access control with field-level restrictions
- 📊 Audit System: Comprehensive logging of all operations
- ⚡ Performance: Built-in caching and rate limiting
- 🔍 Discovery: Dynamic tool generation based on configured doctypes
🚀 Quick Start
1. Installation
# Clone/create project
mkdir erpnext_mcp_server && cd erpnext_mcp_server
# Create virtual environment
python -m venv venv
source venv/bin/activate # Windows: venv\Scripts\activate
# Install dependencies
pip install mcp httpx pydantic python-dotenv typing-extensions
2. Configuration
Create config/config.json
:
{
"erpnext": {
"url": "https://your-erpnext-instance.com",
"api_key": "your_api_key",
"api_secret": "your_api_secret"
},
"permissions": {
"doctypes": {
"Customer": {
"read": true,
"create": true,
"update": true,
"delete": false,
"allowed_fields": ["customer_name", "email_id", "mobile_no"],
"conditions": {
"create": {"customer_type": ["Company", "Individual"]}
}
}
}
}
}
3. Run Server
python -m src.server
🔐 Permission Model
Multi-Layer Security Architecture
The permission system operates on four security layers:
1. Operation-Level Permissions
{
"Customer": {
"read": true, // Allow reading customers
"create": true, // Allow creating customers
"update": true, // Allow updating customers
"delete": false // Deny deleting customers
}
}
2. Field-Level Access Control
{
"Customer": {
"allowed_fields": [
"customer_name", "email_id", "mobile_no", "website"
],
"restricted_fields": [
"creation", "modified", "owner", "credit_limit"
]
}
}
3. Conditional Validation
{
"Customer": {
"conditions": {
"create": {
"customer_type": ["Company", "Individual"],
"territory": ["Egypt", "UAE", "Saudi Arabia"]
},
"update": {
"status": {"not_in": ["Disabled", "Blocked"]}
}
}
}
}
4. Audit & Monitoring
{
"audit": {
"enabled": true,
"log_file": "logs/audit.log",
"retention_days": 30
}
}
Permission Examples
Restrictive Configuration (Read-only analyst)
{
"permissions": {
"doctypes": {
"Customer": {
"read": true,
"create": false,
"update": false,
"delete": false,
"allowed_fields": ["name", "customer_name", "territory", "customer_group"]
},
"Sales Invoice": {
"read": true,
"create": false,
"update": false,
"delete": false,
"allowed_fields": ["name", "customer", "total", "status", "posting_date"]
}
}
}
}
Operational Configuration (Sales user)
{
"permissions": {
"doctypes": {
"Customer": {
"read": true,
"create": true,
"update": true,
"delete": false,
"allowed_fields": [
"customer_name", "customer_type", "email_id", "mobile_no",
"customer_group", "territory", "website"
],
"conditions": {
"create": {"customer_type": ["Company", "Individual"]},
"update": {"status": {"not_in": ["Disabled"]}}
}
}
}
}
}
🛠️ Available Tools & Usage
System Tools
test_connection
Test ERPNext server connectivity
Test the ERPNext connection
list_doctypes
Show all configured doctypes and permissions
List all available document types and their permissions
get_doctype_permissions
Get detailed permissions for specific doctype
Show me the permissions for Customer doctype
Generic Document Operations
get_generic_document
Get any document by doctype and name
Get the Customer document named "ABC Company"
list_generic_documents
List documents for any doctype with filters
List all Items where item_group is "Raw Materials" and limit to 10 results
create_generic_document
Create document for any doctype
Create a new Customer with name "XYZ Corp", type "Company", and email "contact@xyz.com"
Doctype-Specific Tools
For each configured doctype, the server automatically generates:
list_{doctype}_documents
- List documentsget_{doctype}_document
- Get specific documentsearch_{doctype}_documents
- Search documentscreate_{doctype}_document
- Create new documentupdate_{doctype}_document
- Update documentdelete_{doctype}_document
- Delete document (if permitted)
Example Usage with Claude
Data Analysis
Show me the top 10 customers by territory and their contact information
→ Uses list_customer_documents
with filters
Data Entry
Create a new customer named "Tech Solutions Ltd" as a Company type in Egypt territory with email info@techsolutions.com
→ Uses create_customer_document
with validation
Information Retrieval
Get details for sales invoice INV-2024-001 including customer and payment status
→ Uses get_sales_invoice_document
Search & Discovery
Find all items containing "laptop" in the name and show their prices
→ Uses search_item_documents
⚙️ Advanced Configuration
Rate Limiting
{
"rate_limiting": {
"enabled": true,
"requests_per_minute": 60,
"requests_per_hour": 1000
}
}
Caching
{
"cache": {
"enabled": true,
"ttl": 300,
"max_size": 1000
}
}
Environment Variables
# Alternative to config file
export ERPNEXT_URL="https://your-instance.com"
export ERPNEXT_API_KEY="your_key"
export ERPNEXT_API_SECRET="your_secret"
export MCP_AUDIT_ENABLED="true"
export MCP_LOG_LEVEL="INFO"
🔒 Security Considerations
Authentication
- Uses ERPNext API Key/Secret authentication
- No passwords stored in configuration
- Supports ERPNext user-level permissions
Data Protection
- Field-level access control prevents sensitive data exposure
- Audit logging tracks all access attempts
- Rate limiting prevents abuse
- Input validation prevents injection attacks
Network Security
- HTTPS-only connections to ERPNext
- Configurable request timeouts
- Connection pooling with limits
Audit Trail
All operations are logged with:
- Timestamp and user context
- Operation type and target doctype
- Success/failure status and reasons
- Data accessed/modified (field names only)
- IP address and session information
Example audit log:
2024-01-15 10:30:45 - INFO - Operation: READ | DocType: Customer | Result: ALLOWED | Document: ABC Corp | Fields: ['customer_name', 'email_id', 'territory']
2024-01-15 10:31:12 - WARNING - Operation: DELETE | DocType: Customer | Result: DENIED | Reason: Delete operation not allowed for doctype 'Customer'
🧪 Testing & Validation
Test Connection
python test_client.py
Validate Permissions
from src.permissions import PermissionManager
config = {...} # Your config
pm = PermissionManager(config)
# Test permissions
can_read = pm.can_read("Customer")
can_create = pm.can_create("Sales Order")
allowed_fields = pm.get_allowed_fields("Item")
# Validate operation
allowed, reason = pm.validate_operation("create", "Customer", {
"customer_name": "Test Corp",
"customer_type": "Company"
})
Performance Testing
import asyncio
from src.erpnext_client import ERPNextClient
# Test rate limiting and caching
client = ERPNextClient(url, key, secret, config)
# This should hit cache after first request
for i in range(10):
result = await client.get_doctype_list("Customer")
print(f"Request {i+1}: {len(result['data'])} customers")
🏃♂️ Deployment
Production Configuration
{
"erpnext": {
"url": "https://your-production-instance.com",
"timeout": 60
},
"rate_limiting": {
"enabled": true,
"requests_per_minute": 30,
"requests_per_hour": 500
},
"audit": {
"enabled": true,
"log_level": "INFO",
"retention_days": 90
},
"cache": {
"enabled": true,
"ttl": 600
}
}
Claude Desktop Integration
Add to claude_desktop_config.json
:
{
"mcpServers": {
"erpnext": {
"command": "python",
"args": ["-m", "src.server"],
"cwd": "/path/to/erpnext_mcp_server",
"env": {
"MCP_LOG_LEVEL": "INFO"
}
}
}
}
Docker Deployment
FROM python:3.11-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install -r requirements.txt
COPY . .
EXPOSE 8080
CMD ["python", "-m", "src.server"]
🚨 Failure Modes & Recovery
Connection Failures
- Automatic retry with exponential backoff
- Graceful degradation when ERPNext is unavailable
- Connection pooling prevents resource exhaustion
Permission Violations
- All unauthorized operations are blocked and logged
- Clear error messages explain permission requirements
- No partial operations - atomic success/failure
Rate Limiting
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.