@viberaven/mcp 1.0.0 → 1.0.1
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 +14 -14
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -4,7 +4,7 @@ Thin MCP wrapper for VibeRaven.
|
|
|
4
4
|
|
|
5
5
|
This package exposes VibeRaven CLI actions as MCP tools for Codex, Claude Code, Cursor, and other agent runtimes. It does not contain VibeRaven backend logic and does not bypass VibeRaven login or scan quotas.
|
|
6
6
|
|
|
7
|
-
The MCP server wraps the stable CLI package: `npx -y
|
|
7
|
+
The MCP server wraps the stable CLI package: `npx -y viberaven`.
|
|
8
8
|
|
|
9
9
|
## Run
|
|
10
10
|
|
|
@@ -15,29 +15,29 @@ npx -y @viberaven/mcp
|
|
|
15
15
|
You can also start the MCP server from the main CLI package:
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
|
-
npx -y
|
|
18
|
+
npx -y viberaven mcp
|
|
19
19
|
```
|
|
20
20
|
|
|
21
21
|
## Tools
|
|
22
22
|
|
|
23
|
-
- `viberaven_check_readiness` -> `npx -y
|
|
24
|
-
- `viberaven_verify` -> `npx -y
|
|
25
|
-
- `viberaven_audit` -> `npx -y
|
|
26
|
-
- `viberaven_init_rules` -> `npx -y
|
|
27
|
-
- `viberaven_clean_plan` -> `npx -y
|
|
28
|
-
- `viberaven_strict_gate` -> `npx -y
|
|
29
|
-
- `viberaven_gate_result` -> `npx -y
|
|
30
|
-
- `viberaven_context_map` -> `npx -y
|
|
31
|
-
- `viberaven_heal_plan` -> `npx -y
|
|
32
|
-
- `viberaven_heal_prompt` -> `npx -y
|
|
33
|
-
- `viberaven_heal_apply` -> `npx -y
|
|
23
|
+
- `viberaven_check_readiness` -> `npx -y viberaven --agent-mode`
|
|
24
|
+
- `viberaven_verify` -> `npx -y viberaven --verify`
|
|
25
|
+
- `viberaven_audit` -> `npx -y viberaven audit --vercel-supabase`
|
|
26
|
+
- `viberaven_init_rules` -> `npx -y viberaven init`
|
|
27
|
+
- `viberaven_clean_plan` -> `npx -y viberaven clean --plan`
|
|
28
|
+
- `viberaven_strict_gate` -> `npx -y viberaven --agent-mode --strict --json`
|
|
29
|
+
- `viberaven_gate_result` -> `npx -y viberaven --agent-mode --json`
|
|
30
|
+
- `viberaven_context_map` -> `npx -y viberaven --condense`
|
|
31
|
+
- `viberaven_heal_plan` -> `npx -y viberaven --heal --plan`
|
|
32
|
+
- `viberaven_heal_prompt` -> `npx -y viberaven --heal --prompt`
|
|
33
|
+
- `viberaven_heal_apply` -> `npx -y viberaven --heal --apply`
|
|
34
34
|
|
|
35
35
|
`viberaven_check_readiness` is the canonical entrypoint. It runs VibeRaven as the Agent Context + Production Gate and writes `.viberaven/agent-tasklist.md`, `.viberaven/gate-result.json`, and `.viberaven/context-map.json`.
|
|
36
36
|
|
|
37
37
|
After one fix, call `viberaven_verify`. Before deploy or CI pass, call `viberaven_strict_gate` or run:
|
|
38
38
|
|
|
39
39
|
```bash
|
|
40
|
-
npx -y
|
|
40
|
+
npx -y viberaven --strict
|
|
41
41
|
```
|
|
42
42
|
|
|
43
43
|
## Machine Artifact Contract
|
package/package.json
CHANGED
|
@@ -1,9 +1,10 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@viberaven/mcp",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"description": "Thin MCP wrapper around the VibeRaven CLI for agent launch-readiness workflows.",
|
|
5
5
|
"license": "UNLICENSED",
|
|
6
6
|
"author": "VibeRaven",
|
|
7
|
+
"mcpName": "io.github.ohad6k/viberaven",
|
|
7
8
|
"homepage": "https://viberaven.dev/mcp.md",
|
|
8
9
|
"repository": {
|
|
9
10
|
"type": "git",
|