Skip to main content
Glama
Sign In
frappe-api-mcp

frappe-api-mcp

by danielsebastianc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

frappe-api-mcp

Model Context Protocol (MCP) server that exposes a single frappe_api tool to call Frappe REST endpoints under /api.

What it provides

  • Tool name: frappe_api

  • Methods: GET, POST, PUT, PATCH, DELETE

  • Input: path (required), method, query, body, headers

  • Auth: uses FRAPPE_AUTH_TOKEN as the Authorization header unless overridden

Related MCP server: ERPNext MCP Server

Requirements

  • Node.js 18+

  • A reachable Frappe/ERPNext site

Local setup

git clone https://github.com/danielsebastianc/frappe-api-mcp.git
cd frappe-api-mcp
npm install
cp .env.example .env

Set these environment variables before running:

  • FRAPPE_BASE_URL (example: http://localhost:8000)

  • FRAPPE_AUTH_TOKEN (example: token api_key:api_secret)

Run

npm start

Test

npm test

OpenCode MCP config example

Do not put real secrets in committed config files. Prefer environment injection.

{
  "mcp": {
    "frappe_api": {
      "type": "local",
      "command": ["node", "/path/to/your/folder/mcp/frappe-api-server.mjs"],
      "environment": {
        "FRAPPE_BASE_URL": "http://localhost:8000",
        "FRAPPE_AUTH_TOKEN": "token api_key:api_secret"
      }
    }
  }
}

Available Tools

1 tool
frappe_apiC

Call any Frappe REST API endpoint via /api using configured token authentication.

Inputs: path (required), method, query, body, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • 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
      17
      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

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