Industry solutionsPublic source

Agriculture MCP Server

Full-stack agriculture MCP server with 35 tools — farm management, weather intelligence, satellite imagery, commodity markets, IoT sensors, and yield forecasting. Includes a built-in example AgTech backend with…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides agriculture capabilities through a typed MCP contract.

Architecture

How Agriculture MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Agriculture MCP Server

Validates the request and owns 35 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask Agriculture MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

35 named tools

list_fields

List all farm fields/plots

read only

get_field

Get field details including area, location, soil type, and current crop

read only

create_field

internal write

update_field

Update field details

internal write

delete_field

Remove a field from the farm

internal write

list_crops

List crops planted across all fields

read only

get_crop

Get crop details including growth stage, planting date, and expected harvest

read only

plant_crop

Record a new crop planting on a field

internal write

get_crop_calendar

Get recommended planting/harvesting calendar for a crop in a region

read only

log_harvest

Record a harvest with yield data

internal write

log_activity

Log a farm activity (irrigation, fertilizer, spraying, weeding)

internal write

list_activities

List farm activities with optional field/date filter

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

29 read only6 internal write

The registry manifest declares read only, internal write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-agriculture

MCP client configuration

export AGTECH_API_URL=http://localhost:7800/api/v1

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Issues and support ↗github.com issues

Keep exploring

Agriculture MCP Server

A purpose-built capability behind one MCP connection.

How Agriculture MCP Server fits into an agent system.

ADK-Rust agent

MCP client

Agriculture MCP Server

Domain system

What can an agent ask Agriculture MCP Server to do?

Understand the effect of every tool.

What the current documentation declares.

Follow the project’s documented starting point.

Continue with the project maintainers’ source of truth.

More in industry solutions.