@wirl/mcp 0.2.0 → 0.2.2

package/README.md

@@ -4,29 +4,33 @@ The wirl MCP server, run locally. It lets a coding agent deploy what it just bui
 
 ## Prefer the hosted server
 
-If your agent supports HTTP MCP, you do not need this package. Connect to the hosted endpoint and it opens the browser once to sign in:
+If your agent supports HTTP MCP, you do not need this package. Connect to the hosted endpoint:
 
 ```bash
 claude mcp add --transport http wirl https://app.wirl.dev/mcp
 ```
 
-The token it receives is deploy-scoped by default: it can deploy, roll back, pull and list, and cannot share apps, change who can open them, or touch connections, members or tokens. One checkbox on the consent page grants full access.
+`claude mcp add` only saves the server's configuration. Then sign in: run `/mcp` inside Claude Code and follow the steps in the browser, or run `claude mcp login wirl` in a terminal.
+
+The token the hosted endpoint gives the agent is deploy-scoped by default: it can deploy, roll back, pull and list, and cannot share apps, change who can open them, or touch connections, members or tokens. One checkbox on the consent page grants full access.
 
 ## Running it locally
 
-For agents without HTTP MCP support, this package runs the same tools over stdio, using the credentials `wirl login` wrote. wirl serves the package itself, so the command names its address rather than an npm name:
+For agents without HTTP MCP support, this package runs the same tools over stdio, using the credentials `wirl login` wrote. `npx` fetches it from npm the first time, so there is nothing to install beyond Node 20 or later:
 
 ```bash
-claude mcp add wirl -- npx -y https://app.wirl.dev/cli/wirl-mcp.tgz
+claude mcp add wirl -- npx -y @wirl/mcp
 ```
 
 Cursor and anything else that speaks MCP take the same command in their own configuration:
 
 ```json
-{ "mcpServers": { "wirl": { "command": "npx", "args": ["-y", "https://app.wirl.dev/cli/wirl-mcp.tgz"] } } }
+{ "mcpServers": { "wirl": { "command": "npx", "args": ["-y", "@wirl/mcp"] } } }
 ```
 
-The first time, the agent calls `wirl_login`, shows you a link and a code, and carries on once you approve in the browser. A local server acts with the CLI's credentials, which are full-scope; revoke them on the Connect an agent page at app.wirl.dev if an agent should lose access.
+If your npm registry does not carry wirl, or to run exactly the build app.wirl.dev serves, name its address instead of the package: `claude mcp add wirl -- npx -y https://app.wirl.dev/cli/wirl-mcp.tgz`.
+
+The local server signs in the first time a wirl tool needs it: the agent calls `wirl_login`, which returns a link and a code, and the agent shows both to the person. The person approves the code in the browser, and the agent's next wirl tool call works. A machine already signed in with `npx wirl login` skips this. A local server acts with the CLI's credentials, which are full-scope; revoke them on the Connect an agent page at app.wirl.dev if an agent should lose access.
 
 ## Tools