CLIO Adios
Let your coding agent open BP5 scientific datasets through ADIOS2 instead of writing one-off C++/Python analysis scripts.
Overview
io.github.iowarp/adios-mcp is a MCP server for the Build phase that lets agents fetch and analyze ADIOS2 BP5 scientific data files, metadata, and attributes.
What is this MCP server?
- Reads and analyzes ADIOS2 BP5 data files from the agent session
- Surfaces dataset metadata and attributes alongside variable payloads
- Ships as CLIO Adios (clio-kit on PyPI) with stdio MCP transport
- Version 2.2.3 aligned with the iowarp/clio-kit server.schema.json manifest
- Pairs with other CLIO Kit MCP servers for compression and logging workflows
- Published server version 2.2.3
- PyPI package identifier clio-kit with stdio transport
- Repository source github.com/iowarp/clio-kit
Community signal: 25 GitHub stars.
What problem does it solve?
BP5 simulation and experiment outputs are painful to probe interactively when you only have shell tools and ad-hoc Python snippets.
Who is it for?
Indie technical founders or researchers building agents around simulation, CFD, or lab pipelines that standardize on ADIOS2 BP5.
Skip if: Builders shipping everyday web SaaS with Postgres or JSON APIs who never touch scientific binary formats.
What do I get? / Deliverables
Your agent can query BP5 contents and attributes through MCP so analysis and integration code starts from verified file facts.
- Agent-callable access to BP5 variables, metadata, and attributes
- Faster grounding for scripts that transform or validate simulation outputs
- Repeatable scientific file inspection without leaving the agent UI
Recommended MCP Servers
Journey fit
ADIOS2 BP5 access lands in Build when you wire HPC or simulation outputs into tooling, notebooks, or agent-driven inspection pipelines. Integrations is the right shelf because this MCP exposes an external scientific I/O stack (ADIOS2) to the agent via stdio, not a generic app feature.
How it compares
Scientific ADIOS2 file MCP, not a SQL database server or a generic document store.
Common Questions / FAQ
Who is io.github.iowarp/adios-mcp for?
Developers and researchers who need agent-assisted inspection of ADIOS2 BP5 datasets during build or analysis workflows.
When should I use io.github.iowarp/adios-mcp?
Use it when a project reads BP5 outputs and you want MCP tools for metadata, attributes, and data access instead of manual ADIOS2 scripts.
How do I add io.github.iowarp/adios-mcp to my agent?
Register the stdio MCP server from the clio-kit PyPI package (2.2.3) in Claude Code, Cursor, or another MCP host per your client’s server config.