Skip to main content
Glama
danielsebastianc

frappe-api-mcp

by danielsebastianc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to frappe-api-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      320 npm
      2
      ISC

    • 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
      2
      MIT

    • Frappe MCP Server

      appliedrelevance
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Frappe Framework sites through comprehensive document operations, schema introspection, report generation, and method execution. Provides secure API-based access to create, read, update, and delete Frappe documents while supporting financial reporting and DocType management.
      24
      16
      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
    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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clearly defined purpose of calling any Frappe REST API endpoint, leaving no room for confusion or misselection.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'frappe_api' follows a clear and appropriate pattern that matches the server's purpose, with no other tools to compare against or create inconsistency.

    Tool Count2/5

    A single tool is too few for a server with the broad scope implied by 'frappe-api-mcp', which suggests a comprehensive API interface. While the tool is flexible, the lack of specialized tools for common operations (e.g., CRUD on specific resources) makes the surface feel thin and underdeveloped for the domain.

    Completeness2/5

    The tool set is severely incomplete for the apparent domain of Frappe API interactions. With only a generic 'call any endpoint' tool, there are significant gaps in coverage—no dedicated tools for common operations like creating, reading, updating, or deleting specific resources, which will likely cause agent failures due to lack of structured guidance.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources