@wirl/mcp 0.0.0-stage → 0.2.0
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 +42 -2
- package/bin.js +8120 -0
- package/package.json +37 -4
package/README.md
CHANGED
|
@@ -1,3 +1,43 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @wirl/mcp
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
The wirl MCP server, run locally. It lets a coding agent deploy what it just built to wirl, share it with a named colleague, pull a deployed app's source, list versions and roll back.
|
|
4
|
+
|
|
5
|
+
## Prefer the hosted server
|
|
6
|
+
|
|
7
|
+
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:
|
|
8
|
+
|
|
9
|
+
```bash
|
|
10
|
+
claude mcp add --transport http wirl https://app.wirl.dev/mcp
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
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.
|
|
14
|
+
|
|
15
|
+
## Running it locally
|
|
16
|
+
|
|
17
|
+
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:
|
|
18
|
+
|
|
19
|
+
```bash
|
|
20
|
+
claude mcp add wirl -- npx -y https://app.wirl.dev/cli/wirl-mcp.tgz
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
Cursor and anything else that speaks MCP take the same command in their own configuration:
|
|
24
|
+
|
|
25
|
+
```json
|
|
26
|
+
{ "mcpServers": { "wirl": { "command": "npx", "args": ["-y", "https://app.wirl.dev/cli/wirl-mcp.tgz"] } } }
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
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.
|
|
30
|
+
|
|
31
|
+
## Tools
|
|
32
|
+
|
|
33
|
+
`wirl_deploy`, `wirl_preview`, `wirl_preview_fetch`, `wirl_list_previews`, `wirl_delete_preview`, `wirl_delete_app`, `wirl_logs`, `wirl_egress`, `wirl_share`, `wirl_pull`, `wirl_list_apps`, `wirl_list_versions`, `wirl_rollback`, `wirl_list_schedules`, `wirl_run`, `wirl_list_connections`, `wirl_whoami`, and `wirl_login` (local only). No app files pass through the model: deploy reads the directory the agent names. If `wirl.json` declares `public_paths`, `wirl_deploy` hands back the exact URL to paste into Slack, Stripe or GitHub's dashboard.
|
|
34
|
+
|
|
35
|
+
## Keys never pass through the agent
|
|
36
|
+
|
|
37
|
+
An app that needs a third-party API declares the connection in `wirl.json`. If the key is missing, the deploy hands back a link to the app's keys page; the person adds the key in their own browser and it goes straight into wirl's vault.
|
|
38
|
+
|
|
39
|
+
## Requirements
|
|
40
|
+
|
|
41
|
+
Node 20 or later. Docs: https://docs.wirl.dev. Site: https://wirl.dev. Issues: https://github.com/Brycce/wirl-platform/issues.
|
|
42
|
+
|
|
43
|
+
wirl is a hosted service; use of this server is governed by the terms at https://wirl.dev/terms.
|