Skip to main content
Glama
jagmohan0908

ERPNext MCP Server

by jagmohan0908
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ERPNext MCP Server

No user-submitted related servers found.

    Related Servers

    • ERPNext MCP Server

      rizkyurdhan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with ERPNext data and functionality through the Model Context Protocol, including document CRUD, report running, and API method calls.
      MIT

    • Frappe MCP Server

      Codenetic-tech
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to securely interact with Frappe Framework/ERPNext instances, supporting document CRUD, RPC methods, file management, workflows, reporting, and more via the Model Context Protocol.
      164 npm
      ISC

    • ERPNext MCP Server

      Ravana-indus
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates with ERPNext/Frappe API to enable AI assistants to interact with ERPNext data and create custom applications including DocTypes, workflows, scripts, and more.
      MIT

    • paperware_mcp

      sadikhossainnub
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to directly interact with ERPNext/Frappe business data and operations, including document management, submissions, cancellations, reports, PDF generation, file uploads, and whitelisted method calls, with per-request permission enforcement.
      MIT

    • Frappe MCP Server

      kiran-harbak
      A
      license
      Not graded
      quality
      D
      maintenance
      Allows AI assistants to interact with Frappe applications through the official REST API, enabling document CRUD operations, schema handling, and detailed API instructions.
      164 npm
      2
      ISC
    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.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: listing doctypes, fetching fields, retrieving documents, creating, updating, and running reports. There is no overlap between these operations.

    Naming Consistency4/5

    All tools use a verb_noun pattern (get_, create_, update_, run_), but pluralization is inconsistent: get_doctypes and get_documents are plural, while get_doctype_fields, create_document, and update_document use singular forms.

    Tool Count5/5

    With 6 tools, the server is well-scoped and covers core ERPNext interactions without unnecessary bloat. Each tool has a clear purpose.

    Completeness3/5

    The set covers create, read (list), and update, but lacks a delete_document operation. Also, get_documents only implies listing, with no explicit get by ID, which may require workarounds. Reports add some breadth.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources