mcp · Global

geonode-mcp

Search, edit metadata/permissions, upload datasets and transfer ownership on a GeoNode catalogue, every call made as the logged-in user via OAuth2

Claim this listing

Represent geonode-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered llm-inferred: keyword search across catalogue resources (datasets, documents, maps) · resource metadata read and edit (title, abstract, keywords) · resource permission read, grant and revoke for users and groups · dataset upload from file content, with shapefile sidecar files · upload status polling · resource deletion · map creation from dataset pks · linked resource lookup · keyword vocabulary listing · resource ownership transfer (GeoNode 4.4.x) · user lookup by name or email
Formats docs-verified: GeoPackage (.gpkg) · Shapefile (.shp with .dbf, .shx and .prj sidecars)
Access docs-verified: Free, open-source (Apache-2.0). Requires a GeoNode 4.4.x or later instance reachable over HTTPS, a one-time admin-registered public OAuth2 client, and per-user GeoNode credentials.

Use cases llm-inferred: Bulk-tagging and abstract updates for flood-hazard dataset records already in a GeoNode catalogue · Sharing a dataset with a project group by granting group view permissions after reading current access · Uploading a GeoPackage of gauge or site locations as a new catalogue dataset, with status polling · Reassigning ownership of a resource when a staff member hands over a project (4.4.x only)
Audience llm-inferred: GIS analysts · GeoNode catalogue administrators and data managers · hydrologists and flood modellers who publish datasets to a shared GeoNode

Constraints docs-verified: Working prototype, not yet used in production · Tested against GeoNode 4.4.x only; 5.x expected to work but unverified · Search is keyword-only, with no spatial or temporal filtering · One shared MCP_BEARER_TOKEN for all users, which cannot be revoked per person · Password grant needs users to type their GeoNode/LDAP password; SSO sites need a different flow · Tokens stored in a plain file (~/.geonode-mcp/tokens.json) with no OS keyring · New keywords cannot be created, only existing ones attached · Uploads are base64 in-band, so very large files are impractical · Ownership transfer works on GeoNode 4.4.x only · delete_resource is irreversible and asks the user for no confirmation

Licence: Apache-2.0
Authentication: API key via env: GEONODE_OAUTH_CLIENT_ID, MCP_BEARER_TOKEN (auto-extracted from README)
GitHub stars: 1
Last commit: 21/09/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Verified via GitHub API (2026-10-15). Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · research sweep: manual-2026-10-15 (sparkgeo/geo-mcp-servers)