Skip to main content
Glama
rakeshgangwar

erpnext-server

by rakeshgangwar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to erpnext-server

No user-submitted related servers found.

    Related Servers

    • MCP ERPNext

      sharat9703
      A
      license
      Not graded
      quality
      B
      maintenance
      Model Context Protocol (MCP) server for ERPNext - manage timesheets, leave applications, projects, and software releases via Claude, Gemini, or any MCP-compatible AI assistant.
      10 npm
      MIT

    • erpnext-mcp

      o-M7MD
      F
      license
      Not graded
      quality
      B
      maintenance
      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.
      -

    • 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.
      312
      AGPL 3.0

    • 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

    • FastMCP Demo

      gogouravr
      F
      license
      B
      quality
      D
      maintenance
      A demonstration TypeScript MCP server that showcases basic MCP concepts with simple tools (greeting, calculator), text resources, and prompt templates for learning the Model Context Protocol.
      2
      -
    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 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: creating documents, retrieving document lists, updating documents, getting metadata about DocTypes and their fields, and running reports. The descriptions clearly differentiate between document operations, metadata queries, and report execution.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as create_document, get_documents, and update_document. This predictability makes it easy for agents to understand and select the appropriate tool based on naming conventions.

    Tool Count5/5

    With 6 tools, this server is well-scoped for ERPNext operations, covering core CRUD actions (create, get, update), metadata retrieval (doctypes and fields), and reporting. Each tool earns its place without being overwhelming or insufficient for the domain.

    Completeness4/5

    The tool set provides strong coverage for document lifecycle (create, get, update) and metadata, with a report execution tool. A minor gap exists in the lack of a delete_document tool, which agents might need to work around, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources