MCP Erpnext — AI skill for Claude Code
Let AI agents operate your ERPNext — documents, workflows, and interactive viewers.
How to install MCP Erpnext
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open Casys-AI/mcp-erpnext and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What MCP Erpnext does
Let AI agents operate your ERPNext — documents, workflows, and interactive viewers.
Alternatives in AI
- WeKnora — Open-source LLM knowledge platform: turn raw documents into a queryable RAG, an autonomous reasoning agent, an 26.9k ★
- Part 4 — Generate AGENTS.md And AI Agent Configuration Files — I'll help you create the instruction files that will guide your AI coding assistant to build your MVP 2.1k ★
- Llmwiki — Open Source Implementation of Karpathy's LLM Wiki 1.5k ★
README
English | [繁體中文](README.zh-TW.md)
@casys/mcp-erpnext
[](https://jsr.io/@casys/mcp-erpnext) [](https://www.npmjs.com/package/@casys/mcp-erpnext) [](https://github.com/Casys-AI/mcp-erpnext/actions/workflows/test.yml) [](https://modelcontextprotocol.io) [](LICENSE)
[!IMPORTANT] **Installing the 3.1 beta:** pin the prerelease while this UX is being validated. For npm/Node use `npx -y @casys/mcp-erpnext@3.1.0-beta.3`; for Deno use `deno run -A jsr:@casys/mcp-erpnext@3.1.0-beta.3/server`. The moving npm alias is `@next`. The beta adds the generic document viewer and attachment workflows, so test it with the MCP host your users actually run before replacing a stable deployment.
Let any MCP-compatible AI agent operate your [ERPNext](https://erpnext.com) / Frappe instance — documents, workflows, and interactive viewers inside the host (Claude Desktop, Claude Code, VS Code Copilot, or custom).
Works with **self-hosted** and **ERPNext Cloud** (frappe.cloud) instances.
Built on **[@casys/mcp-server](https://github.com/Casys-AI/mcp-server)** — the MCP server framework (concurrency, auth, MCP Apps, observability) that powers this project.
Screenshots
Interactive viewers rendered inside an MCP host, driven entirely by tool results.
