agent402-mcp 0.7.0 → 0.7.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 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,6 +45,20 @@ Claude Code: `claude mcp add agent402 -- npx -y agent402-mcp`
|
|
|
45
45
|
- When a call hits HTTP 402: with `AGENT_KEY` set, the server signs an x402 USDC payment and retries; without a key it solves the tool's proof-of-work challenge (~0.2 s of CPU) on the eligible tools.
|
|
46
46
|
- `payment_info` tells the model which mode it's in and what a wallet would unlock.
|
|
47
47
|
|
|
48
|
+
## Workflows (skill packs)
|
|
49
|
+
|
|
50
|
+
For jobs that no single tool covers (e.g. "audit a domain", "build a stock
|
|
51
|
+
brief"), Agent402 ships curated multi-tool **skill packs**. They're surfaced
|
|
52
|
+
as standard MCP **prompts**, so any MCP-aware client picks them up
|
|
53
|
+
automatically:
|
|
54
|
+
|
|
55
|
+
- `prompts/list` returns each pack with typed arguments.
|
|
56
|
+
- `prompts/get { name: "<slug>", arguments: { … } }` returns the rendered
|
|
57
|
+
task template — a Claude-ready plan with the chosen tools wired in.
|
|
58
|
+
- `search_tools` also surfaces matching workflows alongside individual tools,
|
|
59
|
+
so a task-shaped query points the agent at the right plan, not just the
|
|
60
|
+
raw tools.
|
|
61
|
+
|
|
48
62
|
## Configuration
|
|
49
63
|
|
|
50
64
|
| env | default | meaning |
|