Use an AI assistant with your livestock records

What a connected assistant can do

Example prompts for working with saved records.

1. Example 1

   Retrieve an animal’s recorded history

   Ask for the dated records saved against an animal or one of its identifiers, and have the assistant show what it found and what is missing.

   “Show the saved records for tag 327, with the event date and record type for each.”

2. Example 2

   Record feeding against the correct group

   Let the assistant propose a feeding record for a named group, then check the farm, group, event date, and values before it writes.

   “Record that we fed the ewe lambs one oat-straw bale today.”

3. Example 3

   Summarize saved records with sources and gaps

   Ask for a summary of recorded history in a period. Have the assistant separate saved records from missing or unknown dates.

   “Summarize the group’s saved feed records this month and mark dates with nothing recorded.”

Connection options and what you need

Public availability is the Ranch.Bot CLI and the local stdio MCP package. ChatGPT hosted access is a private pilot. Ranch.Bot’s Claude connector is in review and not public yet. You can still connect it privately in your own Claude account as a custom connector. Only sign-in and record reads have been checked. Gemini has no publicly available connection.

Before you start

• A Ranch.Bot account with access to the farm you want to use.
• For public local setup, Node.js 22 or newer on the machine that runs the CLI or local MCP package.
• For Claude, a plan that allows custom connectors. Not every Claude plan or app can add one.
• Farm roles and OAuth scopes that allow the reads or writes you ask for. Readers cannot write.
• Any separate account, subscription, or connection requirements your outside assistant imposes.

Assistant compatibility

Compatibility is evaluated for each assistant, environment, and connection method. The labels are Available, Limited access, Not yet verified, and Unavailable. A released local package is not certification of a named assistant client.

Ranch.Bot CLILocal shell (any shell-capable assistant)

Available

Published 1.2.3. The assistant runs commands after you sign in.

Local stdio MCPAny stdio-capable local client

Available

Published 0.2.0. Package and stdio transport verified; a named client is not.

ChatGPTHosted MCP

Limited access

Private read-only pilot checks passed on 2026-10-10; write-scoped acceptance remains pending and there is no public listing to connect from.

ClaudeHosted MCP or local stdio

Limited access

Hosted: add Ranch.Bot yourself as a custom connector. Sign-in and record reads were checked on 2026-10-14; writes were not. Claude Desktop has not been tested.

CursorLocal MCP or CLI

Not yet verified

Cursor's local MCP configuration has not been tested against the package.

ReplitLocal MCP or CLI

Not yet verified

The intended environment and its runtime and credential limits are unassessed.

Grok BotUnresolved

Not yet verified

The exact official product and environment are not yet confirmed.

MuseUnresolved

Not yet verified

The vendor and product behind this name are unresolved.

Set up the public CLI

The commands below read saved farm data from your farm. Follow the steps in order.

1. 01

   Install the CLI

   Use Node.js 22 or newer and an account with access to a Ranch.Bot farm.

   npm install -g @ranchbot/cli@1.2.3

2. 02

   Sign in through your browser

   Open the URL printed by login, sign in, and approve the displayed code. No API key is needed.

   ranchbot login

3. 03

   Select your farm and read animals

   Check your identity, list farms, then replace <farm_id> with the farm you want to use.

   ranchbot whoami --json
   ranchbot farms list --json
   ranchbot farms use <farm_id>
   ranchbot animals list --json

Prefer no technical setup? The SMS and web setup guide covers everyday records without an outside assistant.

Which assistant is doing the work

Your connected assistant uses Ranch.Bot’s tools to read and change saved farm records. It is not the same as chatting with Ranch.Bot’s built-in assistant. The Ranch.Bot app and SMS workflow show proposed writes for review before saving. Ordinary CLI and MCP writes run directly under your account permissions, without the app review screen or its Change History.

• An outside assistant decides how to use the exposed CLI, local MCP, and hosted connector tools. Connecting it does not run Ranch.Bot’s built-in assistant workflow or inherit all of its capabilities.
• Reviewing proposed values in the outside conversation is not a server-enforced app approval gate.
• Check the farm, target, event date, and values before you authorize a write, and read the saved record back afterwards.
• Clarify ambiguous identifiers and dates. After an uncertain write outcome, check before retrying. Do not blindly replay.
• Assistant memory or a chat answer is not evidence that farm records were saved.

Common questions

More setup help

For everyday records, follow the SMS and web setup guide. For assistant instructions, read the public agent skill. For HTTP integrations, browse the developer reference.