MCP Integration Status

Verified: September 6, 2026

Public MCP installation is not available
The Ranch.Bot MCP npm package and MCP Registry listing are not published, and Ranch.Bot does not run a hosted MCP endpoint. Publication is approved only after the release gate below. Previous package instructions do not work and have been removed.

The public CLI is available separately. Follow CLI Setup for browser OAuth login and shell-capable assistant use. CLI publication does not publish MCP.

What this means for customers

The Ranch.Bot MCP server cannot currently be added to Claude Desktop, Claude Code, ChatGPT, Gemini, Codex, Cursor, OpenCode, Pi, or another MCP client through a public MCP package.

This does not affect the current product. Use the SMS-first setup and the web dashboard without an external assistant or API key.

What exists in source

The mcp-server/ package contains a local implementation over Ranch.Bot's structured farm-data API. This is an advanced developer surface, not a customer onboarding path. The MCP package README is the current tool-surface source of truth.

External MCP writes do not use the Ranch.Bot app's review screen. They call the ordinary farm CRUD endpoints and do not create the Action rows that back Change History today. If this integration is published later, farm scope, revocation, audit behavior, and the lack of in-app review must be verified and stated plainly.

Local development only

Contributors with an authorized source checkout can build the server against a development Ranch.Bot environment:

cd mcp-server
npm install
npm run build
npm test

A local MCP client must run the built entry directly:

node /absolute/path/to/mcp-server/dist/index.js

Set RANCHBOT_API_URL to the development API and set COGNITO_DEVICE_CLIENT_ID to that environment's public OAuth device client. Do not rely on the production default embedded in the current source. Do not put API keys or OAuth tokens in committed configuration.

Public release gate

Public setup instructions return only after all of these are true:

The package is published and read back from npm.
The MCP Registry listing is published and read back.
MCP installation, OAuth sign-in, least-privilege farm scoping, representative read/write tools, external-write safety disclosure, revocation, and upgrade pass from a clean machine.
This page, /connect-your-ai, llms.txt, package READMEs, registry metadata, and well-known files are updated together.

Until then, do not use copied Ranch.Bot install commands from an older page or search result.

Need the livestock record product?

Follow Getting Started for Text-in and web review. For integration questions, email support@ranch.bot.

HTTP developer reference

Browse the developer reference, current access guidance, and integration walkthroughs. API access remains directed developer use; these documents do not change public CLI or MCP installation availability.