Quickstart¶
1. Prerequisites¶
The installer checks for these and helps you install the missing ones:
| Tool | Needed for | Notes |
|---|---|---|
git, curl |
cloning + downloading | usually preinstalled |
| an agent client | the integration target | any of the four below — the installer auto-detects the ones present and refuses to run if it finds none |
uv |
Python servers | auto-installed from astral.sh/uv if missing |
| Go ≥ 1.25 | the two Go servers | only needed for irods + formation; pass --no-go to skip them |
Supported agent clients:
| Client | Detected via | Integration page |
|---|---|---|
| Claude Code | claude on PATH |
Claude Code |
| Codex CLI | codex on PATH |
Codex CLI |
| Antigravity | agy on PATH, the IDE app, or a ~/.gemini config dir |
Antigravity |
| OpenCode | opencode on PATH |
OpenCode |
Other clients1 can reuse the manual install steps.
Windows users
Run everything inside WSL (Ubuntu or similar). The installer detects WSL and
treats it as Linux. Native PowerShell / cmd are not supported.
2. Install¶
This will:
- Detect your platform (Linux / macOS / WSL).
- Clone the four repos from
idss-mesainto~/.mesa/repos/. - Create a Python venv at
~/.mesa/.venvand installmesa-ducklake+mesa-mcp. - Build the Go servers into
~/.mesa/bin/. - Register
mesa-mcp,irods, andformationwith every detected client — Claude Code at user scope, Codex globally, Antigravity and OpenCode via their config files. Restrict targets with--for, e.g.bash -s -- --for claude,codex.
3. Verify¶
You should see mesa-mcp, irods, and formation listed. Then, in your agent
session, try:
Ping the CyVerse Data Store and list what's in the shared directory.
That exercises mesa-mcp's ds_ping and ds_list_directory tools against the public
data.cyverse.org zone — no login needed.
4. (Optional) Authenticate¶
Anonymous access is read-only on public collections. To act as yourself, re-run with your CyVerse credentials:
CYVERSE_USERNAME=you CYVERSE_PASSWORD='••••••' \
curl -fsSL https://raw.githubusercontent.com/idss-mesa/docs/main/install.sh | bash
The credentials are threaded into every client registration the installer creates.
See Credentials for all the options (env vars, ~/.irods, per-server config).
Updating & uninstalling¶
Re-running the one-liner pulls the latest code and rebuilds — it is safe to run again.
Uninstalling removes the three servers from every detected client and (after
confirmation) deletes ~/.mesa:
curl -fsSL https://raw.githubusercontent.com/idss-mesa/docs/main/install.sh | bash -s -- --uninstall
-
OpenClaw support is deferred until its MCP interface can be verified. ↩