agriculture-mcp-server
Related Servers
Alternatives to agriculture-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Open-Meteo free weather APIs, offering 16 tools for forecast, historical, air quality, marine, flood, ensemble, climate, seasonal, and scheduled data collection with no API key required.68 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for global weather, forecasts, air quality, and climate data using Open-Meteo, no API key required.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides real-time weather data, hourly forecasts, and daily summaries using the free Open-Meteo API with no API key required. It enables users to search for weather conditions by specific coordinates or city names across multiple measurement units.2MIT
- AlicenseAqualityDmaintenanceMCP server for Open Food Facts, enabling food product lookup by barcode, search, nutrition facts, allergen checks, and eco-scores without an API key.8MIT
- AlicenseNot gradedqualityBmaintenanceEU Crop Intelligence MCP Server — Yield forecasts, weather analysis, and phenology models for 15 countries. AI agent-native, multi-source intelligence (NASA POWER, Eurostat, Open-Meteo).MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server provides access to Open-Meteo weather APIs including forecast, historical reanalysis, geocoding, air quality, marine weather, and flood risk data, enabling AI agents to retrieve weather information using natural language.7 npmMIT
TDQS
Scored across 8 tools
Tools are generally well-differentiated by domain (climate vs. soil vs. country stats vs. food). The pair `climate_averages` and `climate_history` could cause slight confusion as both retrieve historical NASA POWER climate data for a location, though they are distinguished by monthly averages versus specific date ranges. Food tools are clearly separated by barcode lookup versus text search.
Most tools follow a consistent noun_phrase pattern (e.g., `climate_averages`, `soil_conditions`, `country_agriculture_profile`). However, `compare_countries` uses a verb_noun structure, creating a minor deviation from the otherwise consistent convention. All use snake_case consistently.
Eight tools is an appropriate count for this scope, covering field-level environmental data (climate averages, history, forecasts, soil), macro-level country agricultural statistics (profile and comparison), and food product databases (search and lookup) without redundancy or bloat.
The toolset provides comprehensive read-only coverage across distinct agricultural data domains: temporal climate data (past averages, historical range, forecasts), soil conditions, country-level indicators, and food product information. No obvious CRUD gaps exist for a data-retrieval server, though it lacks analytical tools that might combine these datasets (e.g., crop suitability scoring).