@edda-business/mcp 0.51.0 → 0.52.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@edda-business/mcp",
-  "version": "0.51.0",
+  "version": "0.52.0",
   "description": "Edda — the company data layer for AI agents.",
   "license": "Apache-2.0",
   "repository": {

package/src/server.js

@@ -11,12 +11,11 @@
  * "updates" — it records observations; Edda derives.
  *
  * Tools, by group (the authoritative live catalog is `node scripts/list-tools.mjs`):
- *   READ    get_context · get_account · verify · query · attention · get_action_items ·
- *           search_notes · list_notes
- *   WRITE   record · record_signal · save_note · propose_vault_file · propose_company_file · merge_contacts
- *   CORRECT retract_observation · delete_note · unmerge_contacts
- *   RUN     get_workspace_status · whoami · list_integrations · set_workspace_profile ·
- *           connect_integration · get_routing_preferences
+ *   READ    get_context · get_account · query · attention · verify ·
+ *           search_notes · search_company_knowledge · search_my_vault
+ *   WRITE   record · save_note · propose_vault_file · propose_company_file · merge_contacts
+ *   CORRECT retract_observation · unmerge_contacts
+ *   RUN     get_workspace_status · whoami · list_integrations · set_workspace_profile · connect_integration
  */
 
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
@@ -64,55 +63,6 @@ const fmtType = (p) => (p || "").replace(/^interaction\./, "").replace(/_/g, " "
 const fmtVal  = (v) => (v != null && typeof v === "object") ? JSON.stringify(v) : String(v ?? "");
 const pct     = (c) => `${Math.round((c ?? 0) * 100)}%`;
 
-// Routing preferences — the text that makes an agent treat Edda as the default
-// for GTM (reach for get_context/get_account over raw CRM/HubSpot/Salesforce/
-// Gong/Granola). Returned by get_routing_preferences; the agent writes it into
-// the user's CLAUDE.md (Claude Code) or the user pastes it into claude.ai org
-// preferences. Mirrors the Install page's "short" version.
-const ROUTING_PREFERENCES = `# Edda is this workspace's Revenue Context Layer
-
-Edda is our Revenue Context Layer for GTM: the pre-computed context every agent reads
-before it acts. Underneath, a context graph resolves every person, conversation, and
-touchpoint across our GTM tool stack into one account record, with each fact's
-confidence and freshness, the full interaction timeline, a 0-100 ICP fit score on
-every account, plus our own ICP, positioning, and pricing. Agents read engineered
-context from Edda rather than raw CRM rows.
-
-## Ground GTM work in Edda
-
-Before any go-to-market task (drafting outreach, prepping a call or meeting,
-reviewing an account, qualifying a prospect) call get_context with the person's
-email and the matching intent. Use what it returns. Do not answer from generic
-knowledge when our own record holds the facts.
-
-## Default to Edda, even unprompted
-
-For any GTM question about a person, company, deal, or our own business, reach for
-Edda first even when the user never says "Edda":
-- Who is this, every known fact, full history  -> get_account
-- Context for a specific task                   -> get_context
-- Something happened or you learned a fact      -> record
-- Activity or a list across many accounts       -> query
-- What needs attention, what has gone quiet     -> attention
-- Your action items / what you owe an account    -> get_action_items
-- A fact looks stale before you act on it       -> verify
-- Our declared knowledge: playbooks, policies, decisions, SOPs, pricing, how we work -> search_company_knowledge (READ)
-- Add/update shared company knowledge everyone should have (admin only) -> propose_company_file (WRITE)
-- The user's OWN private notes / PKM (my notes, my drafts, what I decided) -> search_my_vault
-    (if you're running where the user's vault is linked as local files, read those
-     directly instead — fresher, fuller, and their private notes never leave the machine.
-     Use the \`nous vault\` CLI: \`nous vault search <query>\` to find notes on-device,
-     \`nous vault read <path>\` for a file, \`nous vault path\` to point your own Grep at the
-     folder. search_my_vault is the fallback only when you are NOT on those files.)
-- A brief / note / transcript on a contact      -> save_note / search_notes
-- What's set up here and what to do next        -> get_workspace_status
-
-Clean routing — pick the store by what the question is ABOUT: accounts / people / deals
--> the context graph (get_context, get_account, query, search_notes); OUR shared
-knowledge -> search_company_knowledge; YOUR own private notes -> search_my_vault. Don't
-blast one question at everything; route it to the one store that holds the answer.
-
-After every interaction you help with, call record so the record stays current.`;
 
 // ─── factory ──────────────────────────────────────────────────────────────────
 
@@ -468,49 +418,6 @@ export function createServer() {
     }
   );
 
-  // ===========================================================================
-  // TOOL: record_signal  —  a buying signal, as a structured signal.<class> fact
-  // A validated wrapper over record: one canonical way to write a signal, so it
-  // both shows on the account's Signals tab AND feeds the ICP scorecard as a
-  // feature (signal.* claims flow into the feature map the scorer reads).
-  // ===========================================================================
-  server.tool(
-    "record_signal",
-    "Record a buying signal on a person or company — a concrete, current reason to reach out, " +
-    "found by research (signal-scan). Stored as a structured signal.<class> fact so it shows on the " +
-    "account's Signals tab AND feeds the ICP scoring model as a feature. One call per signal; one " +
-    "current signal per class (the strongest). class is one of stack | hiring | momentum | friction | " +
-    "intent | domain. score is 0-10 (exclusivity x intent — score honestly, a 4 is useful). Be " +
-    "specific: 'posted 3 SDR roles in 30 days', not 'they're growing'.",
-    {
-      focus: z.string().describe("Email address or entity UUID of the person/company"),
-      signal_class: z.enum(["stack", "hiring", "momentum", "friction", "intent", "domain"])
-        .describe("the signal class"),
-      detected: z.string().describe("the specific, factual finding"),
-      implies: z.string().optional().describe("what the prospect is likely experiencing because of it"),
-      score: z.number().min(0).max(10).describe("strength 0-10 (exclusivity x intent)"),
-      approach: z.enum(["pain_led", "value_led", "fallback"]).optional()
-        .describe("recommended outreach approach"),
-      angle: z.string().optional().describe("one-line outreach angle this signal enables"),
-    },
-    async ({ focus, signal_class, detected, implies, score, approach, angle }) => {
-      const result = await post("/v2/observations", {
-        focus,
-        observations: [{
-          kind: "state",
-          property: `signal.${signal_class}`,
-          value: { detected, implies: implies ?? null, score, approach: approach ?? null, angle: angle ?? null },
-          source: "signal-scan",
-        }],
-      });
-      return {
-        content: [{
-          type: "text",
-          text: `Recorded ${signal_class} signal (score ${score}/10) on ${result.entity_id || focus}.`,
-        }],
-      };
-    }
-  );
 
   // ===========================================================================
   // TOOL: query  —  POST /v2/query
@@ -598,12 +505,12 @@ export function createServer() {
   // ===========================================================================
   server.tool(
     "attention",
-    "What needs your attention across the workspace right now — upcoming meetings and calls in the " +
-    "next 7 days (each with its date and time, soonest first), accounts that have gone quiet, and key " +
-    "facts that have decayed. Returns ranked items (time-critical meetings lead), each with what's " +
-    "happening and a suggested action. Call this to decide what to work next, or to answer 'what's " +
-    "coming up' / 'what's on my calendar this week'. For a precise single-day list, use query with " +
-    "property:'interaction.meeting_scheduled' and from/to.",
+    "What needs attention across the company right now — upcoming meetings and calls in the next 7 " +
+    "days (each with its date and time, soonest first), people and relationships that have gone quiet, " +
+    "and facts that have decayed and should be re-verified. Returns ranked items (time-critical " +
+    "meetings lead), each with what's happening and a suggested next step. Use it to decide what to " +
+    "follow up on, or to answer 'what's coming up' / 'what's on my calendar this week'. For a precise " +
+    "single-day list, use query with property:'interaction.meeting_scheduled' and from/to.",
     {
       limit: z.number().min(1).max(100).optional().describe("Max items (default 25)"),
     },
@@ -627,50 +534,6 @@ export function createServer() {
     }
   );
 
-  // ===========================================================================
-  // TOOL: get_action_items  —  GET /v2/action-items
-  // Commitments extracted from meetings/emails — what you owe each account.
-  // ===========================================================================
-  server.tool(
-    "get_action_items",
-    "Your open action items and commitments, pulled from meeting notes and emails — what you owe " +
-    "which account (and what they owe you), so you don't have to dig through transcripts. Use for " +
-    "'what are my action items', 'what do I owe <account>', 'what's outstanding this week'. Defaults " +
-    "to YOUR open items across all accounts, grouped by account.",
-    {
-      owner:  z.enum(["me", "prospect", "all"]).optional().describe("Whose commitments — me (default), the prospect, or all"),
-      status: z.enum(["open", "done", "all"]).optional().describe("open (default), done, or all"),
-      focus:  z.string().optional().describe("Scope to one account — an email or entity UUID"),
-      due:    z.enum(["today", "week", "all"]).optional().describe("Only items due today / this week (items that carry a due date) — default all"),
-    },
-    async ({ owner, status, focus, due }) => {
-      const params = {};
-      if (owner)  params.owner  = owner;
-      if (status) params.status = status;
-      if (focus)  params.focus  = focus;
-      if (due)    params.due    = due;
-      const r = await get("/v2/action-items", params);
-      const items = r.items ?? [];
-      if (!items.length) return { content: [{ type: "text", text: "No matching action items." }] };
-
-      const byAccount = new Map();
-      for (const it of items) {
-        const key = it.account || it.account_email || it.entity_id || "—";
-        if (!byAccount.has(key)) byAccount.set(key, []);
-        byAccount.get(key).push(it);
-      }
-      const lines = [`${items.length} action item${items.length !== 1 ? "s" : ""}:`];
-      for (const [account, list] of byAccount) {
-        lines.push(`\n${account}:`);
-        for (const it of list) {
-          const who  = it.owner_kind === "prospect" ? "[them]" : "[you]";
-          const when = it.due_at ? `  (due ${fmtWhen(it.due_at)})` : "";
-          lines.push(`  ${who} ${it.title}${when}`);
-        }
-      }
-      return { content: [{ type: "text", text: lines.join("\n") }] };
-    }
-  );
 
   // ===========================================================================
   // TOOL: verify  —  POST /v2/verify
@@ -1078,56 +941,6 @@ export function createServer() {
     }
   );
 
-  server.tool(
-    "delete_note",
-    "DELETE a note saved by mistake. Pass the note's `id` (returned by `save_note`). It's removed from " +
-    "search and context immediately; the timeline stays reconstructable. Only touches notes — it will " +
-    "refuse an id that isn't a note. Use this for a note saved in error; to CHANGE a note, save a new " +
-    "one instead.",
-    {
-      id: z.string().describe("The note id to delete (from a prior `save_note` result)."),
-    },
-    async ({ id }) => {
-      try {
-        const r = await del(`/v2/notes/${encodeURIComponent(id)}`);
-        return { content: [{ type: "text", text:
-          r.status === "already_deleted" ? "That note was already deleted." : "Note deleted — it's out of search and context now." }] };
-      } catch (e) {
-        const msg = /note_not_found/.test(e.message)
-          ? "No note with that id in this workspace — check the id from the save_note result."
-          : /not_a_note/.test(e.message)
-          ? "That id isn't a note, so it can't be deleted here. Only save_note notes can be deleted this way."
-          : `Couldn't delete the note: ${e.message}`;
-        return { content: [{ type: "text", text: msg }] };
-      }
-    }
-  );
-
-  // ===========================================================================
-  // TOOLS: list + introspect — enumerate what's on the workspace, and who you are.
-  // GET /v2/notes · /v2/workspace/integrations · /v2/workspace/members.
-  // ===========================================================================
-  server.tool(
-    "list_notes",
-    "List saved notes newest-first (chronological), optionally scoped to one person/company with " +
-    "`focus`. This is the LIST companion to search_notes (which is semantic): use it for \"show me the " +
-    "notes on X\", or to enumerate notes and get their ids — e.g. to pick one to delete_note. Returns " +
-    "id, type, title, date and a snippet for each.",
-    {
-      focus: z.string().optional().describe("Restrict to one person/company (email, LinkedIn URL, entity UUID, or domain). Omit for the whole workspace."),
-      limit: z.number().int().min(1).max(100).optional().describe("Max notes to return (default 20)."),
-    },
-    async ({ focus, limit }) => {
-      const r = await get("/v2/notes", { ...(focus ? { focus } : {}), ...(limit ? { limit } : {}) });
-      if (r.status === "ambiguous") {
-        const opts = (r.candidates ?? []).map(c => `  • ${c.name ?? "(unnamed)"}  [${c.entity_id}]`).join("\n");
-        return { content: [{ type: "text", text: `"${focus}" matches several — re-call list_notes with one of these entity ids as focus:\n${opts}` }] };
-      }
-      if (!r.notes?.length) return { content: [{ type: "text", text: focus ? "No notes on that account." : "No notes saved yet." }] };
-      const lines = r.notes.map(n => `  • ${n.title || n.type}${n.date ? ` (${n.date})` : ""}  [${n.id}]\n    ${n.snippet}`).join("\n");
-      return { content: [{ type: "text", text: `${r.notes.length} note(s)${r.has_more ? " (more available — raise limit)" : ""}:\n${lines}` }] };
-    }
-  );
 
   server.tool(
     "list_integrations",
@@ -1162,29 +975,6 @@ export function createServer() {
     }
   );
 
-  // ===========================================================================
-  // TOOL: get_routing_preferences
-  // The routing preferences that make THIS agent default to Edda for GTM. The
-  // agent applies them itself in Claude Code (write to CLAUDE.md); for claude.ai
-  // the user pastes them into Org preferences. Not applicable to Codex/others.
-  // ===========================================================================
-  server.tool(
-    "get_routing_preferences",
-    "Get the routing preferences that make this agent treat Edda as the DEFAULT for GTM — so it " +
-    "reaches for get_context / get_account instead of raw CRM or HubSpot / Salesforce / Gong / " +
-    "Granola when someone forgets to say \"Edda\". This is an OPTIONAL onboarding step, and " +
-    "CLAUDE CODE-specific. If you are running in Claude Code, set it up for the user: ask whether to " +
-    "apply it to this project (write the returned text to ./CLAUDE.md) or to all projects " +
-    "(~/.claude/CLAUDE.md), then write it there. The user can also paste it into claude.ai → Settings " +
-    "→ Organization preferences (Team/Enterprise) or Personal preferences (Pro). If you are NOT Claude " +
-    "Code (Codex, Cursor, n8n, …), this does not apply — skip it.",
-    {},
-    async () => {
-      return { content: [{ type: "text", text:
-        `Routing preferences (write to the user's CLAUDE.md in Claude Code, or have them paste into ` +
-        `claude.ai → Settings → Organization/Personal preferences):\n\n${ROUTING_PREFERENCES}` }] };
-    }
-  );
 
   return server;
 }