CLIO Geojson
Validate and summarize GeoJSON feeds in your agent before you ship map features, ETL jobs, or location APIs that would fail on malformed geometry.
Overview
io.github.iowarp/geojson-mcp is a MCP server for the Ship phase that inspects, validates, and summarizes GeoJSON documents for agents before release.
What is this MCP server?
- Inspects, validates, and summarizes GeoJSON documents through MCP tools
- Stdlib-only GeoJSON handling emphasis—lighter dependency story within clio-kit
- stdio MCP transport (clio-kit 2.2.3 on PyPI)
- Helps agents explain feature counts, bounds, and structure without manual jq scripts
- Pairs logically with geo-mcp rendering after data is known good
- Version 2.2.3 in MCP registry metadata
- Stdio transport via PyPI clio-kit package
- Server title CLIO Geojson under namespace io.github.iowarp/geojson-mcp
Community signal: 25 GitHub stars.
What problem does it solve?
Malformed or surprising GeoJSON slips into your branch and you only discover broken maps or API errors after deploy.
Who is it for?
Builders shipping location features who want quick GeoJSON sanity checks and summaries inside their MCP coding workflow.
Skip if: Teams that need heavy spatial analysis, reprojection, or topology repair at scale—this server focuses on inspection and validation summaries.
What do I get? / Deliverables
With the server connected, your agent can validate and summarize each GeoJSON artifact so you fix structure issues during review instead of in production.
- Validation signals and summaries for GeoJSON inputs
- Agent-readable feature and geometry overviews for code review
- Reduced risk of shipping broken geospatial payloads
Recommended MCP Servers
Journey fit
Catching invalid GeoJSON belongs in the ship lane—quality gates before release—rather than only at initial data discovery. Testing is the canonical shelf because inspect-and-validate workflows mirror pre-release checks on fixtures, imports, and API payloads.
How it compares
GeoJSON QA MCP tool, not a map renderer or general database migration skill.
Common Questions / FAQ
Who is io.github.iowarp/geojson-mcp for?
It is for developers and solo builders handling GeoJSON who want MCP agents to validate structure and produce readable summaries before integration or release.
When should I use io.github.iowarp/geojson-mcp?
Use it in Ship when reviewing imports, API fixtures, or user-uploaded geographic data, especially right before merging map or geospatial endpoints.
How do I add io.github.iowarp/geojson-mcp to my agent?
Install clio-kit from PyPI, register io.github.iowarp/geojson-mcp as a stdio MCP server in your client, and invoke tools against GeoJSON files or strings in your project.