You can work with Musubi from your terminal or from a coding agent you already use.
The MCP server (musubi-mcp) connects Musubi to a coding agent you already use, like Claude Code, Cursor, or Codex. Your agent's model does the reasoning and calls Musubi as one of its tools alongside everything else it has access to, for example your internal documentation or data tools. That makes it the right choice for work that spans Musubi and your other systems in one session.
The CLI (musubi) is a command-line tool for your terminal and CI: import datasets in bulk, manage policies as code with changes reviewed in pull requests, and run evaluations as part of your release process.
| Musubi Agent | MCP server (musubi-mcp) | CLI (musubi) | |
|---|---|---|---|
| Where it runs | In the app | Inside your coding agent: Claude Code, Cursor, Codex, or Zed | Your terminal or CI |
| Who reasons | The frontier model we provide, with our T&S playbooks | Your agent's model, with its skills and yours | You do. Deterministic commands, no LLM in the loop |
| Setup | None | One install command | One install command |
| Best for | Conversational work inside Musubi; it sees the page you're on | Work that spans Musubi and your other systems in one session | Scripts, pipelines, bulk imports, and policies managed as code |
| Tradeoffs | Desktop browsers only; can't reach tools outside Musubi | Needs an MCP host; your host's model shapes the results | No conversation; you need to know what you want |
One command installs the Musubi CLI and connects it to your editor or agent. You'll sign in through your browser as part of setup.
curl -sSL <https://app.musubilabs.ai/install.sh> | sh
musubi --help to see what's available.musubi doctor any time to inspect your config and key health.Re-run the same command — it detects an existing install and upgrades in place. Or run musubi upgrade from a terminal.
The installer respects HTTPS_PROXY, HTTP_PROXY, and NO_PROXY environment variables. Set them in your shell before running the curl command.