mcpField
F

Frappe Inspector

Local
frappeinspector.xyzDeveloper Tools
Visit website

About Frappe Inspector

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "belius303-frappe-inspector": {
      "command": "npx",
      "args": [
        "-y",
        "@frappe-inspector/mcp"
      ],
      "env": {
        "FRAPPE_INSPECTOR_LICENSE_KEY": "<FRAPPE_INSPECTOR_LICENSE_KEY>"
      }
    }
  }
}
Run commandnpx -y @frappe-inspector/mcp
Environment variables to set
FRAPPE_INSPECTOR_LICENSE_KEYSecretOptional Universal Pro license key for advanced Frappe Inspector capabilities.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@frappe-inspector/mcp1.4.0

Tools

12

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
pathstringNoAbsolute or relative project path.
refreshbooleanNoIgnore the in-process snapshot cache.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.