Frappe Inspector

io.github.Belius303Published by GitHub account Belius303v1.4.0Updated Oct 24, 2026

Static analysis tools for Frappe Framework and ERPNext projects via local stdio MCP.

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.Belius303/frappe-inspector
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Belius303 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Belius303%2Ffrappe-inspector.svg)](https://sourceweft.com/mcp/io.github.Belius303%2Ffrappe-inspector?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local stdio MCP server that gives an assistant static analysis tools for Frappe Framework and ERPNext projects.

What you can do: Inspect Frappe Framework and ERPNext codebases through static analysis
Examine project structure and code without running the application
Support review and understanding of Frappe/ERPNext customizations
No individual tools are documented in the supplied listing, so exact capabilities are unclear
When to use it: Useful when working on or reviewing Frappe Framework or ERPNext projects and you want the assistant to analyze the codebase locally rather than through a hosted service.
Requirements: Runs as a local process over stdio, installed from the npm package @frappe-inspector/mcp, so Node.js and a local Frappe/ERPNext project are needed. Desktop client only. An optional license key can be supplied via FRAPPE_INSPECTOR_LICENSE_KEY for advanced capabilities.

Before you install

The optional FRAPPE_INSPECTOR_LICENSE_KEY is a secret and should be kept out of shared configuration. The listing does not describe whether the tools only read code or also modify files, so check before pointing it at an important repository.

Installation

In SourceWeft

Open Frappe Inspector in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.4.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.