Frappe Dev MCP Server
NPM · FRAPPE-DEV-MCP-SERVER · SCANNED SEP 25
MCP server for Frappe/ERPNext development with AI assistance for DocTypes, bench commands, and APIs
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 16 of 53 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 321 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1431 tokens (~49/item across 29 items; 29 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "frappe_run_bench_command" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Frappe Dev MCP Server server?
Frappe Dev MCP Server runs locally as an npm package, launched with npx -y frappe-dev-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · frappe-dev-mcp-server
claude mcp add sajmustafake-frappe-dev-mcp-server -- npx -y frappe-dev-mcp-server
{
"mcpServers": {
"sajmustafake-frappe-dev-mcp-server": {
"command": "npx",
"args": [
"-y",
"frappe-dev-mcp-server"
]
}
}
} {
"servers": {
"sajmustafake-frappe-dev-mcp-server": {
"command": "npx",
"args": [
"-y",
"frappe-dev-mcp-server"
]
}
}
} codex mcp add sajmustafake-frappe-dev-mcp-server -- npx -y frappe-dev-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sajmustafake-frappe-dev-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"frappe-dev-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add sajmustafake-frappe-dev-mcp-server --command npx --arg -y --arg frappe-dev-mcp-server
mcp_servers:
sajmustafake-frappe-dev-mcp-server:
command: "npx"
args: ["-y", "frappe-dev-mcp-server"] {
"McpServers": {
"sajmustafake-frappe-dev-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"frappe-dev-mcp-server"
]
}
}
} assistant mcp add sajmustafake-frappe-dev-mcp-server -t stdio -c npx -a -y frappe-dev-mcp-server
{
"mcpServers": {
"sajmustafake-frappe-dev-mcp-server": {
"command": "npx",
"args": [
"-y",
"frappe-dev-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −2
- Stability: pass → 0.83 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/frappe-dev-mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 53 packages
| Packages resolved | 53 |
|---|---|
| Deprecated | 1 |
| Stale | 15 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
frappe_call_method ~56
Execute a whitelisted Frappe method
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments for the method |
| method | string | yes | Method path (e.g., 'frappe.client.get') |
| site | string | – | Site name |
No output schema declared.
No examples provided.
frappe_create_api_endpoint ~70
Create a custom API endpoint for a Frappe app
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the Frappe app |
| code | string | yes | Python code for the API endpoint |
| endpoint_name | string | yes | Name of the API endpoint |
| method | string | – | – |
No output schema declared.
No examples provided.
frappe_create_app ~59
Create a new Frappe app
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the new app |
| description | string | – | App description |
| publisher | string | yes | Publisher name |
| title | string | yes | Title of the app |
No output schema declared.
No examples provided.
frappe_create_doctype ~95
Create a new Frappe DocType with JSON definition and Python controller
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the Frappe app |
| doctype_name | string | yes | Name of the DocType |
| fields | array | yes | Array of field definitions |
| is_child | boolean | – | – |
| is_submittable | boolean | – | – |
| module | string | yes | Module where DocType belongs |
No output schema declared.
No examples provided.
frappe_create_document ~52
Create a new Frappe document
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Document data as key-value pairs |
| doctype | string | yes | DocType of the document |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_create_ui_block ~57
Create UI blocks using frappe-ui and Tailwind CSS patterns
| Name | Type | Req | Description |
|---|---|---|---|
| block_type | string | yes | Type of UI block to create |
| customization | string | – | Specific customization requirements |
| theme | string | – | Theme for the block |
No output schema declared.
No examples provided.
frappe_delete_document ~49
Delete a Frappe document
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | DocType of the document |
| name | string | yes | Name of the document |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_generate_frappe_ui_component ~66
Generate a Vue component using frappe-ui components
| Name | Type | Req | Description |
|---|---|---|---|
| component_name | string | yes | Name of the component |
| component_type | string | yes | Type of frappe-ui component |
| content | string | – | Component content/template |
| props | object | – | Component props |
No output schema declared.
No examples provided.
frappe_generate_vue_page ~52
Generate a Vue page with frappe-ui layout
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | – | List of components to include |
| page_name | string | yes | Name of the page |
| route | string | yes | Route path |
No output schema declared.
No examples provided.
frappe_get_app_structure ~35
Get the structure of a Frappe app
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the Frappe app |
No output schema declared.
No examples provided.
frappe_get_doctype_list ~29
List all available DocTypes in the system
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_get_doctype_schema ~47
Get the complete schema/structure of a Frappe DocType
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | Name of the DocType |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_get_document ~54
Retrieve a Frappe document by DocType and name
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | DocType of the document |
| name | string | yes | Name of the document |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_get_field_options ~52
Get options for Link/Select fields in a DocType
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | DocType name |
| fieldname | string | yes | Field name |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_get_financial_statements ~66
Get financial statements (P&L, Balance Sheet, Cash Flow)
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name |
| fiscal_year | string | – | Fiscal year |
| site | string | yes | Site name |
| statement_type | string | yes | Type of financial statement |
No output schema declared.
No examples provided.
frappe_get_frappe_usage_info ~34
Get combined schema and usage information for Frappe development
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_get_report_meta ~40
Get metadata for a Frappe report
| Name | Type | Req | Description |
|---|---|---|---|
| report_name | string | yes | Name of the report |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_get_ui_templates ~26
Get available UI templates and patterns
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Template category |
No output schema declared.
No examples provided.
frappe_get_vue_component_tree ~30
Get the Vue component tree structure (simulated)
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | Page name |
No output schema declared.
No examples provided.
frappe_inspire_ui_block ~44
Generate creative UI blocks inspired by modern design patterns
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Target framework |
| inspiration | string | yes | Description of the inspiration or use case |
No output schema declared.
No examples provided.
frappe_install_app ~42
Install a Frappe app on a site
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | Name of the app to install |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_list_documents ~62
List Frappe documents with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | DocType to list |
| filters | object | – | Filters as key-value pairs |
| limit | number | – | Maximum number of results |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_list_reports ~25
List available Frappe reports
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_migrate_database ~30
Run database migration for Frappe apps
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | Site name to migrate |
No output schema declared.
No examples provided.
frappe_refine_ui_block ~44
Refine and improve existing UI blocks
| Name | Type | Req | Description |
|---|---|---|---|
| existing_code | string | yes | Existing UI block code to refine |
| improvements | string | yes | What improvements to make |
No output schema declared.
No examples provided.
frappe_run_bench_command ~53
Execute bench commands for Frappe development
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Bench command to execute |
| cwd | string | – | Working directory (optional) |
| site | string | – | Site name (optional) |
No output schema declared.
No examples provided.
frappe_run_doctype_report ~53
Generate a report based on a DocType
| Name | Type | Req | Description |
|---|---|---|---|
| doctype | string | yes | DocType for the report |
| filters | object | – | Filters for the report |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_run_query_report ~49
Execute a Frappe query report
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Report filters |
| report_name | string | yes | Name of the query report |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
frappe_update_document ~60
Update an existing Frappe document
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Updated document data |
| doctype | string | yes | DocType of the document |
| name | string | yes | Name of the document |
| site | string | yes | Site name |
No output schema declared.
No examples provided.
What is the Frappe Dev MCP Server server?
Frappe Dev MCP Server is listed in the public MCP registry as io.github.SajmustafaKe/frappe-dev-mcp-server. MCP server for Frappe/ERPNext development with AI assistance for DocTypes, bench commands, and APIs. This page covers its npm package (frappe-dev-mcp-server).
Is the Frappe Dev MCP Server server safe to use?
Frappe Dev MCP Server scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Frappe Dev MCP Server server expose?
Frappe Dev MCP Server exposes 29 tools: frappe_create_doctype, frappe_run_bench_command, frappe_get_app_structure, frappe_create_api_endpoint, frappe_migrate_database, and 24 more. Their descriptions and schemas cost roughly 1,431 tokens of context every time the server is loaded.
Is the Frappe Dev MCP Server server still maintained?
Frappe Dev MCP Server is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Frappe Dev MCP Server server under?
Frappe Dev MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.