
plantcv-mcp
io.github.musharnaPublished by GitHub account musharnav1.19.2Updated Nov 3, 2026
Plant phenotyping via PlantCV — returns traits plus the segmentation overlay they came from
Overview
Runs PlantCV plant phenotyping locally, returning trait numbers together with the segmentation overlay they were measured from.
- What you can do
- Suggest segmentation settings and preview what each channel and object type would yield
- Segment images into masks, returning overlays, diagnostics and warnings without traits, and refine nearly-right masks
- Measure traits from a segmented session, across batches of images, per plant in a tray, or for leaf and stem morphology
- Count leaves by watershed or optionally with Segment Anything
- Calibrate scale from a marker, correct lens distortion, and crop or zoom images
- Segment and measure hyperspectral and thermal imagery
- When to use it
- Useful when an assistant needs quantitative plant measurements from images — leaf area, morphology, counts, spectral or thermal statistics — and you want the mask shown alongside the numbers so bad segmentations are caught rather than trusted.
- Requirements
- Runs locally over stdio as a Python package (pip install plantcv-mcp, or uvx with Python 3.13; Python 3.11 to 3.13 required). The optional Segment Anything tool needs the sam extra. No authentication or environment variables are declared; the --root flag or PLANTCV_MCP_ROOTS confines file access.
Installation
In SourceWeft
- Open plantcv-mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
plantcv-mcp
plantcv-mcp is an MCP server that lets AI agents run PlantCV plant phenotyping. It returns trait numbers and the segmentation overlay they were measured from, and refuses to return numbers when the segmentation is degenerate.
[CI] [PyPI] [Python] [License] [DOI] [Glama]
[Correct segmentation: four views of a rendered plant, stems and leaves tinted red and outlined in cyan, the gray background untouched] [Inverted segmentation: the whole gray background tinted red, the four plant views left out]
Left, channel="a", object_type="dark": the mask covers 3.1% of the frame, 9 components,
area=32427. Right, channel="s", object_type="dark": the mask covers 96.1%; it is the
background, area=1007829.
Why you get the overlay
Both images come from the same file and the same threshold method; only the channel differs. Without the picture, both runs return 17 traits with correct units and believable magnitudes. The one on the right is measuring the wall behind the plants. Red marks the measured pixels; a cyan line traces the mask's edge.
So segment() returns the overlay and diagnostics but no traits, and measure() needs the
session_id that segment() mints: no single image is measured before you are shown it. The
exception is measure_images(), which applies one recipe to up to 200 images without overlays.
Settle the recipe on one image's overlay first (the server does not check); every image still
passes the segment() guards, and one that trips a blocking guard gets no traits.
Measured with PlantCV 4.11.3 on a synthetic render (first row:
tests/fixtures/multi_specimen.png) and on photographs, each of these returns believable
numbers with correct units:
Install
With uv nothing needs installing: uvx --python 3.13 plantcv-mcp fetches and
runs the current release. Otherwise:
Requires Python 3.11 to 3.13: PlantCV 4.11.3 needs SciPy below 1.16, which has no Python 3.14
wheels, so --python 3.13 keeps uvx off a 3.14 default. PlantCV and its scientific stack make the first install (or first uvx
run) slow. From a checkout: uv add /path/to/plantcv-mcp. The one optional tool,
segment_leaves_sam(), needs pip install "plantcv-mcp[sam]" (torch, torchvision,
segment-anything); without it, that tool refuses with that command and every other tool works.
Configure your MCP client
Claude Desktop and other stdio hosts:
With a pip install the command is plantcv-mcp (checkout config).
Verify with list_methods().
Flags: --root DIR (repeatable, or PLANTCV_MCP_ROOTS) confines every read, and every file
the server keeps, to your imagery: plantcv-mcp --root /data/phenotyping. --no-isolate (or
PLANTCV_MCP_ISOLATE=0) runs analyses in-process instead of in the crash-containing worker.
What the benchmark shows
Claude with the server was compared with Claude writing its own code (mostly OpenCV) in a Python environment we set up with the same PlantCV and OpenCV, on 46 measurement questions about rendered plant images, 3 runs each. A tie means the server matches that result without you building the environment. Questions right in every run, server against Claude's own code: Claude Haiku 5.5 38 against 32, Sonnet 5.5 33 against 28, Opus 5.5 42 against 44. None is separated (pre-registered; exact McNemar p = 0.15, 0.23 and 0.63), and Claude's own code was cheaper on all three models.
The chart is the Opus 5.5 re-run on 2026-10-18, against an unreleased commit (051aff0) that adds
several-channel segmentation rules and zoom_image: right on 97.1% of answers with its own code
and 95.7% with the server. Its own code cost $0.038 against $0.066 per answer (medians; the
intervals do not overlap). On release 1.16.1 the server was right on 86.2% against 95.7%
(p = 0.18). The images have crisp edges, so a single color cut with no model answers 28 of the
46.
We wrote the questions and ran the benchmark ourselves; an outside re-run is welcome. Method, controls and limitations: benchmarks/agent_qa; the Haiku and Sonnet runs: 2026-10-20 re-run.
Tools
Typical loop: suggest_segmentation → segment → look at the overlay → segment again
with another channel, method or polarity if it is wrong (or refine if it is nearly right) →
measure. With a ColorChecker in the frame, color_correct=true corrects colors before
segmenting and excludes the card from the mask. Parameters, an example response and the
measured facts behind each tool:
docs/GUIDE.md.
What it refuses
Each guard was added after a specific failure and names the next action. Blocking guards withhold numbers; advisories travel with them.
- Inverted mask (
implausible_coverage): the right-hand image above, 17 believable traits describing the wall. - Nothing selected, or
fill_sizedeleted the specimen (empty_mask,fill_erased_mask): PlantCV returns 17 zeros within_bounds=True. - Background texture (
noisy_segmentation): specks of chamber wall measured as one plant. - Several plants in one mask (
multi_specimen): usemeasure_regions(). - Wrong scale, wrong session kind, a file changed after segmentation: refused, naming the right tool.
- A lens calibration the boards do not determine, or no color card when one was asked for: refused.
Why each guard exists, and every warning code: docs/GUIDE.md#warnings-and-refusals.
Security
With no --root, the server reads any image file the host user can read and returns it to the
model. It writes only the lens-corrected image, the Segment Anything checkpoint when asked to
download it, and short-lived temporary copies of hyperspectral and thermal inputs. Run it as a
non-root user with --root set. Analyses run in a worker subprocess, so a native crash is a
tool error, not a dead server. Details:
docs/GUIDE.md#security-and-trust-boundary.
Attribution and license
MIT licensed. It depends on PlantCV, which is licensed under the Mozilla Public License 2.0. No PlantCV source is vendored or redistributed here; it is an ordinary runtime dependency, so the MIT license applies to this project's own files. Unofficial: not affiliated with, endorsed by, or sponsored by the Donald Danforth Plant Science Center or the PlantCV maintainers. See NOTICE.
Cite it with CITATION.cff (archived at doi:10.5281/zenodo.21713516). Changes: CHANGELOG.md.
Source: README.md at commit d6b2e59
Tools
0Version history
12- v1.19.2LatestNov 3, 2026
- v1.18.3Nov 1, 2026
- v1.18.2Nov 1, 2026
- v1.18.1Oct 31, 2026
- v1.18.0Oct 29, 2026
- v1.17.1Oct 20, 2026
- v1.17.0Oct 20, 2026
- v1.16.1Sep 26, 2026
- v1.16.0Sep 23, 2026
- v1.15.0Sep 19, 2026
- v1.14.0Sep 19, 2026
- v1.13.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts