CLIO Sac
Inspect SAC seismic waveforms and TAR archive members from an agent when you process geophysical datasets.
Overview
io.github.iowarp/sac-mcp is a MCP server for the Operate phase that analyzes SAC seismic-waveform files and TAR archives for agents via stdio.
What is this MCP server?
- CLIO Sac MCP server for SAC seismic-waveform files and TAR archive inspection
- Analyze archive members and compute workflow-oriented metrics via MCP tools
- Bundled in clio-kit 2.2.3 on PyPI with stdio transport
- Targets geophysics and seismology builders automating file review with agents
- GitHub source at iowarp/clio-kit alongside other CLIO scientific MCP servers
- Server version 2.2.3
- PyPI package clio-kit, stdio transport
- Repository github.com/iowarp/clio-kit
Community signal: 25 GitHub stars.
What problem does it solve?
Geophysics builders manually unpack TAR archives and probe SAC headers and traces outside the agent, breaking flow on every new event or station file.
Who is it for?
Solo builders and researchers shipping seismic or waveform tooling who already use SAC and want agent-driven archive inspection.
Skip if: General web app developers with no SAC or seismology data, or teams that only need generic CSV analytics.
What do I get? / Deliverables
After registration, your agent can inspect SAC and TAR members and drive analysis steps through MCP instead of ad hoc terminal scripts.
- MCP tools for SAC and TAR inspection wired into your agent
- Repeatable agent-driven checks on waveform files and archive members
- Less manual scripting for seismic file operations
Recommended MCP Servers
Journey fit
Seismic file inspection and derived metrics are ongoing analysis work after data pipelines exist, which maps to operating and iterating on specialized datasets. Iterate fits because SAC and TAR analysis is repeated catalog and archive review rather than greenfield UI or landing-page work.
How it compares
Domain-specific seismic-file MCP server, not a generic object-store or spreadsheet integration.
Common Questions / FAQ
Who is io.github.iowarp/sac-mcp for?
It is for developers and researchers working with SAC seismic waveforms and TAR bundles who want MCP access from AI coding agents.
When should I use io.github.iowarp/sac-mcp?
Use it when you repeatedly inspect SAC files or TAR archive members and want the agent to orchestrate that analysis during operational data review.
How do I add io.github.iowarp/sac-mcp to my agent?
Install clio-kit from PyPI, add the sac-mcp MCP server with stdio transport in your client config, and ensure local paths to SAC and TAR data are available to the agent.