Agmarknet MCP Server
This server provides access to Indian agricultural commodity wholesale price data from Agmarknet, enabling you to query and analyze mandi (regulated market) prices across India.
Get commodity prices (
get_commodity_price): Retrieve daily wholesale min, max, and modal prices for a specific commodity, optionally filtered by state, district, or market.Compare markets (
compare_markets): Compare prices of a commodity across different mandis, ranked cheapest-first by modal price, optionally filtered by state and limited to a top N results.Get price summary (
get_price_summary): Get a statistical summary (average, lowest, and highest prices) for a commodity across all matching markets, optionally filtered by state.List commodities (
list_commodities): Browse all available commodities in the dataset, with an optional search term to narrow results.List markets (
list_markets): Browse all available mandis (regulated markets) reporting data, optionally filtered by state and/or commodity.
Note: The
mainbranch serves today's data only and includes a built-in sample dataset usable without an API key. Thefeat/ceda-api-migrationbranch offers an additionalget_price_trendtool and historical data back to 2000.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Agmarknet MCP ServerWhere is the cheapest place to buy onions in Maharashtra?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agmarknet MCP Server
A Model Context Protocol (MCP) server that gives LLMs (like Claude) access to Indian agricultural commodity prices — daily wholesale min/max/modal rates across thousands of mandis (regulated markets) and hundreds of commodities.
Ask a model "Where were tomatoes cheapest in Pune last month?" and it answers from real market data.
Pick your implementation
The project lives on two branches with different data sources. They expose the same kind of tools; choose by your data needs.
|
| |
Data source | data.gov.in Agmarknet | CEDA Agri Market API (Ashoka University) |
API key |
|
|
Without a key | Serves a small sample dataset so the tools work out of the box — for flavour only, not live prices | Will not run — a key is required |
To use real data | Add the key to | Add the key to |
Data coverage | Current day only (when the live API is reachable) | Historical, 2000–present (lags ~a few months) |
Price trends | ✗ | ✅ |
Reliability | data.gov.in is frequently down / WAF-blocked | Stable |
Tools | 5 | 6 |
Best for | Trying the tools instantly on sample data | Real analysis — trends and accurate prices |
TL;DR: Want to see the server work with no live API? Use
main(it ships with sample data). Want real, reliable commodity data and trends? Usefeat/ceda-api-migration.
Switch with git checkout main or git checkout feat/ceda-api-migration.
Related MCP server: Agricultural AI MCP Server
Setup
Install (same for both branches)
git clone https://github.com/Krishna-Baldwa/agmarket-mcp.git
cd agmarknet-mcp
git checkout feat/ceda-api-migration # or: git checkout main
python -m venv .venv
source .venv/bin/activate
pip install -e .Configure the API key
cp .env.example .envOn feat/ceda-api-migration (CEDA):
Get a free key from the CEDA Data Portal.
Set
CEDA_API_KEY=<your key>in.env. Done — the server uses real data.
On main (data.gov.in):
Out of the box it serves a small sample dataset (no key needed) so you can see the tools respond.
To switch to real data.gov.in data:
Get a free key at data.gov.in and set
DATA_GOV_IN_API_KEY=<your key>in.env.In
src/agmarknet_mcp/server.py, change the client to live mode:api_client = AgmarknetClient(use_mock=False) # was use_mock=True
Connect to Claude Desktop
Add this to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; The easiest way to get to it is from inside the app rather than hunting through folders: open Claude Desktop → Settings → Developer tab → click Edit Config. That opens the file directly (and creates it if it doesn't exist yet).), using the env var for your branch:
{
"mcpServers": {
"agmarknet": {
"command": "/absolute/path/to/agmarknet-mcp/.venv/bin/python",
"args": ["-m", "agmarknet_mcp.server"],
"env": {
"CEDA_API_KEY": "your_api_key_here"
}
}
}
}(On main, use "DATA_GOV_IN_API_KEY" instead — or omit env to run on sample data.)
Restart Claude Desktop and ask:
"Compare tomato prices across mandis in Pune district."
"What's the 60-day onion price trend in Maharashtra?" (CEDA branch)
Test without an LLM
npx @modelcontextprotocol/inspector python -m agmarknet_mcp.serverTools
feat/ceda-api-migration (CEDA — real historical data)
Tool | What it does |
| Min/max/modal prices — latest available date, or a specific |
| Rank a district's mandis cheapest-first. |
| Average / cheapest / dearest on the latest date. |
| Daily-average price, window average, high/low, and % change over N days. |
| List tracked commodities, optionally filtered. |
| List the mandis reporting a commodity in a district. |
Tools accept names, not numeric ids (see Design). state is required; district narrows to individual mandis (omit for a state-wide aggregate).
main (data.gov.in + sample fallback)
Tool | What it does |
| Daily min/max/modal price for a commodity. |
| Rank markets cheapest-first. |
| Average / cheapest / dearest across markets. |
| List commodities in the current dataset. |
| List reporting mandis. |
Design (CEDA branch)
The CEDA API is id-based: commodities, states, districts, and markets are all numeric ids, and /prices returns ids, not names. LLMs and humans think in names, so the server's core job is translation:
Name → ID resolution. Tools accept
"Tomato","Maharashtra","Pune"; the client resolves them to ids (case-insensitive, unique-substring matching) before calling the API, and raises a clear error for unknown/ambiguous names so the model can self-correct.ID → name enrichment. Raw price rows (which carry only
market_id) are translated back into readable records before reaching the model.Cached reference data. Commodities, geographies, and markets are fetched once and reused.
Tolerant validation.
pydanticvalidates every response. The API changes shape by granularity (state-level queries omitdistrict_id/market_id), which the models handle explicitly.
Module layout
server.py— FastMCP server: defines the tools and handles the stdio/JSON-RPC lifecycle.api.py— the API client (CedaClienton CEDA;AgmarknetClientwith sample fallback onmain).models.py—pydanticmodels for the API's raw shapes and the domain objects the tools return.
Data sources
main: Directorate of Marketing & Inspection (DMI), Govt. of India, via data.gov.in.CEDA branch: CEDA Agri Market Data, "Centre for Economic Data & Analysis, Ashoka University" — built on the same Agmarknet data, 2000–present. Free to download, display or include the data in other products for non-commercial purposes.
License
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Krishna-Baldwa/agmarket-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server