Change "Install with `pip install marimo[mcp]` or `uv add marimo[mcp]`" to the relevant instruction for the environment

[yairchu]

Description

My marimo process had the following output:

[W 251005 20:39:51 config:106] Failed to reconfigure MCP servers: MCP dependencies not available. Install with `pip install marimo[mcp]` or `uv add marimo[mcp]`
[E 251005 20:40:07 tool_manager:161] Failed to get MCP tools: MCP dependencies not available. Install with `pip install marimo[mcp]` or `uv add marimo[mcp]`

Similar to the recent changes in upgrade instructions at #6508, the same logic could be applied for these instructions.

Suggested solution

If running in a uv environment, suggest uv add, otherwise, suggest only pip install.

Are you willing to submit a PR?

• Yes

Alternatives

No response

Additional context

No response

[yairchu]

Btw, the suggested command doesn't work as is too (at least not on macOS):

$ uv add marimo[mcp]
zsh: no matches found: marimo[mcp]

It does work as uv add "marimo[mcp]"

[mscolnick]

hey @yairchu - that would be great. there are a bunch of places we use pip install.

maybe we can create a utility class (and later extend to pixi, conda, etc):

def get_install_text(packages: list[str]): str
   ...

[yairchu]

I see that marimo._runtime.runtime.Kernel has packages_callbacks.package_manager which can be any one of those in marimo._runtime.packages.package_managers.

Should the package manager be propagated to all the places that suggest to do pip install?

[mscolnick]

It might be a pain to propagate that through in some cases, but that would be more accurate.

We could pass down the package manager but making it optional. And if it's not supplied, just guessing how you currently do it.