Soilgrids logo

Soilgrids

Query global SoilGrids properties and WRB soil classifications at coordinates through MCP.

Install Soilgrids

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "soilgrids": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-soilgrids"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Soilgrids MCP server exposes ISRIC SoilGrids data through tools for coordinate-based soil analysis. It returns scaled soil properties, WRB classifications with probability rankings, and a directory of available properties and depth intervals. The server can run locally over stdio or through Pipeworx's hosted MCP endpoint, with no API key required for the listed SoilGrids tools. Reach for it when an agent needs soil composition, classification, or property-code discovery for a location.

Use cases

  • Query soil composition at a latitude and longitude
  • Classify a location using WRB soil classes
  • Discover valid SoilGrids property codes and depth intervals
  • Retrieve scaled soil values for environmental analysis

Key features

  • Coordinate-based SoilGrids property lookup
  • WRB classification with top-five probabilities
  • Property and depth-interval discovery
  • 250 m global soil grid coverage
  • Hosted HTTP and local stdio access

Tools3

What Soilgrids lets your agent do. Expand a tool for its parameters.

Self-reported~201 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-soilgrids (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads607Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Soilgrids works

What Soilgrids MCP server does

The Soilgrids MCP server connects MCP clients and agents to ISRIC SoilGrids, a global 250 m soil-data grid. Its tools work with geographic coordinates and provide either measured soil-property values or a World Reference Base (WRB) classification.

soil_properties retrieves values for properties such as clay, sand, silt, pH, organic carbon, nitrogen, cation exchange, bulk density, and water content. The response uses real units rather than the raw map-unit scaling used by the source data. soil_classification returns the most probable WRB soil class and the five highest-ranked classes with their probabilities. list_soil_properties describes the properties available from SoilGrids and the depth intervals associated with them, which helps an agent choose valid property codes before making a property query.

How it works

You can connect the Soilgrids MCP server to an MCP client through the hosted streamable HTTP endpoint:

config.json
{
  "mcpServers": {
    "soilgrids": {
      "url": "https://gateway.pipeworx.io/soilgrids/mcp"
    }
  }
}

The hosted endpoint lists the SoilGrids tools together with shared Pipeworx gateway tools. The gateway also provides an ask_pipeworx route for asking questions in natural language; it can select a tool and populate its arguments. Alternatively, the full Pipeworx endpoint exposes the broader catalog directly.

A standalone package is available when you want only this pack's tools. It communicates over stdin and stdout and does not require a Pipeworx account or a gateway round trip:

config.json
{
  "mcpServers": {
    "soilgrids": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-soilgrids"]
    }
  }
}

Setup and configuration

For the hosted option, add the endpoint to an MCP client that supports remote MCP connections. For local use, run npx -y @pipeworx/mcp-soilgrids or use the stdio configuration above. The provided setup does not define required environment variables or an API-key configuration. Direct HTTP calls are also available through endpoints such as POST https://gateway.pipeworx.io/v1/tools/soil_properties with a JSON body containing latitude and longitude.

Tools and capabilities

  • Query soil properties at a coordinate.
  • Retrieve WRB classification and the five most probable classes.
  • Enumerate supported property codes and depth ranges.
  • Use values returned in real units for supported properties.
  • Access the tools through hosted MCP, local stdio, or the gateway's HTTP tool interface.

Limitations and notes

SoilGrids requests may take several seconds to complete. The data represents a 250 m global grid, so results should be interpreted at that source resolution rather than as exact field measurements. The property tool depends on valid property codes; use list_soil_properties to discover the available codes and depth intervals. The hosted pack endpoint includes shared Pipeworx meta-tools in addition to the pack-specific tools, while the standalone process exposes only the Soilgrids tools.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Soilgrids

Soilgrids is an MCP server that connects AI agents to ISRIC SoilGrids. Its main tools retrieve soil properties at coordinates, return WRB soil classifications with probability rankings, and list available property codes with depth intervals. It supports hosted gateway access and a standalone local stdio package.

Install it locally by configuring an MCP client to run `npx -y @pipeworx/mcp-soilgrids`. The package communicates over stdin and stdout and does not require a Pipeworx account. You can instead configure the hosted endpoint at `https://gateway.pipeworx.io/soilgrids/mcp`.

Yes, Soilgrids works with Cursor through the hosted MCP endpoint. Add `https://gateway.pipeworx.io/soilgrids/mcp` as the server URL in Cursor's MCP configuration. The README also names Claude Desktop and Windsurf as supported client options.

No, the SoilGrids tools are described as keyless.

SoilGrids requests may take several seconds because the underlying API can be slow to respond. This applies to soil-property, classification, and property-list requests, so clients should allow for that response time.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSoilgrids AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/soilgrids?style=directory)](https://allmcps.com/mcp/soilgrids)
HTML Embed
<a href="https://allmcps.com/mcp/soilgrids"><img src="https://allmcps.com/api/badge/soilgrids?style=directory" alt="Soilgrids on AllMCPs" /></a>