MCP server for Agro GPS, the digital field notebook.
Free, no key: search and check plant protection products (pesticides, fungicides, herbicides) in the official registers of 30 European countries, mirrored by Agro GPS: is it still authorised, which substances, which uses, is it allowed on this crop.
With your key: your farms, field notebook, group dashboard, advisor queue and farm finances and, with a write key, recording new notebook entries.
{
"mcpServers": {
"agro-gps": {
"command": "npx",
"args": ["-y", "agro-gps-mcp"]
}
}
}That is enough for the public tools. For your own farm data, create a key in the app at agrogps.eu/app (Settings → API and webhooks) and add it:
"env": { "AGROGPS_API_KEY": "agk_your_key_here" }Variable | Required | Default |
| only for farm tools | — |
| no |
|
| no |
|
Related MCP server: agriculture-mcp-server
Tool | What it does |
| Search a country's official register by trade name; authorisation state and a link to each product page |
| One product by registration number: state, expiry, substances, authorised uses and, with |
Examples: "Is Roundup Ultra Plus still authorised in Spain?", "Can I use product 7400057 on grapevine in France?". Public endpoints are rate limited per IP address.
The key acts as you: it only sees the farms and groups you belong to, with your role in each. A read key only
queries; a write key can also use record_entry. Revoke it from the same screen at any time. Without a key these
tools are still listed and answer with instructions to create one.
Tool | What it does | Access |
| Farms the key can see, role, plan and whether holder data is complete | read |
| Notebook entries of a farm with compliance fields, paginated | read |
| Audit trail of one entry, field by field | read |
| Groups (company or cooperative) the key owner belongs to | read |
| Consolidated panel of a group per farm and crop | read |
| Farms an advisor reviews, with a traffic light | read |
| Entries of a farm pending review or missing fields | read |
| Costs, income and margins of a farm or group per campaign | read |
| Budget vs actual per line | read |
| Estimated campaign close per crop (low / mid / high) | read |
| Receivables and payables | read |
| Cash-flow forecast by week or month | read |
| Imported bank movements and match candidates | read |
| Adds a new entry to the notebook | write |
record_entry only adds entries: nothing in this server edits or deletes existing data. Every entry is attributed
to the key owner and marked as written through the API in the audit trail. Official submission to the
administration never happens here: it needs a person's session in the app.
Servidor MCP del cuaderno de campo Agro GPS. Sin clave, consulta los registros oficiales
de fitosanitarios de 30 países: si un producto sigue autorizado, sus sustancias, sus usos y si vale para un
cultivo. Con clave (créala en agrogps.eu/app, Ajustes → API y webhooks), el
asistente consulta tus explotaciones, cuaderno, grupos, cola del asesor y cuentas; con write además registra
labores nuevas. La clave ve solo tus explotaciones y nunca borra ni edita nada. El envío oficial a la
administración no pasa por aquí.
npm ci
npm run lint && npm test && npm run build
node build/index.jsnpm run pages regenerates src/data/product-pages.ts (which products have a page on agrogps.eu) from the
landing repo checked out at ../landing.
MIT
Entries of a farm that still need review or lack mandatory fields, with the list of missing fields.
Inputs: farm_id (required).
For advisors and owners: every farm they can review, with entries, missing compliance fields, pending, flagged and approved counts and a traffic light.
Inputs: no named parameters.
Imported bank accounts with their last balance and movements, what each one was matched to and, for the unmatched ones, the best candidates with a score.
Inputs: farm_id, group_id, only_open.
Budget lines (campaign x farm x crop x category) with actual spend, remaining, used percentage and status ok / warning (90%+) / over. Amounts in euro cents.
Inputs: farm_id, campaign, group_id.
ESTIMATE of how the campaign closes per crop: expected yield x price minus costs already imputed and the budget still pending, as a low / mid / high range, total and per hectare. Says whether each assumption was saved by the farm, taken from last campaign or is missing. Always present it as an estimate.
Inputs: farm_id (required), campaign.
Expected cash in and out by week or month from open receivables and payables, starting from the last imported bank balance, with overdue amounts apart.
Inputs: farm_id, horizon, group_id, granularity.
Free, no API key. Looks up one product by its official registration number in a country's register: authorisation state (authorised / withdrawn / expired), expiry date, formulation, active substances and authorised uses. With crop_eppo it also says whether the product is authorised on that crop. Includes a link to the product page.
Inputs: country (required), registration (required), crop_eppo.
Who created, edited or deleted a notebook entry and when, field by field (audit trail).
Inputs: entry_id (required).
Money of a farm or a whole group for one campaign: month-by-month cost and income, cost by category (phyto, fertiliser, fuel, labour, machinery, seed, insurance, other), cost per hour per worker and per machine, margin per hectare per parcel and per crop, per-farm totals and KPIs of the last three campaigns. Amounts are integer euro cents.
Inputs: crop, farm_id, campaign, group_id.
Consolidated panel of a group: per farm, entries, cost, income, margin, treated hectares, compliance light (green/amber/red), pending review counts and a breakdown by crop; plus totals.
Inputs: group_id (required).
Field notebook entries (labores) of a farm: treatments, fertilising, irrigation, sowing, harvest, expenses… with the compliance fields (Anexo II). Paginated: pass since = the next cursor of the previous page. Deleted entries come back with deleted=true so a mirror can stay in sync.
Inputs: farm_id (required), since.
Farms (explotaciones) the API key can see, with the key owner's role in each, the plan and whether the holder data required for official submissions is complete. Call this first to get farm ids.
Inputs: no named parameters.
Groups (a company or cooperative holding several farms) the key owner belongs to, with their role.
Inputs: no named parameters.
Register a task in the farm's field notebook (needs a key with write scope). The entry is attributed to the key owner and marked as written by API in the audit trail; the server stores when it arrived and rejects future dates. It only adds new entries: it never edits or deletes existing ones. Confirm the farm, parcel, product and date with the user before calling it. Official submission to the administration is never done here: it needs a person's session in the app.
Inputs: title (required), farm_id (required), event_at (required), entry_type (required), +9 more.
Free, no API key. Searches the official register of plant protection products (pesticides, fungicides, herbicides) of a European country by commercial product name and says whether each one is still authorised. Returns up to 15 matches with registration number, holder, status and a link to its page. Search by trade name (e.g. 'Roundup'), not by active substance.
Inputs: q (required), country (required).
Money to collect (receivable) and to pay (payable) with issue date, due date, paid date, status (open / overdue / paid) and days overdue, plus totals.
Inputs: status, farm_id, group_id, direction.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 16 tools
Most tools have clearly distinct purposes: field notebook operations, product lookups, farm/group listing, compliance review, and several financial views. There is some overlap between group_overview, advisor_portfolio, and finance_dashboard in reporting metrics, but descriptions scope them differently enough for an agent to choose correctly.
All names use consistent snake_case and are descriptive, which makes the set readable. The main deviation is that some tools use verb_noun (list_farms, record_entry) while others use noun_noun (finance_dashboard, budget_variance), but the pattern is still predictable.
16 tools is slightly above the ideal 3-15 range, but the server covers multiple domains: field entries, compliance, groups/advisors, product registers, and finance. Each tool appears to earn its place, so the count is reasonable rather than excessive.
The surface covers core read and reporting workflows plus entry creation, audit history, compliance review, product lookups, and extensive financial views. Minor gaps exist, such as no update/delete for entries and no active-substance product search, but these appear intentional or workable around.
Crop-protection products, active ingredients, approved uses and registrations per country.
Read satellite, NDVI, weather and soil data; create and delete fields in Agro API.
Weather, climate, soil, terrain, fire and flood risk data for any point or polygon. Free tier.
Farm management for Brazilian farms: pest scouting, rainfall, work orders, inventory, fleet, post-harvest and cost per field. Reads and records, with OAuth on the user's own upCampo account. Nothing is ever deleted.
