Public MCP Server for Agricultural AI Agents
What is the SeedMatch Group MCP server and how does an AI agent connect?
SeedMatch Group publishes a public, read-only Model Context Protocol server at https://seedmatchgroup.com/api/public/mcp. Any MCP client — ChatGPT, Claude, Gemini or a custom agent — can connect over Streamable HTTP with no sign-in and call 13 tools: buyer-answer search, project guides, procurement checklists, and the greenhouse, water demand, irrigation zoning, pump duty and fertigation planners, plus a dry-run RFQ preview. Nothing is stored, no supplier is contacted, and every figure is a budget-level planning estimate.
- Endpoint: https://seedmatchgroup.com/api/public/mcp
- Transport: MCP Streamable HTTP · Auth: none (read-only)
- REST companions: https://seedmatchgroup.com/api/public/.mcp/
- Signed-in buyer workspace: https://seedmatchgroup.com/mcp
How to connect
- Claude / Claude Desktop — Settings → Connectors → Add custom connector → paste the endpoint URL. No authentication.
- ChatGPT — Settings → Connectors → Add MCP server → paste the endpoint URL, transport: Streamable HTTP.
- Gemini / other agents — Register the endpoint as a Streamable HTTP MCP server, or call the REST companions under /api/public/.mcp/ directly.
Machine-readable descriptor: /mcp-server.json · tool directory /tools.json · site guidance /llms.txt.
The 13 public tools
| Tool | Purpose | Inputs | Returns |
|---|---|---|---|
| list_seedmatch_tools | Start here: every public capability with purpose, inputs, units, limits and next step, plus the project planning chain. | None | Tool list and the crop → area → climate → water → zones → flow → pump → fertigation → RFQ chain |
| search_buyer_answers | Match a plain-language agricultural question against the published buyer answer blocks. | Question text | Direct answer, the inputs that change it, the stated limitation, the next tool and the implied RFQ track |
| list_buyer_answers | Browse the published answer blocks by project group. | Optional group id | Answer ids, questions and groups |
| get_buyer_answer | Return a single published answer block by id. | Answer id | Question, answer, inputs, limitation and next step |
| list_project_guides | List the published planning guides for greenhouse, irrigation, fertigation and integrated projects. | None | Guide ids and titles |
| get_project_guide | Return the full published guide content for one project area. | Guide id | Guide sections |
| get_procurement_checklist | Return the data and documents a supplier needs before pricing a given package. | Checklist id | What to submit and which documents speed up pricing |
| estimate_greenhouse_project | Indicative CAPEX, water and energy envelope for a greenhouse project at concept stage. | Area, technology level, climate context, crop | Budget-level planning ranges — never a quotation |
| plan_water_demand | Screen peak and seasonal water demand for a cultivated area. | Area, crop, climate context | Indicative demand in m³ and peak day figures |
| plan_irrigation_zones | Screen how many irrigation zones an area and irrigation window imply. | Area, flow per hectare, irrigation window | Indicative zone count and design flow |
| screen_pump_duty | Screening duty point from flow and head components. Flow alone never selects a pump. | Design flow, static lift, friction and system head components | Screening duty point for supplier discussion |
| plan_fertigation_equipment | Equipment scope from a concentration the buyer's agronomist supplies. Never prescribes recipes, doses, EC or pH. | Design flow, injection ratio, tank and channel assumptions | Indicative injector, tank and channel scope |
| preview_rfq | Structure a requirement and list what is still missing. Contacts no supplier, sends nothing, stores nothing. | Project data collected so far | Structured RFQ preview and missing-field list |
What the server will and will not do
- Read-only and unauthenticated: nothing is stored and no supplier is contacted.
- All figures are budget-level planning estimates — never quotations, engineering designs or yield, saving, ROI or performance guarantees.
- Supplier identities are never disclosed; all communication runs through SeedMatch Group.
- Saving projects, RFQ items and checklists requires the buyer's signed-in workspace at /mcp.
