@plaud-ai/mcp 0.1.32 → 0.2.0

package/dist/chunk-5JTZ7NKP.js

@@ -1,144 +0,0 @@
-var __create = Object.create;
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __getProtoOf = Object.getPrototypeOf;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __commonJS = (cb, mod) => function __require() {
-  return mod || (0, cb[__getOwnPropNames(cb)[0]])((mod = { exports: {} }).exports, mod), mod.exports;
-};
-var __export = (target, all) => {
-  for (var name in all)
-    __defProp(target, name, { get: all[name], enumerable: true });
-};
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__getProtoOf(mod)) : {}, __copyProps(
-  // If the importer is in node compatibility mode or this is not an ESM
-  // file that has been converted to a CommonJS file using a Babel-
-  // compatible transform (i.e. "__esModule" has not been set), then set
-  // "default" to the CommonJS "module.exports" for node compatibility.
-  isNodeMode || !mod || !mod.__esModule ? __defProp(target, "default", { value: mod, enumerable: true }) : target,
-  mod
-));
-
-// src/skills.ts
-var SKILLS = [
-  {
-    name: "search-recordings",
-    description: "Search and filter Plaud recordings by date, tag, or keyword",
-    content: `## Plaud Skill: search-recordings
-
-There is no server-side search or filter API. To find a recording, fetch all pages from \`list_files\` and match client-side.
-
-**Step 1 \u2014 Collect search criteria**
-
-If the user's request is vague, ask for more specific information before fetching:
-- Approximate date or time range?
-- Rough title or topic to look for in the name?
-
-The more specific the criteria, the earlier a match can be found during pagination.
-
-**Step 2 \u2014 Fetch pages and match**
-
-Call \`list_files\` starting from page 1. For each page, check if any recording matches the user's criteria by name, date, or duration. Continue fetching subsequent pages until a match is found or all pages are exhausted.
-
-**Step 3 \u2014 Present results**
-
-Show a clear list of matches: recording name, date, duration, and file ID. If no match is found, tell the user and suggest refining the criteria.
-
-Do not fetch transcripts or notes unless the user explicitly asks to view the content of a specific recording.`
-  },
-  {
-    name: "extract-structured-data",
-    description: "Extract structured fields from a Plaud recording using a custom schema",
-    content: `## Plaud Skill: extract-structured-data
-
-When the user wants to extract specific fields or structured information from a recording, follow this workflow:
-
-1. If no recording is specified, call \`list_files\` and ask the user to identify the target
-2. Call \`get_note\` to retrieve the AI-generated summary, action items, and key topics
-3. Call \`get_transcript\` if the extraction requires full verbatim content
-4. Apply the user's schema or field list to the content and return the extracted data
-5. Present each field clearly; flag any fields where the content is ambiguous or absent
-
-Example schemas the user might request:
-- \`{ "action_items": [], "decisions": [], "attendees": [] }\`
-- \`{ "pain_points": [], "follow_ups": [], "deal_stage": "" }\`
-- \`{ "diagnoses": [], "medications": [], "next_appointment": "" }\``
-  },
-  {
-    name: "generate-artifact",
-    description: "Generate a document (email, summary, SOAP note, brief) grounded in a Plaud recording",
-    content: `## Plaud Skill: generate-artifact
-
-When the user wants to generate a document grounded in recording content, follow this workflow:
-
-1. Call \`get_note\` to retrieve AI-generated notes for the target recording
-2. Call \`get_transcript\` if the artifact requires verbatim quotes or precise detail
-3. Generate the artifact using the recording content as the source of truth
-4. Format the output to match the requested artifact type
-
-Common artifact types:
-- **Follow-up email** \u2014 summarize key points, list action items, professional tone
-- **Meeting summary** \u2014 attendees, decisions made, next steps
-- **SOAP note** \u2014 Subjective / Objective / Assessment / Plan format for clinical use
-- **Project brief** \u2014 background, goals, scope, timeline from a planning session
-- **Weekly digest** \u2014 highlights across multiple recordings from the past week`
-  },
-  {
-    name: "synthesize-corpus",
-    description: "Analyze trends and patterns across multiple Plaud recordings",
-    content: `## Plaud Skill: synthesize-corpus
-
-When the user wants to analyze patterns, trends, or themes across multiple recordings, follow this workflow:
-
-1. Call \`list_files\` with date or tag filters to identify the target set of recordings (max 50 per call)
-2. For each recording, call \`get_note\` to retrieve the AI-generated summary
-3. Call \`get_transcript\` only if deeper analysis requires full verbatim content from specific recordings
-4. Synthesize insights across all recordings:
-   - Recurring themes or topics
-   - Trends over time
-   - Consistent decisions or blockers
-   - Patterns in action items or follow-ups
-5. Present findings with references to specific recordings as supporting evidence
-
-Use date filters to scope the corpus (e.g., last week, last quarter, a specific project period).`
-  },
-  {
-    name: "push-to-destination",
-    supported: false,
-    description: "Send recording content or a generated artifact to Notion, HubSpot, Slack, Linear, or a webhook",
-    content: `## Plaud Skill: push-to-destination
-
-When the user wants to send recording content or a generated artifact to an external system, follow this workflow:
-
-1. Confirm what content to send: extracted data, a generated artifact, or raw notes
-2. Confirm the destination and any required identifiers:
-   - **Notion** \u2014 page ID or database ID
-   - **HubSpot / Salesforce** \u2014 CRM object ID (deal, contact, or company)
-   - **Linear** \u2014 project or team ID
-   - **Slack** \u2014 channel name or ID
-   - **Webhook** \u2014 URL provided by the user
-3. Deliver the content to the destination using the appropriate integration tool or API call available in your environment
-4. Confirm successful delivery to the user
-
-Note: Destination credentials (API tokens, webhook URLs) must be provided by the user. Do not store them in conversation history \u2014 use environment variables or the user's config.`
-  }
-];
-var ACTIVE_SKILLS = SKILLS.filter((s) => s.supported !== false);
-var SKILLS_COMBINED = ACTIVE_SKILLS.map((s) => s.content).join("\n\n---\n\n");
-
-export {
-  __commonJS,
-  __export,
-  __toESM,
-  ACTIVE_SKILLS,
-  SKILLS_COMBINED
-};

package/skills/plaud/SKILL.md

@@ -1,40 +0,0 @@
----
-name: plaud
-description: Access and manage Plaud recordings, transcriptions, and meeting notes. Use when the user mentions Plaud, wants to find recordings, review transcripts, check meeting summaries, or manage their audio files.
----
-
-You have access to the user's Plaud recordings via MCP tools. Use them to help the user find, review, and analyze their recordings.
-
-## Available tools
-
-| Tool | When to use |
-|---|---|
-| `login` | User is not authenticated, or auth has expired |
-| `logout` | User wants to sign out or disconnect |
-| `get_current_user` | User asks who is logged in, or to verify account |
-| `list_files` | User wants to browse, search, or find recordings |
-| `get_file` | User wants full details of a specific recording (including download link) |
-| `get_note` | User wants the AI-generated summary, action items, or key topics of a recording |
-| `get_transcript` | User wants the full timestamped transcript with speaker labels |
-
-## Typical workflows
-
-**First-time use:** Call `login` first. If any tool returns an auth error, call `login` before retrying.
-
-**Find a recording:** Call `list_files` to browse. Use pagination (`page`, `page_size`) if the user wants more results.
-
-**Review notes or summary:** Call `get_note` with the file ID.
-
-**Read transcript:** Call `get_transcript` with the file ID.
-
-**Get full details (including download link):** Call `get_file` with the file ID. The response includes:
-- `source_list`: timestamped transcript with speaker labels
-- `note_list`: AI-generated summaries in Markdown
-- `presigned_url`: temporary download link (valid 24 hours)
-
-## Guidelines
-
-- Always check if the user is logged in before calling data tools. If you get an auth error, call `login` first.
-- When listing files, present results clearly with name, date, and duration.
-- When showing transcripts, format them readably with timestamps and speaker labels.
-- When showing notes, render the Markdown content directly.