@wervt/cli 0.2.19 → 0.2.20

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skill/SKILL.md +11 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wervt/cli",
3
- "version": "0.2.19",
3
+ "version": "0.2.20",
4
4
  "description": "Deploy and manage apps on wervt.",
5
5
  "keywords": [
6
6
  "agents",
package/skill/SKILL.md CHANGED
@@ -23,6 +23,17 @@ approve it in the dashboard (CLI page) and the machine gets its own admin sessio
23
23
  login for them, never look for tokens in files, env or keychains, and never print or ask to paste
24
24
  one into the chat.
25
25
 
26
+ Where the user can't run the login (a cloud sandbox like Claude Code on the web), use wervt's MCP
27
+ servers instead, if they're connected. They act as the user:
28
+
29
+ - The dashboard's (`whoami`, `apps.list`, `logs.query`, `env.update`, …) manages deployed apps:
30
+ everything below except building and deploying.
31
+ - build's (`create-app`, `edit-file`, `run`, `deploy`, …) builds and deploys apps in a cloud
32
+ sandbox, without this machine.
33
+
34
+ Not connected: ask the user to add `https://dashboard.<domain>/mcp` (and, to build,
35
+ `https://build.<domain>/mcp`) as MCP servers.
36
+
26
37
  ## 2. Scaffold
27
38
 
28
39
  ```bash