Skip to main content
Use this page to understand what the remote Leaf MCP server exposes after you connect a client to https://mcp.withleaf.io/mcp. It is a tool reference, not a REST API reference, and it groups the available capabilities by product area.

Overview

The Leaf MCP (Model Context Protocol) server exposes tools that AI assistants can call to interact with the Leaf API programmatically. Instead of making REST calls directly, your MCP-compatible client (such as Cursor, Claude Desktop, or a custom agent) invokes typed tools and receives structured responses.
The MCP server is a tool server, not a REST API. There is no base URL — you configure the server in your MCP client, and it handles communication with the Leaf API on your behalf.

Configuration

To use the Leaf MCP server, point your MCP client at the remote Leaf server and pass your Leaf API token as a LEAF_TOKEN header. The server authenticates every tool call against the Leaf API using this token.
Use the remote HTTP server as the canonical setup. Older local npx-based examples are outdated.

Available tools

The server groups its tools into the categories listed below. Each tool accepts typed parameters and returns JSON matching the corresponding Leaf API response.

User management

Fields

Field operations

Machine files

Batch uploads

Weather

Weather tools accept optional model and units parameters. Time parameters use ISO 8601 format.

Billing

Provider credentials

Credential event tools are intended for troubleshooting. They expose authentication status and error details for provider connections.
Last modified on March 24, 2026