Read and write farm asset, log, and planting records on a farmOS instance using its JSON:API interface.
domain: farmos.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain API credentials for the target farmOS instance (self-hosted or hosted).
Fetch /api/schema to discover the available JSON:API resource types and their fields for that farmOS version.
Call GET /api/{entity_type}/{bundle} (e.g., asset/plant, log/harvest) to list or filter existing records.
POST a new resource under the appropriate entity/bundle path following the JSON:API document structure, referencing related entities by UUID.
PATCH existing records by UUID to update fields such as status or linked assets/logs.
Known gotchas
farmOS assigns UUIDs to all resources and expects UUID references (not sequential IDs) in relationships.
The JSON:API schema and available fields can differ between farmOS 1.x and 2.x, so confirm which major version the target instance runs before hardcoding paths.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?