@awesomate/hosting-mcp 0.140.1 → 0.151.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 +31 -0
- package/dist/index.js +2780 -2408
- package/package.json +2 -2
- package/skill/CHANGELOG.json +99 -0
- package/skill/awesomate-email/SKILL.md +22 -2
- package/skill/awesomate-funnels/SKILL.md +18 -10
- package/skill/awesomate-funnels/references/lead-magnet.md +6 -4
- package/skill/awesomate-funnels/references/webinar.md +142 -0
- package/skill/awesomate-knowledge/SKILL.md +3 -3
- package/skill/awesomate-knowledge/references/faqs.md +1 -1
- package/skill/awesomate-knowledge/references/from-your-files.md +2 -2
- package/skill/awesomate-knowledge/references/ingestion-sources.md +3 -1
- package/skill/awesomate-knowledge/references/quotas-and-packs.md +1 -1
package/README.md
CHANGED
|
@@ -73,5 +73,36 @@ A change to `src/` or `skill/` needs a new version and a `skill/CHANGELOG.json`
|
|
|
73
73
|
entry at the top, and a new tool needs a place in `docs/reference.json` and,
|
|
74
74
|
where it changes what someone can ask for, a line in the right guide under `docs/`.
|
|
75
75
|
|
|
76
|
+
`test/tools-list.snapshot.json` is what the built server's `tools/list`, resource
|
|
77
|
+
list and prompt list return, byte for byte (each sorted by name), and `npm test`
|
|
78
|
+
fails when it differs. A change meant to show (a new tool, a new argument, new
|
|
79
|
+
wording) refreshes it in the same PR with
|
|
80
|
+
`npm run build && node scripts/tools-list-snapshot.mjs --write`; a change that
|
|
81
|
+
only moves code must leave it as it is. The snapshot also records what the MCP SDK
|
|
82
|
+
adds to each tool, so a lockfile bump that changes it refreshes the snapshot too.
|
|
83
|
+
|
|
84
|
+
### Where a tool is registered
|
|
85
|
+
|
|
86
|
+
Tools are moving out of `src/index.ts` into a shared registry, one group at a
|
|
87
|
+
time, so the same tools can later serve Claude chat as well as this npx server
|
|
88
|
+
(remote-mcp plan, Part B). `src/tools/groups.json` names every tool's group and
|
|
89
|
+
the surfaces that offer it; a new tool needs a line there or `npm test` fails.
|
|
90
|
+
|
|
91
|
+
- A group that has moved lives in `src/tools/<group>.ts`, inside
|
|
92
|
+
`register<Group>(r)`. Register through `r`: `r.registerTool`, `r.readTool`,
|
|
93
|
+
`r.registerResource`, and `r.config()` for the account (never
|
|
94
|
+
`requireConfig()`, which only index.ts has).
|
|
95
|
+
- A group that has not moved yet is still registered in `src/index.ts`.
|
|
96
|
+
- Titles, the annotation kinds and the result shapes (`TITLES`, `annotate`,
|
|
97
|
+
`READ_ONLY`, `textResult`, `errorResult` and the rest) are in `src/tools/kit.ts`.
|
|
98
|
+
- `whoami`, `get_context`, `skill_update` and `design_system_package` stay in
|
|
99
|
+
index.ts (group `host`): they read the credentials file and the installed
|
|
100
|
+
skills, or write files on the user's machine, which only the npx server can.
|
|
101
|
+
|
|
102
|
+
A group moves with `node scripts/registry-slice.mjs --group <group>`, which
|
|
103
|
+
moves the code verbatim and checks it reads back byte for byte. Each move is
|
|
104
|
+
merged inside an announced hold on `src/index.ts`; `--check` proves the
|
|
105
|
+
committed move is exactly the script's output on fresh main.
|
|
106
|
+
|
|
76
107
|
Publishing is CI-only: any `mcp/**` change merged to main with a bumped
|
|
77
108
|
version publishes via `publish-mcp.yml`. Never `npm publish` by hand.
|