Skip to main content
Glama
Kai-Oesterling

ERPNext MCP Server

by Kai-Oesterling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ERPNext MCP Server

No user-submitted related servers found.

    Related Servers

    • ERPNext MCP Server

      Sheikh-Muhammad-Mujtaba
      A
      license
      Not graded
      quality
      C
      maintenance
      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.
      MIT

    • ERPNext MCP Tools

      Arui-world
      A
      license
      Not graded
      quality
      B
      maintenance
      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.
      MIT

    • ERPNext MCP Server

      ManotLuijiu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ERPNext management, file operations, read-only database access, and ERPNext API integration through a standardized MCP server.
      4
      MIT

    • Frappe Assistant Core

      OsamaASidd
      A
      license
      Not graded
      quality
      C
      maintenance
      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.
      AGPL 3.0

    • Frappe Assistant Core

      buildswithpaul
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables LLMs to interact with ERPNext/Frappe sites for document CRUD, search, reports, workflows, and analytics, respecting user permissions and logging all actions.
      308
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation3/5

    Most tools are distinct, but get_doctype_fields and get_doctype_meta overlap in scope, and add_doctype_field vs create_custom_field can confuse agents about which to use. Descriptions help but boundaries are not always clear.

    Naming Consistency4/5

    Tool names generally follow a verb_noun pattern (get_document, create_document, submit_document), but there are minor inconsistencies such as singular vs plural (get_document vs get_documents) and mixed resource naming (create_custom_field vs add_doctype_field).

    Tool Count4/5

    At 19 tools, the count is slightly above the ideal 3-15 range but still reasonable for an ERP system covering documents, Doctypes, workflows, and reports. The breadth justifies the number without feeling bloated.

    Completeness4/5

    The toolset covers document CRUD, lifecycle actions (submit/cancel), DocType management, customization, workflows, and report execution. Minor gaps exist such as no delete workflow or update custom field, but core workflows are well supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources