@icoretech/warden-mcp 0.1.2 → 0.1.4
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 +22 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,7 @@
|
|
|
1
1
|
# warden-mcp
|
|
2
2
|
|
|
3
3
|
[](https://www.npmjs.com/package/@icoretech/warden-mcp)
|
|
4
|
+
[](https://ghcr.io/icoretech/warden-mcp)
|
|
4
5
|
[](https://github.com/icoretech/warden-mcp/actions/workflows/ci.yml)
|
|
5
6
|
[](LICENSE)
|
|
6
7
|
|
|
@@ -18,6 +19,21 @@ Published package: [`@icoretech/warden-mcp`](https://www.npmjs.com/package/@icor
|
|
|
18
19
|
- Attachments: create/delete/download
|
|
19
20
|
- Organization + collection helpers (list + org-collection CRUD)
|
|
20
21
|
- Safe-by-default: item reads are **redacted** unless explicitly revealed; secret helper tools return `null` unless `reveal: true`
|
|
22
|
+
- Strong fit for LLM automation: pair it with a browser-capable MCP host so an agent can fetch credentials, complete sign-in flows, read TOTP codes, and keep automating after login
|
|
23
|
+
|
|
24
|
+
## LLM Automation Use Case
|
|
25
|
+
|
|
26
|
+
`warden-mcp` is not only useful for vault administration. A very practical use case is pairing it with an LLM that can also drive a browser.
|
|
27
|
+
|
|
28
|
+
That lets the agent do end-to-end authenticated workflows such as:
|
|
29
|
+
|
|
30
|
+
- open a site or backoffice in the browser
|
|
31
|
+
- read the right login from Vaultwarden or Bitwarden
|
|
32
|
+
- fill username and password without hardcoding secrets in prompts or config
|
|
33
|
+
- retrieve a current TOTP code with `keychain.get_totp` for TOTP-based MFA
|
|
34
|
+
- continue the real task after login, such as navigation, data entry, exports, or routine admin work
|
|
35
|
+
|
|
36
|
+
In practice, this is what makes the server useful for full automation, not just secret lookup. The same MCP session that gives the model browser control can also give it scoped access to the credentials and MFA material needed to finish the workflow.
|
|
21
37
|
|
|
22
38
|
## Runtime Requirement
|
|
23
39
|
|
|
@@ -96,6 +112,12 @@ This mode is what makes `warden-mcp` different from a simple local wrapper:
|
|
|
96
112
|
- one running server can front different vault hosts or different identities without restarting
|
|
97
113
|
- it fits shared-agent and gateway setups much better than per-client local processes
|
|
98
114
|
|
|
115
|
+
### Docker
|
|
116
|
+
|
|
117
|
+
```bash
|
|
118
|
+
docker run --rm -p 3005:3005 ghcr.io/icoretech/warden-mcp
|
|
119
|
+
```
|
|
120
|
+
|
|
99
121
|
### Global install
|
|
100
122
|
|
|
101
123
|
```bash
|