docs: remove uv installation instructions from README - #15
Conversation
This repo is not a tutorial for installing uv; users who need it can refer to the linked uvx docs.
Keep the remaining agents collapsed.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8806ae43ed
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ``` | ||
|
|
||
| Then register the server with your AI coding agent. Click yours to expand 👇 | ||
| RemoteShell is a stdio MCP server distributed on PyPI. Run it directly with [`uvx`](https://docs.astral.sh/uv/) — no install step required. Then register the server with your AI coding agent. Click yours to expand 👇 |
There was a problem hiding this comment.
When installing on a fresh machine that does not already have uv/uvx on PATH, every registration example below stores or invokes uvx remoteshell-mcp, so the MCP client will fail with a command-not-found error. This edit removed the only prerequisite/installation note while still saying “no install step required,” leaving first-time users without a step to make the documented commands runnable; consider keeping a short uvx prerequisite note even if the curl installer snippet is omitted.
Useful? React with 👍 / 👎.
1 participant
Changes
curl | shuv install script and the "make sure uv is installed" instruction from the Installation section — this repo is not a tutorial for installing uv. Theuvxdoc link remains for anyone who needs it.<details>blocks have noopenattribute, from docs: add collapsible per-agent MCP install instructions #13), so no change was needed there.The Development section keeps its
uv runusage since that is the actual dev workflow for this repo.