Schema | Frappe MCP Server

Frappe MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`FRAPPE_URL`	Yes	Base URL of your Frappe site (e.g. https://erp.example.com)
`FRAPPE_API_KEY`	Yes	Frappe API key
`FRAPPE_TIMEOUT`	No	Request timeout in seconds (default: 30)	30
`FRAPPE_API_SECRET`	Yes	Frappe API secret
`FRAPPE_VERIFY_SSL`	No	Set to false to skip TLS verification (default: true)	true

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
frappe_pingA	Check connectivity to the configured Frappe/ERPNext site.
frappe_get_docB	Retrieve a single document (doctype record) by its doctype and document name.
frappe_search_docsB	Search or list documents of a given DocType with optional filters, field selection, pagination, and ordering.
frappe_create_docC	Create a new document of the given DocType with the provided field values.
frappe_update_docB	Update an existing document identified by doctype and name with the provided field values.
frappe_delete_docB	Delete a document by its doctype and name.
frappe_run_methodB	Call a whitelisted server-side Python method on the Frappe site (e.g. 'frappe.auth.get_logged_user').

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/muthanii/frappe_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server