mcp-scraper 0.28.2 → 0.29.0

package/dist/bin/mcp-stdio-server.js

@@ -7,7 +7,7 @@ import {
   registerMemoryMcpTools,
   registerPaaExtractorMcpTools,
   registerSerpIntelligenceCaptureTools
-} from "../chunk-Q7VZUYRR.js";
+} from "../chunk-66SYKL2G.js";
 import "../chunk-R7EETU7Z.js";
 import "../chunk-MTSBI7ZH.js";
 import {
@@ -16,7 +16,7 @@ import {
 import "../chunk-ZQSHKWV4.js";
 import {
   PACKAGE_VERSION
-} from "../chunk-GOAQIV6K.js";
+} from "../chunk-7TNTBRQW.js";
 import "../chunk-4767BA2O.js";
 import "../chunk-M2S27J6Z.js";
 import "../chunk-ICT7DDHL.js";

package/dist/{chunk-Q7VZUYRR.js → chunk-66SYKL2G.js}

@@ -19,7 +19,7 @@ import {
 } from "./chunk-ZQSHKWV4.js";
 import {
   PACKAGE_VERSION
-} from "./chunk-GOAQIV6K.js";
+} from "./chunk-7TNTBRQW.js";
 import {
   MC_PER_CREDIT
 } from "./chunk-4767BA2O.js";
@@ -401,12 +401,14 @@ Multi-step orchestrations \u2014 prefer these over hand-chaining primitives when
 
 ## Memory
 mcp-scraper also exposes persistent per-user memory tools (notes, facts, vaults,
-scheduled actions, tables, channels) backed by memory.mcpscraper.dev. Every account starts with 14
+scheduled actions, tables, channels) backed by memory.mcpscraper.dev. Every account starts with 15
 vaults \u2014 call **list-vaults** to see what exists before creating anything new. Pick the vault whose job
 matches the content: **Ideas** (unvalidated concepts), **Knowledge** (distilled lessons/how-tos),
 **Library** (raw source material \u2014 articles, transcripts), **People** (one durable note per person/org),
-**Communications** (individual conversation records), **Calendar** (time-anchored entries), **Tasks**
-(action items with a status), **Projects** (durable named initiatives), **Issues** (something broken),
+**Deals** (commercial opportunities tied to a known person or organization), **Communications** (individual
+conversation records and drafts), **Calendar** (time-anchored entries), **Tasks** (action items linked to a
+known Project), **Projects** (only codebases, known client projects, personal projects, or ongoing siloed
+workstreams), **Issues** (something broken),
 **Improvement Log** (receipts of changes made and whether they worked), **Experiments** (hypothesis +
 measured result), **Sprint** (current cycle's scope), **Inspiration** (other people's work worth
 studying), **Skills** (reusable skill packages; each requires \`scripts/\` and at least one of
@@ -420,6 +422,14 @@ deliberate edits and migrations. Use
 they'll filter/sort by exact value. **memory-search** is meaning-based over full content (embeds, slower);
 **memory-list** filters one vault by kind/tags (fast, exact).
 
+For People, Deals, Projects, Tasks, and Communications, use the returned contract rather than guessing:
+People only holds a real person or organization hub; Deals need a known party; Projects need
+\`project_kind\`; every Task needs a verified \`project_ref\` and matching project name; and email drafts
+awaiting human review need \`direction:"draft"\` with \`approval_state:"pending"\`. Link a known person,
+project, deal, or communication when verified. If a required relationship is not clear, ask the user rather
+than creating a free-floating record. Overview is the review queue: editing leaves a draft pending, and
+approval or denial records a state only\u2014it does not send email.
+
 Treat every memory create or update as a graph operation. **prepare-memory-write** supplies the initial
 shortlist; use **memory-search** when it is weak or the topic is broad, and **memory-get** to read the best
 candidates in full. Add only links supported by the notes: same-
@@ -8165,7 +8175,7 @@ var memoryCaptureTool_notePropsSchema = z3.object({
 var MemoryCaptureSchema = {
   id: "memory-capture",
   upstreamName: "memoryCaptureTool",
-  description: "Strict normal-create path for durable memory. Before capture, list the complete tag vocabulary, call prepare-memory-write, run hybrid memory-search for related notes, and read the strongest link candidates. This tool refuses incomplete notes, writes through memory-put, registers canonical tags, and verifies persisted content and props. Reserve memory-put for low-level migrations or deliberate edits.",
+  description: "Strict normal-create path for durable memory. Before capture, list the complete tag vocabulary, call prepare-memory-write, run hybrid memory-search for related notes, and read the strongest link candidates. This tool refuses incomplete notes and invalid relationship-domain writes: projects need a project kind, tasks need a verified project, deals need a known party, and draft emails need a pending approval state. It writes through memory-put, registers canonical tags, and verifies persisted content and props. Reserve memory-put for low-level migrations or deliberate edits.",
   input: {
     vault: z3.string(),
     folder: z3.string().optional(),
@@ -8223,7 +8233,7 @@ var MemoryQuestionsSchema = {
 var PrepareMemoryWriteSchema = {
   id: "prepare-memory-write",
   upstreamName: "prepareMemoryWriteTool",
-  description: "Mandatory planning pass for a normal new memory. First inspect the complete tag vocabulary with list-memory-tags; then this pass routes the note, returns the live template and natural vault relationships, resolves proposed tags, and shortlists interlinks. Use hybrid memory-search (3 focused queries, 50 fused candidates, bounded graph expansion, rerank to 30 by default) and read strong related notes before capture. This is an explicit AI workflow directive, not a claim of persisted call-order enforcement.",
+  description: "Mandatory planning pass for a normal new memory. First inspect the complete tag vocabulary with list-memory-tags; then this pass routes the note, returns the live template and natural vault relationships, resolves proposed tags, and shortlists interlinks. For People, Deals, Projects, Tasks, and Communications, it also returns required relationship and approval guidance: search existing records first and ask rather than inventing a missing project or party. Use hybrid memory-search (3 focused queries, 50 fused candidates, bounded graph expansion, rerank to 30 by default) and read strong related notes before capture. This is an explicit AI workflow directive, not a claim of persisted call-order enforcement.",
   input: {
     title: z3.string().min(1),
     content: z3.string().min(1),
@@ -8930,10 +8940,10 @@ var putTool_notePropsSchema = z3.object({
 var PutSchema = {
   id: "memory-put",
   upstreamName: "putTool",
-  description: "Create or edit one note at a path in a memory vault; content is persisted and indexed for search. For row-shaped datasets you'll filter/sort by exact value, use table-create/table-insert-rows/table-query instead. Ordinary vaults are indexed and shareable \u2014 never store real secrets there; use a secure vault (create-secure-vault) instead, which is never indexed or shareable and is encrypted at rest. Requires write scope.",
+  description: "Create or deliberately edit one note at a path in a memory vault; content is persisted and indexed for search. For normal new People, Deals, Projects, Tasks, or Communications records, use prepare-memory-write then memory-capture: People must be real people or organizations, Deals need a known party, Projects need a supported kind, Tasks need a verified Project, and draft emails need pending approval. For row-shaped datasets you'll filter/sort by exact value, use table-create/table-insert-rows/table-query instead. Ordinary vaults are indexed and shareable \u2014 never store real secrets there; use a secure vault (create-secure-vault) instead, which is never indexed or shareable and is encrypted at rest. Requires write scope.",
   input: {
     vault: z3.string().optional().describe(
-      "Vault to write to. Optional; defaults to the session active vault, then the first vault the caller is entitled to. On a default-provisioned account, pick the vault whose job matches the content (see the server instructions for the full 13-vault guide) rather than defaulting blindly \u2014 e.g. a lesson learned goes in Knowledge, the raw source it came from goes in Library, a broken feature goes in Issues, a named real-world initiative goes in Projects."
+      "Vault to write to. Optional; defaults to the session active vault, then the first vault the caller is entitled to. On a default-provisioned account, pick the vault whose job matches the content (see the server instructions for the full 15-vault guide) rather than defaulting blindly \u2014 e.g. a lesson learned goes in Knowledge, the raw source it came from goes in Library, a broken feature goes in Issues, a named real-world initiative goes in Projects. Do not use this low-level tool to create ordinary People, Deals, Projects, Tasks, or Communications records: first use prepare-memory-write then memory-capture so relationships and approval state are validated."
     ),
     path: z3.string().optional().describe("Vault-relative note path to create or overwrite, e.g. projects/q3-plan. Writing an existing path replaces it. Required unless shareId is given."),
     shareId: z3.string().optional().describe("Edit a note someone individually shared with you and you accepted (accept-share), by its shareId, instead of vault+path. Requires the share to grant edit permission, and baseRevision is mandatory (get the current revision first) since you are editing alongside the owner and possibly others."),
@@ -9720,9 +9730,9 @@ var DeleteVaultSchema = {
 var GetVaultContractSchema = {
   id: "get-vault-contract",
   upstreamName: "getVaultContractTool",
-  description: "Read the machine-enforced purpose, template, statuses, types, natural neighbor vaults, and typed relationship guidance for one of the 13 governed Obsidian-style vaults. Call before composing a note when the correct shape is uncertain.",
+  description: "Read the machine-enforced purpose, template, statuses, types, natural neighbor vaults, and typed relationship guidance for one of the 15 governed Obsidian-style vaults. Call before composing a note when the correct shape is uncertain.",
   input: {
-    vault: z3.string().describe("One governed vault: Ideas, Inspiration, Knowledge, Library, People, Communications, Calendar, Tasks, Projects, Issues, Improvement Log, Experiments, or Sprint.")
+    vault: z3.string().describe("One governed vault: Ideas, Inspiration, Knowledge, Library, People, Deals, Communications, Calendar, Tasks, Projects, Issues, Improvement Log, Experiments, Sprint, or Skills.")
   },
   output: {
     ok: z3.boolean(),
@@ -9792,17 +9802,17 @@ var ListVaultsSchema = {
 var ProvisionDefaultsSchema = {
   id: "provision-defaults",
   upstreamName: "provisionDefaultsTool",
-  description: "Provision the standard 14-vault memory structure (Ideas, Inspiration, Knowledge, Library, People, Communications, Calendar, Tasks, Projects, Issues, Improvement Log, Experiments, Sprint, Skills) for an identity. Idempotent \u2014 existing vaults are untouched. Optionally issues a fresh API key entitled to all 14. Requires admin scope.",
+  description: "Provision the standard 15-vault memory structure (Ideas, Inspiration, Knowledge, Library, People, Deals, Communications, Calendar, Tasks, Projects, Issues, Improvement Log, Experiments, Sprint, Skills) for an identity. Idempotent \u2014 existing records are untouched and existing vault contracts are refreshed. Optionally issues a fresh API key entitled to all 15. Requires admin scope.",
   input: {
-    granteeIdentity: z3.string().min(1).describe("Identity that should OWN the 14 default vaults (e.g. an email or user id)."),
-    issueKey: z3.boolean().optional().describe("When true, also issue a new API key for the identity entitled to all 14 vaults and return its secret once. Default false."),
+    granteeIdentity: z3.string().min(1).describe("Identity that should OWN the 15 default vaults (e.g. an email or user id)."),
+    issueKey: z3.boolean().optional().describe("When true, also issue a new API key for the identity entitled to all 15 vaults and return its secret once. Default false."),
     plan: z3.enum(["free", "pro", "team", "enterprise"]).optional().describe("Subscription plan carried by the issued key. Optional; defaults to free. Only used when issueKey is true.")
   },
   output: {
     ok: z3.boolean().describe("True when provisioning succeeded; false on auth/scope error."),
     identity: z3.string().optional().describe("Identity the vaults were provisioned for."),
-    created: z3.array(z3.string()).optional().describe("Vault names newly created on this call (empty when all 14 already existed)."),
-    vaults: z3.array(z3.string()).optional().describe("All 14 default vault names the identity now owns."),
+    created: z3.array(z3.string()).optional().describe("Vault names newly created on this call (empty when all 15 already existed)."),
+    vaults: z3.array(z3.string()).optional().describe("All 15 default vault names the identity now owns."),
     keyId: z3.string().optional().describe("Stable id of the issued key. Present only when issueKey was true."),
     secret: z3.string().optional().describe("The issued key secret \u2014 RETURNED ONCE. Present only when issueKey was true."),
     plan: z3.string().optional().describe("Plan assigned to the issued key. Present only when issueKey was true."),
@@ -10069,4 +10079,4 @@ export {
   MEMORY_TOOL_SCHEMAS,
   registerMemoryMcpTools
 };
-//# sourceMappingURL=chunk-Q7VZUYRR.js.map
+//# sourceMappingURL=chunk-66SYKL2G.js.map