Permite que un cliente de IA lea y escriba registros de ganado bovino y ovino a través de un MCP server local con acceso limitado al ámbito de la granja.
También conocido como RanchBot/mcp-server, @ranchbot/mcp-server
- Stars
- 1
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.2.0
- Último commit
- 20 oct 2026
- Licencia
- MIT
¿Qué es Ranch.Bot MCP?
Permite que un cliente de IA lea y escriba registros de ganado bovino y ovino a través de un MCP server local con acceso limitado al ámbito de la granja.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Ranch.Bot
Gestionar datos de ganado mediante un asistente de IA es posible con este MCP server local que se conecta a tu cuenta de Ranch.Bot. Diseñado para productores, el servidor permite que un cliente de IA lea y escriba registros de ganado bovino y ovino utilizando un transporte stdio. Funciona con un alcance basado en la granja, lo que significa que expone una sola granja a la vez al cliente conectado.
Para usar el servidor, necesitas Node.js 22 o superior y una cuenta de Ranch.Bot con acceso a la granja. La configuración implica instalar el paquete vía npm y usar el comando ranchbot-mcp login para autenticarte a través de un navegador, lo que elimina la necesidad de API keys manuales. Una vez configurado, un cliente de IA puede usar herramientas como list_animals y list_records para recuperar inventarios o gestionar historiales.
Escribir datos requiere roles y permisos específicos. Mientras que los Readers pueden realizar consultas, los Editors y Owners pueden crear actualizaciones o confirmar nacimientos. El servidor admite flujos de trabajo complejos, como el uso de preview_birth_event y confirm_birth_event para garantizar la precisión de los datos antes de confirmar los cambios en los registros de la granja.
Qué puedes hacer con él
- 1Resumir el inventario de la granjaPide a la IA que proporcione un resumen completo de la población animal actual en una granja específica.
- 2Conciliar registros de ganado dispersosUsa el asistente para comparar hojas de cálculo, notas y PDFs con los registros oficiales de la granja.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Ranch.Bot MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Ranch.Bot MCP en Claude Code
$ claude mcp add mcp-server -- npx -y @ranchbot/mcp-serverInstalar Ranch.Bot MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@ranchbot/mcp-server"
]
}
}
}Instalar Ranch.Bot MCP en VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ranchbot/mcp-server"
]
}
}
}Instalar Ranch.Bot MCP en VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@ranchbot/mcp-server"]}'Instalar Ranch.Bot MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@ranchbot/mcp-server"
]
}
}
}Instalar Ranch.Bot MCP en Codex
$ codex mcp add mcp-server -- npx -y @ranchbot/mcp-serverInstalar Ranch.Bot MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@ranchbot/mcp-server"]
Instalar Ranch.Bot MCP en Gemini CLI
$ gemini mcp add -s user mcp-server npx -- -y @ranchbot/mcp-serverInstalar Ranch.Bot MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@ranchbot/mcp-server"
]
}
}
}Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleranchbot/mcp-server is public and reachablegithub.com/ranchbot/mcp-server ↗Aprobado
- El paquete indica este repositorio como su origen@ranchbot/mcp-server names ranchbot/mcp-server as sourcenpmjs.com/package/@ranchbot/mcp-server ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for @ranchbot/mcp-servernpmjs.com/package/@ranchbot/mcp-server/v/0.2.0#provenance ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-20github.com/ranchbot/mcp-server ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @ranchbot/mcp-serverAprobado
- No hay avisos críticos en el paquete ni en sus dependencias119 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubRanch.Bot MCP Server
Read and write cattle and sheep records through a local MCP server on your own computer. It uses your Ranch.Bot account over the stdio transport and exposes one farm at a time. Hosted connections are not public yet. ChatGPT access is a private pilot. Ranch.Bot’s Claude connector is in review; you can still connect it privately as a custom connector.
Requirements: Node.js 22 or newer, a Ranch.Bot account, and access to a farm.
Install and sign in
These commands install this source package's version (0.2.0). For the recommended public release, use the pinned command on MCP setup, the source of truth for setup; release status and promotion rules live in MAINTAINING.md. Stop older CLI and MCP processes before upgrading; never remove their active lock files.
npm install -g @ranchbot/mcp-server@0.2.0
ranchbot-mcp --version
ranchbot-mcp login
Open the printed URL, sign in, and explicitly approve the displayed code and requested access in
your browser. No API key is needed. If login expires, run ranchbot-mcp login again; sign out with
ranchbot-mcp logout. See
Troubleshooting for
access-denied and session problems, and keep passwords and token files out of assistant messages.
Configure a local stdio client
Point an MCP client at the installed command with no arguments:
{
"mcpServers": {
"ranchbot": { "command": "ranchbot-mcp", "args": [] }
}
}
If the client cannot find the command, use its absolute executable path. Restart the client after
changing configuration. ranchbot-mcp --help and ranchbot-mcp --version work without
authentication. Any MCP client that can run a local stdio server works; this is not a certification
of any named client.
First successful read
Ask the client to call these tools in order:
list_my_farmswith{}. Choose the intended farm ID. If more than one farm is plausible and the producer did not name one, ask instead of guessing.list_animalswith{"farm_id":"<farm_id>"}, replacing the placeholder with that ID.
An empty list is a successful read. Pass farm_id explicitly on every scoped call; setting a
default with set_default_farm is optional. If access is denied, check the account and farm
membership; missing authentication means terminal login, then retry. Tool calls never start browser
approval. A different account clears the process's default farm.
list_animals accepts query, match_mode (exact default, or partial) and
identifier_type; exact matches saved identifiers and the current profile name, partial is literal
substring discovery over profile names and NAME/MANAGEMENT_TAG identifiers. list_records
accepts animal_id, group_id, include_group_context and explicit inclusive/exclusive
applied_from/applied_before RFC3339 bounds; the first three and the bounds activate bounded
history mode. Scoped credentials need the matching extra read scope for a target filter.
A useful read-only task: "Summarize the selected farm's current inventory." Read the complete
relevant population, follow each operation's pagination (skip/take) and returned total, and
report incomplete retrieval rather than presenting a first page as the whole answer.
Writing farm data
Ordinary writes save directly under your server permissions, without the app confirmation screen or its Change History. Before any mutation, present the operation, farm, resolved targets, exact values, and consequences and get explicit approval. Read the result back afterwards. If the outcome is uncertain, reconcile with reads before proposing another write.
Roles and scopes both apply: Readers can read, including the safe lookup_animal_by_eid; Editors or
Owners can create and update and confirm a birth; deleting animals, groups, records, or identifiers
needs Owner access. Birth confirmation also needs the write:records, write:animals, and
write:groups scopes. A missing scope and a missing role are separate problems.
Direct births use preview_birth_event → approval → confirm_birth_event. Saved amendments and
entered-in-error use preview_workflow with operation: "amend_birth", the record revision and a
reason, then exact approval and commit_workflow, when exposed by the connected release. Never
re-record a birth as a correction; if capability is missing, stop and contact
support. Read the
birth events reference before handling births.
Farms can configure a versioned record_birth template that drives the shared
preview_workflow → approval → commit_workflow flow. The list_workflow_templates,
get_workflow_template, create_workflow_template, publish_workflow_template_version,
update_workflow_template_state, and set_default_workflow_template tools manage that
configuration (Owner writes with write:farms). After upgrading from a login that lacks
write:farms, run ranchbot-mcp login and approve a fresh authorization. Refresh preserves the
existing grant; it cannot add scopes. A new grant does not elevate your farm role.
Commit requires the exact preview_hash read back from a fresh
preview; a stale hash is rejected. Templates change
labels, visibility, defaults, and custom observations only — the meaning and review controls of
core birth fields do not change. See the workflow guide for the run and
configuration steps.
Agent skill
The package ships the public Agent Skill bundle at skills/ranchbot (SKILL.md plus
references/). It is optional guidance, not a capability or a security boundary; installation
details are in the MCP reference.
Task references
- MCP reference — connection, tool discovery, farm context, errors, and optional skill installation.
- Birth events reference — preview, confirmation, retry, saved amendments, and capability limits.
- Exports reference — archive create, poll, cancel, and download.
- Mixed-source reconciliation — historical imports, coverage ledgers, and lender-document caveats.
Jobs for an external assistant
A producer can authorize a local assistant to reconcile years of lambing spreadsheets, iPhone notes, messages, and livestock PDFs against one farm, produce custom reports, or compare farm history with an authorized lender or AgriStability snapshot for the same population and date. Totals are aggregate evidence, not individual animals or proof of current group membership; this is livestock reconciliation, not financial advice. Follow the mixed-source reconciliation recipe and the workflow pagination rules; MCP does not persist the coverage ledger.
Package guides
- Workflows — find an animal, save an ordinary record, and preview and confirm a birth, with inputs, pagination, and recovery.
- Architecture — the request path and which component enforces each guarantee.
- Troubleshooting — login, farm selection, lock, and access problems.
- Development — credential-free checks, the authenticated development server, and packaging.
- Contributing — how changes reach this exported repository and where to send feedback.
- Security — how to report a vulnerability privately.
Maintainer instructions
See MAINTAINING.md for development, admin login, local installations, EID migration, authentication troubleshooting, and detailed credential-lock recovery. For shell commands, use CLI setup. For everyday record entry, use SMS and web setup. Support: support@ranch.bot.
License
MIT. See LICENSE.
Preguntas sobre Ranch.Bot MCP
¿Cómo agrego Ranch.Bot MCP a Claude Code?
Ejecuta claude mcp add mcp-server -- npx -y @ranchbot/mcp-server en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Ranch.Bot MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Cómo inicio sesión en el MCP server de Ranch.Bot?
Ejecuta el comando ranchbot-mcp login, abre la URL impresa en tu navegador y aprueba el acceso solicitado.
¿Necesito una API key para usar este servidor?
No, no se requiere una API key para la autenticación.
¿Cuáles son los requisitos del sistema para la instalación?
Necesitas Node.js versión 22 o superior, una cuenta de Ranch.Bot y acceso a una granja.
¿Puedo usar esto con ChatGPT?
El acceso a ChatGPT es actualmente un piloto privado.