rwasis-mcp
MCP server for RwaSIS — Rwanda's national soil information system, operated by the Rwanda Agriculture Board (RAB).
Part of the Inzira project — Layer 2.
Installation
pip install rwasis-mcp
Usage
With Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"rwasis": {
"command": "rwasis-mcp"
}
}
}
With mcp CLI
mcp run rwasis-mcp
Tools
get_crops
Returns all crops registered in the RwaSIS system.
Returns: List of crops — Bean, Cassava, Rice, Potato, Maize, Wheat.
Note: only Potato and Rice currently have fertilizer recommendations.
get_soil_by_location
Returns soil data and fertilizer recommendations for a Rwanda location.
Parameters:
| Name | Type | Description |
|---|---|---|
name |
string | Village, cell, sector, or district name (e.g. Gasabo, Kigali) |
Returns: carbon, calcium, potassium, phValues, erosionRisk, erosionRecommendation, potatoFertilizerRecommendation, riceFertilizerRecommendation, boundary.
Note: the
/boundaries?name=endpoint currently returns empty arrays for all locations — the soil data tables appear not yet populated on the RAB side. This is a known issue raised with RAB.
get_soil_by_upi
Returns parcel location and soil data for a Rwanda UPI (parcel identifier).
Parameters:
| Name | Type | Description |
|---|---|---|
upi |
string | Rwanda parcel UPI, e.g. 1/03/08/04/2148 |
UPI format: Province / District / Sector / Cell / Parcel
| Part | Format |
|---|---|
| Province | single digit (1–5) |
| District | two digits |
| Sector | two digits |
| Cell | two digits |
| Parcel | four digits |
Returns: resolved location (province, district, sector, cell, village), parcel boundary polygon, and fertilizer recommendations for Potato and Rice where available.
Example response for 1/03/08/04/2148:
- Location: Kigali City → Kicukiro → Masaka → Gitaraga → Kabeza
- Rice fertilizer: NPK 17-17-17 at 200 kg/ha, Urea at 100 kg/ha
License
MIT
Metadata
Release files for rwasis-mcp 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rwasis_mcp-0.1.7.tar.gz | 6.3 kB | Without provenance | Details for rwasis_mcp-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rwasis_mcp-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for rwasis_mcp-0.1.7-py3-none-any.whl |
Total release size: 12.4 kB
Release files / rwasis_mcp-0.1.7.tar.gz
| Download URL | rwasis_mcp-0.1.7.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
588d89004007c3dc91c6b31781a38a060207c7286b7a41452984af9e618a427c
|
|
BLAKE2b-256 checksum How to use checksums |
a736095b5f954536a5f79d4304b25e5f4c3c74a9032e8d84e25a997d6cc79418
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.5
|
Release files / rwasis_mcp-0.1.7-py3-none-any.whl
| Download URL | rwasis_mcp-0.1.7-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a6111b96b2bcbbeb4af094c3ec909256341abe090d26ad433890416debfabaf2
|
|
BLAKE2b-256 checksum How to use checksums |
5a2c8c5ae396367ecf0d61a55ae1b30800b390a17c3a574df6b599a38e2909b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.5
|
Security for rwasis-mcp 0.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.