Skip to main content
Glama

Related Servers

Alternatives to ERPNext MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      D
      maintenance
      Integrates with ERPNext/Frappe API to enable AI assistants to create, read, update, and list documents, run reports, and authenticate via the Model Context Protocol.
      6
      MIT
    • 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
    • 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
    • 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.
      379 npm
      2
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to interact with any ERPNext instance through comprehensive CRUD operations, advanced permissions, and a web chat interface.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: create_document and update_document handle document lifecycle operations, get_doctypes and get_doctype_fields provide metadata, get_documents retrieves document lists, and run_report executes reports. The descriptions reinforce these distinct roles, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as create_document, get_doctypes, and update_document. This predictability makes the tool set easy to navigate and understand, with no deviations in naming style.

    Tool Count5/5

    With 6 tools, the server is well-scoped for ERPNext operations, covering core document management, metadata access, and reporting. Each tool serves a specific function without redundancy, making the count appropriate for the domain's typical needs.

    Completeness4/5

    The tool set provides strong coverage for document CRUD (create, get, update) and metadata access, with run_report adding reporting functionality. A minor gap exists in document deletion, which could limit full lifecycle management, but agents can likely work around this omission.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues