CLIO Geo
Generate static map images from GeoJSON layers and basemaps inside your agent when you are building location features, reports, or marketing visuals.
Overview
io.github.iowarp/geo-mcp is a MCP server for the Build phase that renders GeoJSON vector layers into map images with basemaps for AI-assisted product work.
What is this MCP server?
- Renders GeoJSON vector layers on basemaps into map images via MCP
- Part of CLIO Geo in clio-kit 2.2.3 with stdio MCP transport
- Agent-driven map generation without opening a separate GIS desktop tool
- Useful for quick prototypes of geo dashboards and static map assets
- Source and packaging aligned with iowarp/clio-kit on GitHub and PyPI
- Registry version 2.2.3 with stdio transport
- Distributed via PyPI package clio-kit
- MCP name io.github.iowarp/geo-mcp (title CLIO Geo)
Community signal: 25 GitHub stars.
What problem does it solve?
You have GeoJSON boundaries or points but generating a shareable map preview means wiring a map stack or manual exports outside your agent session.
Who is it for?
Indie developers building geo-aware SaaS, travel tools, or logistics MVPs who want fast static map renders from GeoJSON via MCP.
Skip if: Products that need full interactive slippy maps with live user panning only—this server targets image rendering, not a replacement for MapLibre or Mapbox GL in the browser.
What do I get? / Deliverables
Once registered, your agent can request rendered maps from your layers so you can drop images into UIs, docs, or pitches in minutes.
- Rendered map images from GeoJSON vector inputs
- Agent-repeatable map previews for UI and documentation
- Faster geo feature demos without a dedicated GIS workflow
Recommended MCP Servers
Journey fit
Rendering map assets is part of constructing the product surface—dashboards, landing embeds, and exports—rather than early idea research or post-launch analytics alone. Frontend is the primary shelf because the server’s output is visual map images that ship in UIs, docs, and shareable content even if GeoJSON came from a backend pipeline.
How it compares
Map rendering MCP integration, not a GeoJSON validation-only or SEO-focused launch tool.
Common Questions / FAQ
Who is io.github.iowarp/geo-mcp for?
It is for builders who work with GeoJSON and want their MCP-enabled coding agent to produce basemap-backed map images for apps, decks, or content.
When should I use io.github.iowarp/geo-mcp?
Use it during Build when you need visual map outputs from vector data—for feature previews, investor screenshots, or static assets in a web product.
How do I add io.github.iowarp/geo-mcp to my agent?
Install clio-kit 2.2.3 from PyPI, add the io.github.iowarp/geo-mcp stdio server entry in your MCP client config, and supply GeoJSON plus basemap options your tools accept.