@edda-business/mcp 0.51.0 → 0.53.0

package/package.json

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

package/src/server.js

@@ -10,20 +10,19 @@
  * sees raw rows — it gets engineered, epistemics-tagged context. It never
  * "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
+ * Tools, by group:
+ *   READ    get_context · get_account · query · attention · verify ·
+ *           search_notes · search_company_knowledge · search_my_vault
+ *   WRITE   save_note · propose_vault_file · propose_company_file · merge_contacts
+ *   CORRECT unmerge_contacts
+ *   RUN     list_integrations · connect_integration
  */
 
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { z } from "zod";
 import { get, post, del } from "./client.js";
 
-export const SERVER_VERSION = "0.51.0";
+export const SERVER_VERSION = "0.53.0";
 
 // ─── helpers ──────────────────────────────────────────────────────────────────
 
@@ -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 ──────────────────────────────────────────────────────────────────
 
@@ -121,10 +71,10 @@ export function createServer() {
     name: "edda",
     version: SERVER_VERSION,
     description:
-      "Edda — the Context Graph for AI Agents. Edda is operated by the agent, not by a human " +
-      "clicking around: call get_workspace_status at the start of a session to see what's set up " +
-      "and what to set up next. Call get_context before drafting outreach or preparing for a " +
-      "meeting. Call record after every interaction, or whenever you learn something.",
+      "Edda — the company knowledge layer for AI agents. The agent reads engineered, " +
+      "epistemics-tagged context instead of raw rows. Call get_context before preparing for a " +
+      "meeting or a decision about a person; search_company_knowledge for how the company works; " +
+      "save_note to keep a brief or transcript on a contact.",
     icons: [
       { src: "https://opennous.cloud/newlogoP.png", mimeType: "image/png", sizes: ["64x64"] },
     ],
@@ -146,7 +96,7 @@ export function createServer() {
     "act on it, 'suspect'/'expired' verify first.",
     {
       focus: z.string().describe("Who to look up — an email, a LinkedIn URL, a domain, an entity UUID, or a name. A name may match several people; you'll get candidates to choose from."),
-      intent: z.enum(["draft_email", "follow_up", "meeting_prep", "call_prep", "account_review"])
+      intent: z.enum(["follow_up", "meeting_prep", "call_prep", "account_review"])
         .optional()
         .describe("What you are about to do — shapes which context surfaces (default: account_review)"),
       budget_tokens: z.number().optional().describe("Approximate token budget for the context block"),
@@ -240,7 +190,7 @@ export function createServer() {
     {
       id: z.string().describe("Who to look up — an email, an entity UUID, or a name. A name may match several people; you'll get candidates to choose from."),
       intent: z
-        .enum(["meeting_prep", "call_prep", "account_review", "follow_up", "draft_email"])
+        .enum(["meeting_prep", "call_prep", "account_review", "follow_up"])
         .optional()
         .describe(
           "What you're about to do. Shapes how much of their history comes back: a meeting brief wants " +
@@ -435,82 +385,7 @@ export function createServer() {
     }
   );
 
-  // ===========================================================================
-  // TOOL: record  —  POST /v2/observations
-  // The single write verb. You observe — Edda derives the updated facts.
-  // ===========================================================================
-  server.tool(
-    "record",
-    "Record what happened or what you learned about a person or company. You never overwrite " +
-    "anything — you observe, and Edda derives the updated facts. Use kind:'event' for an interaction " +
-    "(property like 'interaction.email_sent', 'interaction.call_held', 'interaction.email_reply') and " +
-    "kind:'state' for a fact (property like 'job_title', 'deal.proposal_amount'). Examples — sent an " +
-    "email: {kind:'event',property:'interaction.email_sent',value:{description:'intro email'}}; " +
-    "learned their title changed: {kind:'state',property:'job_title',value:'VP of Engineering'}; " +
-    "a fact ended (they left): {kind:'state',property:'job_title',value:null}.",
-    {
-      focus: z.string().describe("Email address or entity UUID of the person or company"),
-      observations: z.array(z.object({
-        kind: z.enum(["event", "state"]).describe("event = an interaction; state = a fact"),
-        property: z.string().describe("e.g. 'interaction.email_sent' or 'job_title'"),
-        value: z.any().optional().describe("the event detail or the fact value; null = the fact ended"),
-        source: z.string().optional().describe("where this came from (default: agent)"),
-      })).describe("One or more observations to record"),
-    },
-    async ({ focus, observations }) => {
-      const result = await post("/v2/observations", { focus, observations });
-      const parts = [`Recorded ${result.recorded} observation${result.recorded !== 1 ? "s" : ""}.`];
-      if (result.claims_recomputed?.length) {
-        parts.push(`Facts updated: ${result.claims_recomputed.join(", ")}.`);
-      }
-      parts.push(`(entity_id: ${result.entity_id})`);
-      return { content: [{ type: "text", text: parts.join("\n") }] };
-    }
-  );
 
-  // ===========================================================================
-  // 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 +473,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 +502,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
@@ -703,8 +534,7 @@ export function createServer() {
   // TOOL: save_note  —  POST /v2/notes
   // Attach a long-form artifact to a CONTACT: a meeting brief you wrote, a
   // transcript, pre-meeting prep, or a plain note. Append-only and dated, so the
-  // contact builds a record across meetings. Distinct from `record` (which logs
-  // that an interaction happened) — this keeps the document itself.
+  // contact builds up a document trail across meetings.
   // ===========================================================================
   server.tool(
     "save_note",
@@ -712,11 +542,9 @@ export function createServer() {
     "brief you wrote, a transcript, pre-meeting prep, research, or a plain note. Use this whenever " +
     "you produce something durable about a specific contact that's worth keeping for next time (e.g. " +
     "after writing a meeting brief, save it to the contact so future meetings can reference it). " +
-    "Notes are append-only and dated, so a contact builds a record across meetings — later you can " +
-    "read the last few and see what changed. This is NOT for logging that an interaction happened " +
-    "(use `record` with an interaction.* event for that), and NOT for the user's own GTM profile " +
-    "(that lives in their context files — sync it with `sync_icp`). Put the full text in `content` — it's kept for agents to read; the " +
-    "UI shows the title and date, not the whole body.",
+    "Notes are append-only and dated, so a contact builds a document trail across meetings — later " +
+    "you can read the last few and see what changed. Put the full text in `content` — it's kept for " +
+    "agents to read; the UI shows the title and date, not the whole body.",
     {
       focus: z.string().describe("Who to attach it to — an email, LinkedIn URL, domain, or entity UUID (not a bare name)."),
       content: z.string().describe("The full note or document text (a short note or a complete brief/transcript)."),
@@ -909,104 +737,6 @@ export function createServer() {
     },
   );
 
-  // ===========================================================================
-  // TOOL: get_workspace_status  —  GET /v2/workspace/status
-  // The "one main call." Edda is operated by the agent, so the agent needs to
-  // know the state of the workspace: is it onboarded, is the GTM foundation built,
-  // which integrations are connected, is CRM sync configured, are events live —
-  // and what to set up next. Call this at the start of a session.
-  // ===========================================================================
-  server.tool(
-    "get_workspace_status",
-    "See the whole setup state of this workspace in one call, plus a ranked NEXT STEPS list (each step " +
-    "carries its own why/how). Edda is operated by you, the agent — call this at the START of a session " +
-    "and walk the user top-down through the steps it returns; the server sequences them by current " +
-    "state, so trust that order. Two constraints when acting on them: (1) Gmail (Google OAuth) and " +
-    "LinkedIn (no public API — Edda uses Unipile) CANNOT be connected by you — point the user to the " +
-    "Integrations page; key-based tools (Prospeo, Apollo, Instantly, HubSpot token) you CAN connect via " +
-    "connect_integration, and CSV import is a user action in the app. (2) Respect the plan — never push " +
-    "a feature it doesn't include (e.g. CRM sync on free). Recommend the next 1-2 steps, don't dump the " +
-    "whole list.",
-    {},
-    async () => {
-      const s = await get("/v2/workspace/status");
-      const setup = s.setup ?? {};
-      const lines = [];
-
-      const ws = s.workspace ?? {};
-      lines.push(`WORKSPACE: ${ws.name || "(unnamed)"}${ws.website ? ` · ${ws.website}` : ""}${ws.business_type ? ` · ${ws.business_type}` : ""}`);
-      const pl = s.plan ?? {};
-      lines.push(`PLAN: ${pl.name || pl.id || "free"}${pl.crm_sync === false ? "  (CRM sync not included — do not offer it)" : ""}`);
-      if (s.self_hosted) {
-        const e = s.env_integrations ?? {};
-        const mk = (b) => (b ? "✓ set" : "✗ NOT set");
-        lines.push("SELF-HOSTED — these channels are wired via edda.env (you can't set env vars; tell the operator to set + restart):");
-        lines.push(`  LinkedIn/Unipile: ${mk(e.linkedin_unipile)}   Email/Resend: ${mk(e.email_resend)}   Gmail OAuth: ${mk(e.gmail_oauth)}`);
-      }
-      lines.push("");
-
-      const mark = (b) => (b ? "✓" : "✗");
-      lines.push("SETUP:");
-      lines.push(`  ${mark(setup.onboarding?.done)} Profile${setup.onboarding?.done ? "" : ` — missing ${(setup.onboarding?.missing ?? []).join(", ") || "details"}`}`);
-      const ints = setup.integrations?.connected ?? [];
-      lines.push(`  ${mark((setup.integrations?.count ?? 0) > 0)} Integrations (${setup.integrations?.count ?? 0})${ints.length ? `: ${ints.map((i) => i.name).join(", ")}` : ""}`);
-      const crm = setup.crm_sync ?? {};
-      if (crm.available === false) {
-        lines.push(`  – CRM sync (not on the ${pl.name || pl.id || "current"} plan)`);
-      } else {
-        lines.push(`  ${mark(crm.configured)} CRM sync${crm.configured ? `: ${(crm.providers ?? []).map((p) => p.provider).join(", ")}` : ""}${crm.pending_hygiene_proposals ? ` · ${crm.pending_hygiene_proposals} hygiene proposal(s) to review` : ""}`);
-      }
-      lines.push(`  ${mark(setup.enrichment?.connected)} Enrichment${setup.enrichment?.provider ? `: ${setup.enrichment.provider}` : ""}`);
-      lines.push(`  ${mark((setup.webhooks?.count ?? 0) > 0 || (setup.triggers?.count ?? 0) > 0)} Events — ${setup.webhooks?.count ?? 0} webhook(s), ${setup.triggers?.count ?? 0} trigger(s)`);
-      const rec = setup.recommended ?? {};
-      lines.push("");
-      lines.push("RECOMMENDED CHANNELS (connect these first):");
-      lines.push(`  ${mark(rec.email)} Email / Gmail   ${mark(rec.linkedin)} LinkedIn   ${mark(rec.meeting_notetaker)} Meeting note-taker`);
-      lines.push(`  Records imported: ${setup.records?.count ?? 0}`);
-
-      if (s.next_steps?.length) {
-        lines.push("");
-        lines.push("NEXT STEPS:");
-        for (const step of s.next_steps) {
-          lines.push(`  • ${step.title}`);
-          if (step.why) lines.push(`      why: ${step.why}`);
-          if (step.how) lines.push(`      how: ${step.how}`);
-        }
-      } else {
-        lines.push("");
-        lines.push("Everything's set up. Nothing pending.");
-      }
-
-      return { content: [{ type: "text", text: lines.join("\n").trim() }] };
-    }
-  );
-
-  // ===========================================================================
-  // TOOL: set_workspace_profile  —  POST /v2/workspace/onboarding
-  // Agent-driven onboarding. Instead of a human clicking through a wizard in the
-  // app, you collect the basics from the user in conversation and write them
-  // here. This is the first thing get_workspace_status asks for when a workspace
-  // is new.
-  // ===========================================================================
-  server.tool(
-    "set_workspace_profile",
-    "Set or update the workspace's basic identity — its company name and website. Send only the fields " +
-    "you're setting or changing.",
-    {
-      name: z.string().optional().describe("The company / workspace name."),
-      website: z.string().optional().describe("The company website."),
-    },
-    async ({ name, website }) => {
-      const r = await post("/v2/workspace/onboarding", { name, website });
-      const w = r.workspace ?? {};
-      const set = [
-        w.name && `name=${w.name}`,
-        w.website && `site=${w.website}`,
-      ].filter(Boolean);
-      return { content: [{ type: "text", text:
-        `Workspace profile saved.${set.length ? ` ${set.join(" · ")}.` : ""}` }] };
-    }
-  );
 
   // ===========================================================================
   // TOOL: connect_integration  —  POST /v2/workspace/integrations
@@ -1047,87 +777,7 @@ export function createServer() {
     }
   );
 
-  // ===========================================================================
-  // TOOLS: the CORRECTION layer — unsay something recorded by mistake. `record` and
-  // `save_note` are how you write; these are how you take it back. Both heal the
-  // derived layer: retracting an observation re-derives the claim from what remains,
-  // deleting a note drops it from search/context. DELETE /v2/observations|notes/:id.
-  // ===========================================================================
-  server.tool(
-    "retract_observation",
-    "RETRACT an observation you recorded by mistake, and heal the record. Pass the observation's " +
-    "`id` (returned by `record`). Edda deletes it and re-derives the affected fact from the " +
-    "observations that remain — so a wrong value you observed is un-observed and the claim reverts as " +
-    "if it had never happened; if it was the only observation for that fact, the fact is invalidated. " +
-    "Use this when you recorded the wrong thing (wrong value, wrong person, a test), NOT to represent a " +
-    "real change over time — a genuine change is a NEW `record`, which supersedes by recency.",
-    {
-      id: z.string().describe("The observation id to retract (from a prior `record` result)."),
-    },
-    async ({ id }) => {
-      try {
-        const r = await del(`/v2/observations/${encodeURIComponent(id)}`);
-        return { content: [{ type: "text", text:
-          `Observation retracted. The claim for ${r.property} was ${r.claim === "invalidated" ? "invalidated (no observations left)" : "re-derived from the remaining observations"}.` }] };
-      } catch (e) {
-        const msg = /observation_not_found/.test(e.message)
-          ? "No observation with that id in this workspace — check the id from the record result."
-          : `Couldn't retract the observation: ${e.message}`;
-        return { content: [{ type: "text", text: msg }] };
-      }
-    }
-  );
-
-  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",
@@ -1143,48 +793,7 @@ export function createServer() {
     }
   );
 
-  server.tool(
-    "whoami",
-    "Report who this API key acts AS and who else is on the workspace — the agent's own identity in " +
-    "Edda. Returns your scope (a MEMBER key sees only that member's private content plus the shared " +
-    "graph; an ADMIN key sees all raw content) and the team roster with names and roles. Use it to " +
-    "understand whose view you have and to reference teammates. Emails show only for an admin key.",
-    {},
-    async () => {
-      const r = await get("/v2/workspace/members");
-      const scope = r.you?.scope === "admin"
-        ? "an ADMIN key — you see all raw content on this workspace"
-        : "a MEMBER key — you see only your own private content plus the shared graph";
-      const roster = (r.members || [])
-        .map(m => `  • ${m.name || "(unnamed)"} — ${m.role}${m.you ? " (you)" : ""}${m.email ? ` · ${m.email}` : ""}`)
-        .join("\n");
-      return { content: [{ type: "text", text: `You are ${scope}.\n\nWorkspace members (${r.count ?? 0}):\n${roster || "  (none)"}` }] };
-    }
-  );
 
-  // ===========================================================================
-  // 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;
 }