Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http soilgrids 'https://gateway.pipeworx.io/soilgrids/mcp'{
"mcpServers": {
"soilgrids": {
"type": "http",
"url": "https://gateway.pipeworx.io/soilgrids/mcp"
}
}
}@pipeworx/mcp-soilgridsclaude mcp add soilgrids -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-soilgrids@0.2.0{
"mcpServers": {
"soilgrids": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-soilgrids@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-soilgrids
ISRIC SoilGrids MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1837+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
soil_properties | Get soil property values at any coordinate from ISRIC SoilGrids (250m global grid) — clay/sand/silt %, pH, organic carbon, nitrogen, cation exchange, bulk density, water content. Values are returned in real units (scaled from raw map units). Keyless; the SoilGrids API may take several seconds to respond. |
soil_classification | Get the World Reference Base (WRB) soil classification at a coordinate from ISRIC SoilGrids — the most probable soil class (e.g. Cambisols, Podzols) plus the top 5 classes with probabilities. Keyless; may take several seconds to respond. |
list_soil_properties | List the soil properties available from ISRIC SoilGrids with their names and available depth intervals. Use this to discover valid property codes for soil_properties. Keyless; may take several seconds to respond. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"soilgrids": {
"url": "https://gateway.pipeworx.io/soilgrids/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/soilgrids/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1837+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/soil_properties \
-H 'Content-Type: application/json' \
-d '{"latitude":40.7128,"longitude":-74.006}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/soil_properties. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"soilgrids": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-soilgrids"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-soilgridsIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Soilgrids data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Soilgrids?
ISRIC SoilGrids MCP.
How do I install Soilgrids?
It runs as a remote server. In Claude Code: claude mcp add --transport http soilgrids 'https://gateway.pipeworx.io/soilgrids/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Soilgrids need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Soilgrids open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Soilgrids?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.