Skip to main content
Glama
sppandita85

erpnext-fast-mcp-server

by sppandita85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to erpnext-fast-mcp-server

No user-submitted related servers found.

    Related Servers

    • ERPNext MCP Server

      yazelin
      A
      license
      B
      quality
      C
      maintenance
      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.
      28
      1
      MIT

    • 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

    • 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

    • ai_mcp

      renish-1111
      F
      license
      Not graded
      quality
      B
      maintenance
      Universal dynamic MCP server for Frappe & ERPNext v16, exposing 36 tools, resources, prompts, SSE transport, and real-time webhooks to manage 816+ DocTypes.
      -
    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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: CRUD operations (list, create, get, update, delete), metadata inspection, counting, and report execution. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: list_documents, create_document, get_document, update_document, delete_document, get_doctype_meta, get_count, run_report. The use of singular for single-document operations and plural for listing is a sensible convention.

    Tool Count5/5

    8 tools is well-scoped for a document management server. Each tool covers a necessary operation without redundancy or bloat, fitting comfortably within the ideal range.

    Completeness5/5

    The tool set provides full CRUD lifecycle coverage for any DocType, plus useful supplementary tools for metadata discovery, counting, and running reports. There are no critical gaps in the core document workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources