MCP Tools Directory
← Browse integrations

Developer tools

bot.ranch/mcp-server

Free account · sign-in required

Contact bot.ranch/mcp-server

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

Read and write cattle and sheep records with farm-scoped, revocable access.

Transport
stdio
Authentication
oauth
Initial setup
user-authorization
Runtime
unattended
Evidence
documented
Version
0.1.0
Package
@ranchbot/mcp-server
Last compatibility test
Not independently tested

Connect your agent

@ranchbot/mcp-server

Publisher README and package manifest were reviewed from hash-pinned captures. No OAuth flow, farm access, read, write, revocation, or public package availability check was executed in this worker.

Capabilities: Manage farm-scoped animals, groups, and records, Preview and confirm atomic birth events, List and update farm tasks, Read farm memory and retained source evidence, Manage immutable farm protocol versions

Connected profiles

Additional details

Registry identifier

bot.ranch/mcp-server

Source ↗ · Checked 2026-09-17
Published version

0.1.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

@ranchbot/mcp-server

Source ↗ · Checked 2026-09-19
Source manifest version

0.1.0

Source ↗ · Checked 2026-09-19
Unattended configuration

Publisher documentation says the local MCP client launches ranchbot-mcp with no arguments after a separate login step.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

The stdio server uses OAuth device flow, requires explicit browser approval, caches refreshable tokens locally, and documents logout and revocation behavior.

Source ↗ · Checked 2026-09-19
Connection configuration

The public client is a local stdio executable with no arguments; development can instead launch the built Node entry point with an explicit API URL and public client ID.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19