Install reference¶

The installer is a single POSIX bash script, install.sh. You can pipe it from curl or clone this repo and run it directly.

# one-liner
curl -fsSL https://raw.githubusercontent.com/idss-mesa/docs/main/install.sh | bash

# from a clone
git clone https://github.com/idss-mesa/docs.git && ./docs/install.sh

Flags¶

When piping through curl, pass flags after -s --:

curl -fsSL https://raw.githubusercontent.com/idss-mesa/docs/main/install.sh | bash -s -- --no-go

Environment overrides¶

What it lays down¶

~/.mesa/
├── repos/
│   ├── mesa-mcp/            # editable Python source
│   ├── mesa-ducklake/       # editable Python source
│   ├── mesa-anyjev/         # editable Python source (plugin for mesa-mcp)
│   └── irods-mcp-server/    # Go source
├── .venv/                   # uv-managed Python 3.11 venv
│   └── bin/mesa-mcp         # stdio MCP server entry point
└── bin/
    └── irods-mcp-server     # built Go binary

Nothing is installed for formation: it is CyVerse's hosted server, registered by URL. Older installs also built a local bin/formation-mcp; a re-run deletes that binary and replaces the old registration (see Moving from the local formation-mcp). You can delete the leftover repos/formation-mcp/ yourself.

Idempotency¶

Every step is safe to repeat:

• Repos are git pull --ff-only'd if already present, cloned otherwise.
• The venv is recreated and packages reinstalled editable.
• The Go binary is rebuilt.
• For the CLI clients (Claude Code, Codex), each mcp add is preceded by an mcp remove, so re-running updates the registration in place rather than duplicating it. Claude Code's hosted formation entry is left alone when it is already right, because removing it would also delete your Formation sign-in. For Codex, formation is written straight into ~/.codex/config.toml, because codex mcp add --url would start an interactive sign-in; Codex older than 0.77 is skipped with a warning.
• Config files the installer rewrites keep their permissions (a new one is created readable by you only), and a symlinked config is written through the link.
• For the config-file clients (Antigravity, OpenCode), the installer rewrites its own entries in the JSON, leaving any other servers you have configured untouched.

Manual install¶

If you'd rather not use the script, the equivalent steps are:

# Python servers
uv venv --python 3.11 ~/.mesa/.venv
uv pip install --python ~/.mesa/.venv/bin/python -e ./mesa-ducklake -e ./mesa-mcp

# Go server
( cd irods-mcp-server && make build )                     # -> bin/irods-mcp-server
mkdir -p ~/.mesa/bin
cp irods-mcp-server/bin/irods-mcp-server ~/.mesa/bin/

Formation needs no build: register its URL and sign in.

Then register the servers with your client:

claude mcp add mesa-mcp  -s user -- ~/.mesa/.venv/bin/mesa-mcp --transport stdio
claude mcp add irods     -s user -- ~/.mesa/bin/irods-mcp-server -c .../config-stdio.yaml
claude mcp add --transport http -s user formation https://de.cyverse.org/formation/mcp

codex mcp add mesa-mcp  -- ~/.mesa/.venv/bin/mesa-mcp --transport stdio
codex mcp add irods     -- ~/.mesa/bin/irods-mcp-server -c .../config-stdio.yaml
codex mcp add formation --url https://de.cyverse.org/formation/mcp   # signs you in now

Machine-readable versions of this page: Markdown twin · raw source on GitHub · llms.txt · llms-full.txt (whole site). See For AI agents.