l8bin-mcp 0.4.6 → 0.4.8
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 +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -41,9 +41,9 @@ to point at a specific binary.
|
|
|
41
41
|
client. Don't have a LiteBin server yet? One command on any VPS with Docker:
|
|
42
42
|
`curl -fsSL https://l8b.in | bash` ([quickstart](https://l8bin.com/quickstart))
|
|
43
43
|
2. **Call the `setup` tool** with no arguments and follow its `state` + `next`:
|
|
44
|
-
give it your server URL, open the `approval_url` it
|
|
45
|
-
dashboard (you pick the token scope), then call it
|
|
46
|
-
`complete: true`. Auth is stored and the workspace `l8b.toml` is bound —
|
|
44
|
+
give it your server URL (the dashboard address), open the `approval_url` it
|
|
45
|
+
returns, approve in the dashboard (you pick the token scope), then call it
|
|
46
|
+
again with `complete: true`. Auth is stored and the workspace `l8b.toml` is bound —
|
|
47
47
|
no CLI install, no terminal login. Manual alternative:
|
|
48
48
|
`l8b login --server https://your-l8bin.example.com --pair`.
|
|
49
49
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "l8bin-mcp",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.8",
|
|
4
4
|
"description": "l8bin (pronounced LiteBin) MCP server — deploy and operate your self-hosted projects from any MCP client. Wraps the l8b CLI, installing the platform binary on first use.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|