
CLIO Geo
io.github.iowarpPublished by GitHub account iowarpv2.3.2Updated Oct 30, 2026
MCP server for rendering GeoJSON vector layers into map images with basemaps
Overview
CLIO Geo is a local MCP server from the CLIO Kit collection that renders GeoJSON vector layers into map images with basemaps.
- What you can do
- Render GeoJSON vector layers as map images with basemaps
- Inspect, validate and summarize GeoJSON data through the companion geojson server
- Analyze DEMs and terrain point clouds through the companion terrain server
- Run through the shared clio-kit launcher alongside other scientific servers
- When to use it
- Use it when an assistant needs to turn GeoJSON layers into map images for reports, papers or quick visual checks, or when geospatial work sits alongside other scientific data tasks in the CLIO Kit collection.
- Requirements
- Runs locally over stdio as part of the CLIO Kit Python package (clio-kit), installed with uv tool install and started via the clio-kit mcp-server geo command. Desktop only; no authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open CLIO Geo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CLIO Kit
[License: BSD-3-Clause] [PyPI version] [Python] [FastMCP] [CI] [Coverage]
[MCP Servers] [Ruff] [Type Checked] [Package Manager] [Security Audit]
CLIO Kit - Part of the IoWarp platform's tooling layer for AI agents. A comprehensive collection of tools, skills, plugins, and extensions. It ships 22 Model Context Protocol (MCP) servers for scientific computing and enables AI agents to interact with HPC resources, scientific data formats, and research datasets.
Chat with us on Zulip or join us
Developed by [GRC Logo] Gnosis Research Center
❌ Without CLIO Kit
Working with scientific data and HPC resources requires manual scripting and tool-specific knowledge:
- ❌ Write custom scripts for every HDF5/Parquet file exploration
- ❌ Manually craft Slurm job submission scripts
- ❌ Switch between multiple tools for data analysis
- ❌ No AI assistance for scientific workflows
- ❌ Repetitive coding for common research tasks
✅ With CLIO Kit
AI agents handle scientific computing tasks through natural language:
- ✅ "Analyze the temperature dataset in this HDF5 file" - HDF5 MCP does it
- ✅ "Submit this simulation to Slurm with 32 cores" - Slurm MCP handles it
- ✅ "Find papers on neural networks from ArXiv" - ArXiv MCP searches
- ✅ "Plot the results from this CSV file" - Plot MCP visualizes
- ✅ "Optimize memory usage for this pandas DataFrame" - Pandas MCP optimizes
- ✅ "Find all documents where pressure exceeds 200 kPa" - Agentic Search retrieves
One unified interface. 22 MCP servers. Hybrid search engine. 150+ specialized tools. Built for research.
CLIO Kit is part of the IoWarp platform's comprehensive tooling ecosystem for AI agents. It brings AI assistance to your scientific computing workflow—whether you're analyzing terabytes of HDF5 data, managing Slurm jobs across clusters, or exploring research papers. Built by researchers, for researchers, at Illinois Institute of Technology with NSF support.
Part of IoWarp Platform: CLIO Kit is the tooling layer of the IoWarp platform, providing skills, plugins, and extensions for AI agents working in scientific computing environments.
One simple command. Production-ready, fully typed, BSD-3-Clause licensed, and live-tested in real HPC environments.
🚀 Quick Installation
One Command for Any Server
uv tool install keeps CLIO Kit in a persistent, isolated tool environment.
Use uvx --from 'clio-kit==2.4.3' clio-kit ... only for a temporary, one-shot
invocation.
Released clio-kit wheels execute each embedded MCP server from that server's
shipped uv.lock. The launcher uses a source-and-lock-addressed environment
under the user cache, installs only production dependencies, and refuses to
resolve an embedded server whose lock is missing. The --branch launcher
option is an explicit development path and is not an immutable
release-artifact path.
The root wheel also ships machine-readable user contracts for the locked
JARVIS, SLURM, Spack, and Scientific Catalog servers. These artifacts are generated from real stdio
tools/list exchanges and include canonical SHA-256 digests for downstream
federation gates:
Install in Claude Code
See Claude Code MCP docs for more info.
Install in Claude Desktop
Edit claude_desktop_config.json:
See Claude Desktop MCP docs for more info.
Available Packages
The version below is each MCP server's agent-facing contract version, not the
containing clio-kit wheel version. JARVIS 3.4 and SLURM 3.0 have contracts
redesigned for agent use. Spack is at 2.1, while the other
contracts retain their existing 2.x identities until a focused upgrade.
The Spack install contract makes concretization explicit: reuse=true passes
spack install --reuse, while reuse=false passes spack install --fresh.
Agents should discover first, install only when needed, then pass the exact
spack_locate result to JARVIS for runtime loading. A find with no installed
match is normal typed data (count=0, packages=[]); locate reports the
distinct not_installed semantic, while real Spack failures remain errors.
Agentic Search
Hybrid retrieval engine for scientific corpora — combines lexical (BM25), vector, graph, and scientific search (numeric range, unit matching, formula targeting) over namespaced document collections. DuckDB storage, FastAPI, async job queue, OpenTelemetry tracing, Prometheus metrics.
API endpoints: /query, /jobs/index, /documents, /health, /metrics — full docs
📖 Usage Examples
HDF5: Scientific Data Analysis
Tools used: open_file, analyze_dataset_structure, read_partial_dataset, list_attributes
Slurm: HPC Job Management
Tools used: submit_slurm_job, check_job_status, get_job_output
ArXiv: Research Discovery
Tools used: search_arxiv, get_paper_details, export_to_bibtex, download_paper_pdf
Pandas: Data Processing
Tools used: load_data, handle_missing_data, groupby_operations, save_data
Plot: Data Visualization
Tools used: line_plot, data_info
Agentic Search: Scientific Retrieval
CLI: clio-kit search query --namespace local_fs --q "pressure > 200 kPa"
🚨 Troubleshooting
Server Not Found Error
If clio-kit mcp-server <server-name> fails:
Import Errors or Missing Dependencies
For development or local testing:
uv or clio-kit Command Not Found
Install uv package manager:
Then install CLIO Kit persistently and expose uv's tool directory:
Team
- Gnosis Research Center (GRC) - Illinois Institute of Technology | Lead
- HDF Group - Data format and library developers | Industry Partner
- University of Utah - Research collaboration | Domain Science Partner
Sponsored By
[NSF Logo] NSF (National Science Foundation) - Supporting scientific computing research and AI integration initiatives
we welcome more sponsorships. please contact the Principal Investigator
Ways to Contribute
- Submit Issues: Report bugs or request features via GitHub Issues
- Develop New MCPs: Add servers for your research tools (CONTRIBUTING.md)
- Improve Documentation: Help make guides clearer
- Share Use Cases: Tell us how you're using CLIO Kit in your research
Full Guide: CONTRIBUTING.md
Community & Support
- Chat: Zulip Community
- Join: Invitation Link
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Website: https://docs.iowarp.ai/
- Project: IOWarp Project
Source: README.md at commit 93e41d7
Tools
0Version history
3- v2.3.2LatestOct 29, 2026
- v2.3.1Oct 9, 2026
- v2.2.3Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts