@wirl/mcp 0.2.1 → 0.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -3
- package/bin.js +1055 -117
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,13 +4,15 @@ The wirl MCP server, run locally. It lets a coding agent deploy what it just bui
|
|
|
4
4
|
|
|
5
5
|
## Prefer the hosted server
|
|
6
6
|
|
|
7
|
-
If your agent supports HTTP MCP, you do not need this package. Connect to the hosted endpoint
|
|
7
|
+
If your agent supports HTTP MCP, you do not need this package. Connect to the hosted endpoint:
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
10
|
claude mcp add --transport http wirl https://app.wirl.dev/mcp
|
|
11
11
|
```
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
`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.
|
|
14
|
+
|
|
15
|
+
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.
|
|
14
16
|
|
|
15
17
|
## Running it locally
|
|
16
18
|
|
|
@@ -28,7 +30,7 @@ Cursor and anything else that speaks MCP take the same command in their own conf
|
|
|
28
30
|
|
|
29
31
|
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`.
|
|
30
32
|
|
|
31
|
-
The first time
|
|
33
|
+
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: build-and-update unless the person ticked full access on the approval page. Revoke them on the Connect an agent page at app.wirl.dev if an agent should lose access.
|
|
32
34
|
|
|
33
35
|
## Tools
|
|
34
36
|
|