frappe-mcp-server

The server design generally follows good security practices for an MCP. It enforces API key/secret authentication, avoids hardcoded secrets in the main codebase, and uses a well-established Frappe SDK. Direct use of 'eval' or arbitrary code execution from user input is not present. However, the server exposes powerful tools like `call_method` (which can execute any whitelisted Frappe method), `create_doctype`, `update_blueprint`, and messaging tools. The security largely depends on: 1) The permissions granted to the Frappe API key used. 2) The security and whitelisting of methods in the underlying Frappe instance. 3) The control mechanisms of the integrating AI assistant to prevent misuse or unintended operations. Verbose error logging (including `responseData` from Frappe's API) could also expose internal Frappe details to the AI, which should be considered in a production environment.