servers / divisi
Divisi MCP server
communitystreamable_httpremotedestructive capablehealthy
Farm advice for Africa: what to plant, when, what ails a crop, and prices for your place.
01Tools · 45
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| add_task Add a task to a farm, due on `due_date` (within a year back or two
years ahead), optionally for one crop or batch (`unit`, a name or id).
It shows with the farm's other tasks in the app. Only owners and
managers can add one. Pass the same `client_id` to retry safely. | write | true | unknown |
| add_unit Add something the person grows or keeps, the way the app does, and
Divisi schedules its tasks. `what` is in their words: a crop ("maize"),
or animals ("broilers", "layers", "road runners", "goats", "tilapia",
"bees"); `kind` is worked out from it unless given.
A crop goes on a field: `target_planting_date` is the day they mean to
plant, `planting_date` only if it is already in the ground.
Animals: `count` (needed for poultry), `start_date` (the day they
arrived; today if left out) and optionally `ready_date`, the day they
expect to sell, which is added as a task.
`place` is the field, coop, pen, pond or apiary, by name or id; a new
name makes one. Left out, the farm's only place of that kind is used.
Only farm owners and managers can add one. Pass the same `client_id` (a
UUID) to retry safely. | write | true | unknown |
| add_zone Add a field, pen, pond or apiary to a farm. A name already used gets a
number added. Only farm owners and managers can add one. Pass the same
`client_id` (a UUID) to retry safely. | write | true | unknown |
| apply_to_programme Ask to join a programme as the person. This puts the organisation's
request on their list; nothing is shared until they read it and say yes
in Divisi, at the link in the reply. It never says yes for them. Pass
the same `client_id` to retry. | read | false | unknown |
| ask_agronomist Ask Divisi's agronomists, experts and other farmers by posting the
question in Community as the person. It is public and free; answers come
as replies in the app. `background` is what is known so far (crop stage,
what was tried); the post says it was written with an AI assistant.
Photos only as `{type, id}` refs already on Divisi. Pass the same
`client_id` (a UUID) to retry safely. | unknown | unknown | unknown |
| book_consultation Ask a verified expert for a call (`virtual`) or a farm visit
(`in_person`, to one of the person's farms) at the time proposed, at the
expert's own price. `topic` is what it is about, in the person's words.
Nothing is paid now: once the expert agrees a time, the person pays in
Divisi at the link in the reply. Confirm the expert, the time and the
price with the person first. Pass the same `client_id` to retry. | write | true | unknown |
| cancel_consultation Call off a consultation before it starts, either side. A paid booking
is refunded to the farmer in full. | destructive | true | true |
| cancel_rsvp Give up the person's place at an event, so the next person waiting
gets it. | destructive | true | true |
| consultation_step Take the next step on a consultation, as the person: `propose` another
time (with `starts_at`), `accept` or `decline` the time the other side
proposed, report a `problem` or that the expert was `late` (the farmer,
after the time), `contest` a lateness report or say the farmer did not
come (`no_show`) (the expert), or `reschedule` once after missing it
(the farmer, with `starts_at`). Paying, and saying it went well, are done
in the app. | unknown | unknown | unknown |
| create_listing Put something on the Market as the person, from what they said in
one sentence ("40 broilers ready on the 12th, Harare"): produce for sale
(`kind` SALE) or something they want to buy (WANTED, with a
`quantity`). `item` and `unit` are plain words ("tomatoes", "20 L
bucket"). Left out, a sale takes the unit most local prices use and the
usual local `price` (in major units, such as 12.50), and the place's
currency; say that price to the person. `ready_on` (YYYY-MM-DD, up to 90
days ahead) lists it now as a pre-order. It needs a place: a town, one
of their farms or a lat/lng; with none, their only farm. A sale needs a
photo already on Divisi (`media` as `{type, id}` refs); without one the
reply is the link to the screen where they add it, signed in on the web
or in the app. Reuse `client_id` (a UUID) to retry. Nothing is
charged. | write | true | unknown |
| express_interest Tell Divisi the person needs a service where they farm, so they are
told when it arrives there. `need`: inputs (seed and fertiliser), finance
(a farm loan), insurance (cover), tractor, transport (to market),
agronomist (an expert visit), soil_test, vet, storage, events (field
days), labour (farm hands) or control (stopping a pest or disease, named
in `pest_or_disease`). `detail` narrows it when asked: inputs seed or
fertiliser; finance inputs, equipment or cash; insurance crop, animals
or family; labour planting or harvest. `crop` names the crop for seed,
fertiliser, loans, crop cover and field days. `remind_on` asks for a
reminder that day instead. The place is their farm's area. This is
demand, not an application: nothing is shared and nothing is paid.
Asking twice keeps one request; pass the same `client_id` to retry. | unknown | unknown | unknown |
| farm_money Money in, money out and what is left, worked out: per crop or batch,
for costs of the whole farm, and in total, with the totals by heading
the app's income statement shows and the latest records. `unit` (a name
or id) reads one crop or batch; `since`/`until` limit the days. Leave
out `farm_id` to read every farm. | read | false | unknown |
| farm_report How the person's farms are doing and what needs them. Per farm: the
weather now, the days ahead and any warning; every crop, flock, herd,
pond and hive with its stage, head count and the day it is ready; money
in and out per unit with the margin worked out; tasks (late ones first);
the latest work with who logged it. Then what waits on the person:
unread conversations and who they are with, offers and deals to act on,
and events they are going to. Leave out `farm_id` to read every farm (up
to five). | read | false | unknown |
| find_crops Crops that suit a place, best first, with when to plant each. Give a
town or district name ("Murewa", "Nakuru") or a lat/lng. The list is in
Divisi's agronomy order: planting window, then suitability. Each crop links to its guide and its planting page, and lists the services the person can ask Divisi for about it (seed, cover, a loan). | read | false | unknown |
| find_events Upcoming field days, trainings and meetups, soonest first: near a town,
district or lat/lng (within `radius_km`, at most 200), or online.
`search` matches a topic or title. Pages of 20. | read | false | unknown |
| find_experts Verified agronomists, vets and advisers on Divisi, best first: who
they are, what they know, where they are, whether they visit farms near
the place, and what a call or a farm visit costs. `crop` keeps those who
know it; give a town or district, or a lat/lng (a signed-in person's own
farm by default). `name` matches their name. Pages of 10. | read | false | unknown |
| find_market Where a market is and when it runs. Give a market's `name` ("Mbare
Musika", "Mile 12", "Wakulima"; spelling and the word market do not
matter) or a town, district or lat/lng to see the markets near it, nearest
first. `crop` keeps only markets that trade it. Each market has its town,
country, how far away it is, the days and hours it runs, what is traded,
what is in season this month, and its Divisi page. It gives no
prices. | read | false | unknown |
| find_programmes Outgrower schemes and other farmer programmes taking farmers this
season where the person farms (their farm by default, or a town,
district or lat/lng): who runs each, what it offers, the season, what
joining asks them to share, and what it costs them. `crop` keeps those
for that crop. | read | false | unknown |
| identify_problem Which pests or diseases might explain what a farmer sees on a crop:
candidates from that crop's Divisi guide, best match first, each with how
to identify it, photos and a link to its page. `symptoms` is the
farmer's own words ("holes in the leaves, sawdust in the funnel"). These
are possibilities to check against the photos, not a diagnosis. | unknown | unknown | unknown |
| inbox The person's message conversations, newest first, each with who it is with,
how many messages are unread and the last message. `search` matches a
person, group or message text. Pages of 30. Reading marks nothing as
read. | read | false | unknown |
| log_work Write work done, money in or out, or both, into the farm records,
in the person's words. `unit` names the crop or batch it was for (its
name or id); leave it out for the whole farm. `day` defaults to today.
Work: `what`, and optionally `operation` (PLANTING, WEEDING,
FERTILISING, SPRAYING, IRRIGATION, SCOUTING, HARVEST, POST_HARVEST,
LAND_PREP, FEEDING or OTHER).
Money: `amount` with `money` ("income" or "expense"); `category` in
their words or a code (feed, day-old chicks, vaccine, labour, transport,
bird sale, crop sale…), worked out when left out; `currency` defaults to
the farm's; `quantity` is how many were bought or sold (birds sold this
way leave the flock count).
Pass the same `client_id` (a UUID) to retry safely. | read | false | unknown |
| make_offer Offer to buy from (or sell to) a listing as the person: `quantity` of
its unit at `price_per_unit` in major units. A buyer chooses how to pay:
`divisi` (the default where Divisi can take the payment: they pay before
meeting and the money is held until they have the goods) or `cash` when
they meet. The reply says which it is. The other person answers in
Divisi. Reuse `client_id` to retry. | unknown | unknown | unknown |
| manage_listing Keep one of the person's listings up to date: `renew` keeps it on the
Market (with `quantity_available`, how many are left now), `sold` takes
it down as sold out, `hide` takes it off the Market for now and `show`
puts a hidden one back. Reuse `client_id` to retry. | read | false | unknown |
| market_prices The typical price range Divisi has seen for a product near a place,
per `unit` ("kg", "50 kg bag", "crate"), from listings, deals and
published market prices, with how many prices it rests on. Without a
`unit`, it answers in the unit most prices near there were given in. Give
a town or district name, or a lat/lng. `currency` defaults to the
country's. When
there are too few prices to be honest, it says so instead of guessing. | unknown | unknown | unknown |
| my_consultations The person's consultations, booked or booked with them, newest first,
each with its next step. `open_only` false includes finished ones. | unknown | unknown | unknown |
| my_deals The person's Market deals that are still going, as buyer and seller,
most recently changed first (`include_finished` adds closed ones): what
was agreed, how it is paid (cash, or through Divisi), where the money is
(unpaid, held until the buyer has the goods, paid out, refunded, being
checked), where the handover code is, and the one thing to do next. Also
the offers waiting for the person's answer. | unknown | unknown | unknown |
| my_money The person's money in Divisi: what is theirs to spend or withdraw,
what is coming from sales (held until each buyer has the goods, with the
day it is paid out), money on its way to their bank or phone, anything
they owe, their Credit and when it runs out, refunds coming back to
them, and the fee. `currency` (e.g. USD) keeps only that one. Read
only. | read | false | unknown |
| my_requests The services the person has asked Divisi for and still wants, newest
first: waiting, reminders set, and what has reached their area (with
where to get it). `need` keeps one kind, such as tractor. | read | false | unknown |
| pay_deal What paying for one of the person's deals through Divisi takes, and
the page in Divisi where they pay it themselves: how much comes from
their Credit, how much by card (and in which currency the card is
charged), whether their balance covers it, and the fee. The assistant
never pays; give the person the link. Divisi holds the money until they
have the goods and gives it all back if the deal falls through. | write | true | unknown |
| read_guide The summary of Divisi's guide to one crop, pest or disease, named in
any language: for a crop, its overview, key facts, season stages and the
threats to watch for; for a pest or disease, how to spot it and what to
do. `kind` narrows the search when a name could be either. Links to the
full page. | read | false | unknown |
| read_thread The messages in one of the person's conversations, newest first, 30 a
page. Only conversations they are in can be read. | read | false | unknown |
| record_sale Write down a sale from one of the person's listings that happened
outside Divisi (at the gate, on WhatsApp): `quantity` of the listing's
unit at `price_per_unit`, on `sold_on` (YYYY-MM-DD, today if left out),
to `buyer` if they want a name. What is left on the listing goes down,
and the money goes into the farm's books. Reuse `client_id` to retry. | unknown | unknown | unknown |
| reply_to_review Answer a rating someone gave the person, once, in their own words.
It shows under the rating. | write | true | unknown |
| respond_to_offer Answer an offer the person received: `accept` (makes a deal),
`decline`, or `counter` with another `price_per_unit` (and `quantity`,
the same as asked if left out). `withdraw` takes back one they made. A
buyer accepting may choose `pay_with`; otherwise the offer's own choice
stands. The reply says how the deal is paid. Reuse `client_id` to
retry. | unknown | unknown | unknown |
| review_deal Rate the other person on a finished deal, 1 to 5 `stars`, with a
short `comment` if they want one. Others see it when they decide whether
to trade with them. Reuse `client_id` to retry. | unknown | unknown | unknown |
| rsvp Take a place at an event as the person. A full event puts them on its
waiting list. Retrying is safe: one place each. | read | false | unknown |
| search_market Find Market listings: produce and inputs for sale (`kind` SALE) or
what people want to buy (WANTED), near a town, district or lat/lng
(within `radius_km`, at most 100). Prices are per unit as listed, with
the usual local range beside them where Divisi has one, and each seller's
rating and orders handed over, so a buyer can judge the price and the
seller. Pages of 20. | read | false | unknown |
| sell_harvest Put a crop or a batch of animals from the person's farm up for sale,
as it nears harvest or slaughter. Divisi fills in what it knows: what it
is and its variety, the farm's place and currency, how many animals the
batch holds today, the day it is ready (listed ahead as a pre-order up
to 90 days early), the unit most local prices use, and the usual local
price when no `price` is given (say that price to the person). Give any
of them to change it. Without `production_unit_id`, their only crop or
batch; with several, the error lists them to choose from. A sale needs a
photo already on Divisi (`media` as `{type, id}` refs); without one the
reply is the link to the screen where they add it, signed in on the web
or in the app. Reuse `client_id` to retry. | unknown | unknown | unknown |
| send_message Send a text message as the person: into a conversation they are in
(`conversation_id`), or to a person (`to_person_id`), which opens or
reuses their direct conversation. A first message to someone who does not
follow them is a request the other person accepts first. Blocked people
cannot be messaged. Pass the same `client_id` (a UUID) to retry
safely. | write | true | unknown |
| set_up_farm Add a farm the person owns. Say where with `lat`/`lng` (best: advice
is then for that spot) or a town or district as `place` (its centre is
used until the spot is set in the app). Divisi fills in the country,
currency and time zone. Pass the same `client_id` (a UUID) to retry
safely. | write | true | unknown |
| update_deal Move one of the person's deals on. A seller: `handed_over` with the
4-digit `code` the buyer shows them (ask the seller for it; never guess),
`more_time` (once) to hand over a deal paid through Divisi. A buyer:
`problem` (`missing`, `wrong` or `damaged`; the money waits until Divisi
decides), `new_code` after too many wrong codes. Saying all is right pays
the seller, so the buyer does that themselves in Divisi, from the deal's
link. Either: `cancel` before handover (a buyer who paid gets it all
back), `no_show` when the other person did not come. No money is paid
here. Reuse `client_id` to retry. | write | true | unknown |
| update_farm Rename a farm, change its description, or move it (`lat`/`lng`, or a
`place`). Only what is passed changes. Only farm owners and managers can
change a farm. `farm_id` may be left out when the person has one farm. | write | true | unknown |
| update_task Look after a task: mark it done (`done`, with an optional `note` of
what was done and the `day`, today if left out), move it to another
`due_date`, or rename it (`title`). Only what is passed changes. Pass
the same `client_id` (a UUID) to retry safely. | write | true | unknown |
| when_to_plant When to plant one crop at one place: the planting window open now or
next, the other seasons in the year, when harvest falls, and the services
the person can ask Divisi for about it. `crop` is a
name in any language ("maize", "chibage"); give a town or district name,
or a lat/lng. | unknown | unknown | unknown |
| withdraw_interest Take a service request off the person's list: they no longer need it
and will not be told when it arrives. | read | false | unknown |
02Install & source
Hosted · connect by URL
https://divisi.africa/mcp
- homepagehttps://divisi.africa/mcp
03Access granted
Send chat messages · writeUpdate a CRM · writeManage tasks & tickets · write
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-11-20 20:04Z
next_check2026-11-22 11:23Z
cadenceevery 48h
verifiedtools_list:passed handshake:passed metadata:passed
index_statusindex — 5 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README.
[](https://mcpexplorer.com/servers/divisi)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →