"ERPNext" matching MCP servers:

Enables AI agents to read and operate ERPNext/Frappe systems through HTTP APIs, with safe-mode approval for sensitive operations and complete storage of large request and response payloads.

A robust, asynchronous Model Context Protocol (MCP) server that securely connects LLMs to your ERPNext instance (Self-Hosted or Frappe Cloud) via its REST API.

Integrates Claude with ERPNext v16, enabling CRUD operations, queries, and method calls through a secure MCP interface.

A comprehensive MCP server for ERPNext providing generic, doctype-agnostic access to any ERPNext document type with robust permission controls, audit logging, and enterprise-grade security.

This MCP server connects ChatGPT to ERPNext, enabling AI-powered business analytics, report generation, and document management.

Enables interaction with ERPNext instances via its REST API to manage documents, inventory, and reports. It supports full CRUD operations, submittable document workflows, and schema inspection through natural language.

Enables users to manage CRM leads, opportunities, projects, tasks, and sales records within ERPNext directly through MCP-compatible clients. It supports global searches, timesheet entries, and access to dashboard KPIs using natural language.

MCP server for ERPNext that provides read-only access to business data and controlled creation/update of draft documents, with strict security, RBAC, field whitelisting, audit, idempotency, and optimistic locking.

Enables AI assistants and automation tools to securely query ERPNext data through 16 read-only tools, with OAuth 2.0 or API-key authentication and usage telemetry.

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.

Enables generic CRUD operations on ERPNext/Frappe DocTypes via MCP tools, allowing users to interact with ERPNext data like documents, reports, and schema through natural language commands.

Enables profile-scoped access to sales, purchase, and accounts workflows through MCP, including reads, queries, lifecycle actions, PDFs, emails, and governed approval-based writes subject to native Frappe permissions.

Connects MCP clients to Frappe/ERPNext sites via REST API, enabling document CRUD, search, and remote method calls.

Enables LLMs to interact with any ERPNext instance through comprehensive CRUD operations, advanced permissions, and a web chat interface.

Universal dynamic MCP server for Frappe & ERPNext v16, exposing 36 tools, resources, prompts, SSE transport, and real-time webhooks to manage 816+ DocTypes.

Connects an MCP client such as Claude to an ERPNext/Frappe site, signing in as one of your users so the assistant can read, build, debug and fix customizations like DocTypes, scripts, workflows, permissions, reports and print formats under that user's roles. Every change waits for an approved plan, and semantic memory plus a knowledge index let the assistant recall sandbox rules and your company's own context.

A governed MCP server for ERPNext that provides AI agents with access to 51 doctypes and 265 tools through a PLAN-CONSENT-EXECUTE-PROVE workflow, deny-by-default.

Enables MCP clients to securely read, write, and maintain Frappe/ERPNext sites with role-based permissions, audit logging, and dry-run safeguards.

MCP server that enables Claude, ChatGPT, and other LLMs to interact with ERPNext sites through natural language, supporting document CRUD, search, reports, workflows, and custom tools, while respecting user permissions and logging all calls.

Enables AI agents to explore and operate Frappe Framework, ERPNext, and HRMS sites at runtime by discovering installed apps, permission-visible DocTypes, schemas, records, child tables, reports, workflows, workspaces, print formats, files, and translations through the authenticated Frappe session. It also supports guarded create, update, delete, submit, cancel, and workflow actions alongside standard DocType, Custom Field, Property Setter, Client Script, permission, and app-customization export operations, each gated by preview and explicit confirmation.