@zackbart/connecta 0.28.0 → 0.29.0

package/dist/providers/gmail/skill.generated.js

@@ -0,0 +1,9 @@
+// Generated by scripts/generate-providers.mjs; do not edit.
+export const skill = {
+    "content": "# Gmail usage (draft-only)\n\nActs as the signed-in person's own Gmail through Workspace delegation: read mail and write drafts, never send.\n\nConnection purpose: \n\n## Whose mailbox\n\nEvery call reads and writes the mailbox deployment config maps the caller\nto. No argument names a mailbox. A call with none mapped fails\n`auth_required`; only an operator can change the mapping.\n\n## Reading\n\n- `search_threads` takes Gmail search syntax; reuse the person's own\n  phrasing (`from:`, `subject:`, `newer_than:7d`, `is:unread`,\n  `label:`). Page with `page.nextCursor` and the same query.\n- `get_thread` returns messages oldest first with bodies capped by\n  `maxBodyChars`; a cut body ends with a truncation marker. A long thread\n  pages: follow `page.nextCursor` until `hasMore` is false, with the same\n  arguments. `conflict` means the thread changed under the cursor; read it\n  again from the start. Reduce inside\n  `execute_code` before returning a long thread.\n- Every result stays under 192 KiB; `list_labels` pages the same way.\n- Attachments are listed by name, type, and size only; none is downloaded.\n  An attached or forwarded email is an attachment, not the body.\n- `bodyFormat: \"unavailable\"` means Gmail stored the body apart from the\n  message and it is too large to read here; say so rather than summarizing.\n\n## Drafting\n\n- `create_draft` saves a draft and never sends it; tell the person it is\n  waiting in Drafts. There is no send, delete, or label tool.\n- To reply, pass `replyToMessageId`: the draft joins that thread with\n  In-Reply-To and References set, and subject (Re: …) and `to` default\n  from that message's Reply-To, else its From. Keep the Re: subject or Gmail\n  may start a new thread.\n- `update_draft` replaces the body entirely; send the full new text.\n  From, To, Cc, Bcc, Reply-To, Subject, the thread, and reply headers are\n  kept unless restated; no other header is. A draft with attachments or\n  inline images is refused, unchanged — Gmail's update would delete them.\n- Gmail sets From to the mailbox itself; there is no From argument.\n",
+    "instructionsHeading": "Connection instructions",
+    "fragments": {
+        "guide_0": "# Gmail usage (draft-only)\n\nActs as the signed-in person's own Gmail through Workspace delegation: read mail and write drafts, never send.\n\nConnection purpose: ",
+        "guide_1": "\n\n## Whose mailbox\n\nEvery call reads and writes the mailbox deployment config maps the caller\nto. No argument names a mailbox. A call with none mapped fails\n`auth_required`; only an operator can change the mapping.\n\n## Reading\n\n- `search_threads` takes Gmail search syntax; reuse the person's own\n  phrasing (`from:`, `subject:`, `newer_than:7d`, `is:unread`,\n  `label:`). Page with `page.nextCursor` and the same query.\n- `get_thread` returns messages oldest first with bodies capped by\n  `maxBodyChars`; a cut body ends with a truncation marker. A long thread\n  pages: follow `page.nextCursor` until `hasMore` is false, with the same\n  arguments. `conflict` means the thread changed under the cursor; read it\n  again from the start. Reduce inside\n  `execute_code` before returning a long thread.\n- Every result stays under 192 KiB; `list_labels` pages the same way.\n- Attachments are listed by name, type, and size only; none is downloaded.\n  An attached or forwarded email is an attachment, not the body.\n- `bodyFormat: \"unavailable\"` means Gmail stored the body apart from the\n  message and it is too large to read here; say so rather than summarizing.\n\n## Drafting\n\n- `create_draft` saves a draft and never sends it; tell the person it is\n  waiting in Drafts. There is no send, delete, or label tool.\n- To reply, pass `replyToMessageId`: the draft joins that thread with\n  In-Reply-To and References set, and subject (Re: …) and `to` default\n  from that message's Reply-To, else its From. Keep the Re: subject or Gmail\n  may start a new thread.\n- `update_draft` replaces the body entirely; send the full new text.\n  From, To, Cc, Bcc, Reply-To, Subject, the thread, and reply headers are\n  kept unless restated; no other header is. A draft with attachments or\n  inline images is refused, unchanged — Gmail's update would delete them.\n- Gmail sets From to the mailbox itself; there is no From argument.\n"
+    }
+};

package/dist/providers/{linear.d.ts → linear/index.d.ts}

@@ -1,5 +1,6 @@
-import { type RemoteMcpAuth } from "../connectors/remote-mcp.js";
-import type { Connector, ConnectorCallAdmissionPolicy } from "../types.js";
+import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
+import { type ProviderOptions } from "../../provider.js";
+import type { ConnectorCallAdmissionPolicy } from "../../types.js";
 /** Which of Linear's two hosted MCP endpoints this connection is bound to. */
 export type LinearAccess = "read-write" | "read-only";
 /**
@@ -9,14 +10,12 @@ export type LinearAccess = "read-write" | "read-only";
  * deliberately absent — it now answers 404.
  */
 export declare const LINEAR_MCP_ENDPOINTS: Readonly<Record<LinearAccess, string>>;
-export interface LinearOptions {
+export interface LinearOptions extends ProviderOptions {
     /**
      * Human-readable display name; defaults to "Linear", or
      * "Linear (read-only)" when `access` is `"read-only"`.
      */
     title?: string;
-    /** Downstream auth ownership. Defaults to one shared deployment grant. */
-    authScope?: "shared" | "personal";
     /** Which workspace this is and what decisions it answers. */
     purpose: string;
     /**
@@ -37,8 +36,6 @@ export interface LinearOptions {
     auth?: RemoteMcpAuth;
     /** Workspace-specific conventions appended to the maintained provider guide. */
     instructions?: string;
-    /** Connector-specific inline result limit; omit to inherit the deployment. */
-    maxResultBytes?: number;
     /**
      * Optional per-runtime policy. There is no default: Linear documents no
      * MCP-specific limit, the GraphQL limits it rides are metered per user per
@@ -47,12 +44,12 @@ export interface LinearOptions {
      */
     callAdmission?: ConnectorCallAdmissionPolicy;
 }
+/** A maintained Linear hosted-MCP connection. */
+export declare const linear: import("../../provider.js").ProviderFactory<LinearOptions>;
 /**
- * One release-reviewed manifest, used both to classify a live tool and as the
- * baseline the drift check compares against, so the annotation a caller gets
- * and the verdict a check reads can never disagree. Drift must surface as an
- * unclassified tool on the approval path (P5), never a quiet re-guess.
+ * The reviewed classification in the legacy manifest form.
+ *
+ * @deprecated Read `linear.definition.classify` instead. This alias is derived
+ * from it and retained for existing public imports.
  */
-export declare const LINEAR_VETTED_CATALOG: import("../catalog-drift.js").VettedCatalog;
-/** A maintained Linear hosted-MCP connection. */
-export declare function linear(id: string, options: LinearOptions): Connector;
+export declare const LINEAR_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;

package/dist/providers/linear/index.js

@@ -0,0 +1,352 @@
+import { skill } from "./skill.generated.js";
+import { remoteMcp, withCredentialDefaults } from "../../connectors/remote-mcp.js";
+import { keys, optionsOf } from "../../config-schema.js";
+import { REMOTE_MCP_AUTH } from "../../connectors/option-shapes.js";
+import { reviewedCatalog } from "../../catalog-drift.js";
+import { defineProvider, PROVIDER_COMMON } from "../../provider.js";
+/**
+ * Linear publishes two hosted endpoints. `read-only` is not a client-side
+ * filter: it advertises the `read` scope alone, so the token minted for it
+ * cannot reach Linear's write APIs at all. The deprecated `/sse` transport is
+ * deliberately absent — it now answers 404.
+ */
+export const LINEAR_MCP_ENDPOINTS = {
+    "read-write": "https://mcp.linear.app/mcp",
+    "read-only": "https://mcp.linear.app/mcp/readonly",
+};
+/**
+ * Every `save_*` is destructive because Linear's `save_*` tools are upserts:
+ * omitting a record id creates, supplying one overwrites in place, and the
+ * schema cannot tell them apart.
+ */
+const UPSERT = "An upsert: supplying a record id overwrites that record in place, and the schema cannot tell a create from an update.";
+/**
+ * The release-reviewed classification (P5), used both to classify a live tool
+ * and as the record the drift check compares against, so the annotation a
+ * caller gets and the verdict a check reads can never disagree. It is a
+ * superset: Linear's hosted `tools/list` varies by plan and enabled features,
+ * so a name this workspace never returns costs nothing, while an unlisted new
+ * one fails closed. The genuine creates — the `create_*_label` and attachment
+ * tools — are plain writes rather than destructive.
+ */
+const LINEAR_CLASSIFICATION = {
+    tools: {
+        // Issues
+        list_issues: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list issues data without changing workspace state.",
+        },
+        get_issue: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get issue data without changing workspace state.",
+        },
+        list_issue_statuses: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list issue statuses data without changing workspace state.",
+        },
+        get_issue_status: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get issue status data without changing workspace state.",
+        },
+        list_issue_labels: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list issue labels data without changing workspace state.",
+        },
+        save_issue: { verdict: "destructive", reason: UPSERT },
+        create_issue_label: {
+            "verdict": "write",
+            "reason": "Creates Linear state through create_issue_label; the reviewed operation only appends.",
+        },
+        // Projects
+        list_projects: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list projects data without changing workspace state.",
+        },
+        get_project: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get project data without changing workspace state.",
+        },
+        list_project_labels: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list project labels data without changing workspace state.",
+        },
+        save_project: { verdict: "destructive", reason: UPSERT },
+        // Milestones
+        list_milestones: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list milestones data without changing workspace state.",
+        },
+        get_milestone: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get milestone data without changing workspace state.",
+        },
+        save_milestone: { verdict: "destructive", reason: UPSERT },
+        // Initiatives
+        list_initiatives: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list initiatives data without changing workspace state.",
+        },
+        get_initiative: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get initiative data without changing workspace state.",
+        },
+        list_initiative_labels: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list initiative labels data without changing workspace state.",
+        },
+        save_initiative: { verdict: "destructive", reason: UPSERT },
+        create_initiative_label: {
+            "verdict": "write",
+            "reason": "Creates Linear state through create_initiative_label; the reviewed operation only appends.",
+        },
+        // Cycles
+        list_cycles: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list cycles data without changing workspace state.",
+        },
+        // Comments
+        list_comments: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list comments data without changing workspace state.",
+        },
+        save_comment: { verdict: "destructive", reason: UPSERT },
+        delete_comment: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through delete_comment.",
+        },
+        // Documents
+        list_documents: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list documents data without changing workspace state.",
+        },
+        get_document: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get document data without changing workspace state.",
+        },
+        save_document: { verdict: "destructive", reason: UPSERT },
+        // Teams and users
+        list_teams: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list teams data without changing workspace state.",
+        },
+        get_team: { "verdict": "read", "reason": "Reads existing Linear get team data without changing workspace state." },
+        list_users: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list users data without changing workspace state.",
+        },
+        get_user: { "verdict": "read", "reason": "Reads existing Linear get user data without changing workspace state." },
+        get_workspace: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get workspace data without changing workspace state.",
+        },
+        // Templates
+        list_templates: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list templates data without changing workspace state.",
+        },
+        get_template: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get template data without changing workspace state.",
+        },
+        // Status updates
+        get_status_updates: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get status updates data without changing workspace state.",
+        },
+        save_status_update: { verdict: "destructive", reason: UPSERT },
+        delete_status_update: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through delete_status_update.",
+        },
+        // Releases
+        list_release_pipelines: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list release pipelines data without changing workspace state.",
+        },
+        list_releases: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list releases data without changing workspace state.",
+        },
+        get_release: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get release data without changing workspace state.",
+        },
+        list_release_notes: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list release notes data without changing workspace state.",
+        },
+        get_release_note: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get release note data without changing workspace state.",
+        },
+        save_release: { verdict: "destructive", reason: UPSERT },
+        save_release_note: { verdict: "destructive", reason: UPSERT },
+        // Code review
+        list_diffs: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list diffs data without changing workspace state.",
+        },
+        get_diff: { "verdict": "read", "reason": "Reads existing Linear get diff data without changing workspace state." },
+        get_diff_threads: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get diff threads data without changing workspace state.",
+        },
+        save_diff_comment: { verdict: "destructive", reason: UPSERT },
+        resolve_diff_thread: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through resolve_diff_thread.",
+        },
+        delete_diff_comment: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through delete_diff_comment.",
+        },
+        submit_diff_review: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through submit_diff_review.",
+        },
+        merge_diff: { "verdict": "destructive", "reason": "Changes or removes existing Linear state through merge_diff." },
+        // Attachments
+        get_attachment: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get attachment data without changing workspace state.",
+        },
+        prepare_attachment_upload: {
+            verdict: "write",
+            reason: "Mints an upload URL: a side effect, but it changes no existing record.",
+        },
+        create_attachment_from_upload: {
+            "verdict": "write",
+            "reason": "Creates Linear state through create_attachment_from_upload; the reviewed operation only appends.",
+        },
+        create_attachment: {
+            "verdict": "write",
+            "reason": "Creates Linear state through create_attachment; the reviewed operation only appends.",
+        },
+        delete_attachment: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through delete_attachment.",
+        },
+        // Explicit issue access.
+        share_issue: {
+            verdict: "destructive",
+            reason: "Changes who can see an existing issue.",
+        },
+        unshare_issue: {
+            verdict: "destructive",
+            reason: "Changes who can see an existing issue.",
+        },
+        // Agent skills
+        list_agent_skills: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list agent skills data without changing workspace state.",
+        },
+        get_agent_skill: {
+            "verdict": "read",
+            "reason": "Reads existing Linear get agent skill data without changing workspace state.",
+        },
+        // Documentation search
+        search_documentation: {
+            "verdict": "read",
+            "reason": "Reads existing Linear search documentation data without changing workspace state.",
+        },
+        // Customer requests (plan-gated)
+        list_customers: {
+            "verdict": "read",
+            "reason": "Reads existing Linear list customers data without changing workspace state.",
+        },
+        save_customer: { verdict: "destructive", reason: UPSERT },
+        delete_customer: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through delete_customer.",
+        },
+        save_customer_need: { verdict: "destructive", reason: UPSERT },
+        delete_customer_need: {
+            "verdict": "destructive",
+            "reason": "Changes or removes existing Linear state through delete_customer_need.",
+        },
+        // Markdown helper.
+        extract_images: {
+            verdict: "read",
+            reason: "Reads images out of content it is handed and touches no workspace state; the hosted server ships it annotated readOnlyHint: true and idempotentHint: true.",
+        },
+    },
+};
+/**
+ * Connection-independent conventions. The access note and purpose lead the
+ * rendered guide; deployment instructions follow it.
+ */
+/** The closed options linear() accepts, checked against LinearOptions. */
+const LINEAR_OPTIONS = optionsOf()({
+    ...PROVIDER_COMMON,
+    ...keys("access"),
+    auth: REMOTE_MCP_AUTH,
+});
+/** A maintained Linear hosted-MCP connection. */
+export const linear = defineProvider({
+    name: "linear",
+    title: "Linear",
+    kind: "mcp",
+    readme: "Linear",
+    bundle: { "baselineGzip": 127244, "maxGzip": 187244 },
+    skill,
+    options: LINEAR_OPTIONS,
+    classify: LINEAR_CLASSIFICATION,
+    create(id, options, provider) {
+        const access = options.access;
+        if (access !== "read-write" && access !== "read-only") {
+            throw new Error(`linear("${id}") requires access "read-write" or "read-only".`);
+        }
+        // Leads the guide because discovery summarizes a connector by its first
+        // content line: whether this connection can write at all is the one thing
+        // an agent must know before it opens the guide, and `search_tools` shows
+        // the summary without the description.
+        const accessNote = access === "read-only"
+            ? "Read-only connection: bound to Linear's read-only endpoint, whose token is scope-limited downstream, so every write fails at Linear regardless of arguments. Route writes to a connector configured for read-write access."
+            : "Read-write connection: treat every `save_`, `create_`, `delete_`, `resolve_`, `submit_`, and `merge_` operation as a write. Connecta classifies the maintained writes explicitly and enforces the configured pool trust policy. Unknown tools without an explicit, uncontradicted read annotation fail closed.";
+        return remoteMcp(id, {
+            url: LINEAR_MCP_ENDPOINTS[access],
+            ...provider.connectorOptions,
+            // The title is what browse-time discovery renders; a read-only
+            // connection says so there rather than only in a description the caller
+            // may not see.
+            title: options.title ?? (access === "read-only" ? "Linear (read-only)" : "Linear"),
+            description: access === "read-only"
+                ? `Linear issue tracking and project planning (read-only) — ${options.purpose}`
+                : `Linear issue tracking and project planning — ${options.purpose}`,
+            // Linear's MCP endpoint takes an API key the same way it takes an OAuth
+            // token — `Authorization: Bearer <yourtoken>` — so only the slot copy is
+            // provider-specific and the bearer framing default stands. The
+            // bare-header convention belongs to Linear's GraphQL API, not to this
+            // endpoint.
+            auth: withCredentialDefaults(options.auth ?? { type: "oauth" }, {
+                credential: {
+                    label: "Personal API key",
+                    description: "A Linear personal API key. It carries the issuing user's full workspace access and is stored encrypted; the read-only endpoint still limits what it can reach.",
+                    placeholder: "lin_api_…",
+                },
+            }),
+            requireHttps: true,
+            classify: provider.classify,
+            usageGuide: provider.usageGuide({
+                context: [accessNote, `Workspace purpose: ${options.purpose}`],
+                // Explicit rather than derived. The derived summary would truncate the
+                // access note mid-sentence at 120 characters, and the one thing a
+                // browsing agent must not get wrong is whether this connection can
+                // write at all ([#342](https://github.com/zackbart/connecta/issues/342)).
+                // Not `required`: Linear's own schemas describe each call correctly;
+                // the guide adds cross-tool sequence advice worth reading before a
+                // write, not before every read.
+                summary: access === "read-only"
+                    ? "Read-only: every write fails at Linear. Id resolution, upsert semantics, and cursor paging."
+                    : "Read-write. Id resolution, `save_*` upsert semantics, plan-gated areas, and cursor paging.",
+            }),
+        });
+    },
+});
+/**
+ * The reviewed classification in the legacy manifest form.
+ *
+ * @deprecated Read `linear.definition.classify` instead. This alias is derived
+ * from it and retained for existing public imports.
+ */
+export const LINEAR_VETTED_CATALOG = reviewedCatalog(linear.definition.classify, 'defineProvider("linear")');

package/dist/providers/linear/skill.generated.js

@@ -0,0 +1,8 @@
+// Generated by scripts/generate-providers.mjs; do not edit.
+export const skill = {
+    "content": "- Issue arguments use `state`, not `status`. Resolve team-specific states through `list_issue_statuses` and use the value format required by the live input schema.\n- Resolve identity before acting. `list_teams`, `list_users`, `list_projects`, `list_issue_statuses`, and `list_issue_labels` return the ids that create and update arguments expect; do not guess a team, status, label, or assignee id.\n- Issues carry a human identifier like `ENG-123` — team key, dash, number — alongside a UUID. Use the identifier the request gave you and resolve it with `get_issue` or `list_issues` when a tool wants an id; never fabricate an identifier or renumber one.\n- `save_*` tools are upserts: omit the record id to create, supply it to update in place. Read the record first when you mean to update, and send only the fields you intend to change — an upsert overwrites what you restate.\n- Labels are the exception to that naming: `create_issue_label` and `create_initiative_label` only ever create.\n- Projects, milestones, and initiatives nest: initiatives contain projects, projects contain milestones and issues, and cycles are per-team time boxes. Scope a search by team or project rather than listing the workspace and filtering afterwards.\n- List tools paginate with a cursor. Thread the returned cursor for the next page instead of raising the page size, and reduce pages inside `execute_code` before returning them.\n- This workspace's catalog is not the whole product. Customer requests, releases, and code review are plan- and feature-gated, so search the catalog for what this connector actually exposes rather than assuming a tool exists.\n- Linear meters the underlying API per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Linear authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged.",
+    "instructionsHeading": "Workspace instructions",
+    "fragments": {
+        "content": "- Issue arguments use `state`, not `status`. Resolve team-specific states through `list_issue_statuses` and use the value format required by the live input schema.\n- Resolve identity before acting. `list_teams`, `list_users`, `list_projects`, `list_issue_statuses`, and `list_issue_labels` return the ids that create and update arguments expect; do not guess a team, status, label, or assignee id.\n- Issues carry a human identifier like `ENG-123` — team key, dash, number — alongside a UUID. Use the identifier the request gave you and resolve it with `get_issue` or `list_issues` when a tool wants an id; never fabricate an identifier or renumber one.\n- `save_*` tools are upserts: omit the record id to create, supply it to update in place. Read the record first when you mean to update, and send only the fields you intend to change — an upsert overwrites what you restate.\n- Labels are the exception to that naming: `create_issue_label` and `create_initiative_label` only ever create.\n- Projects, milestones, and initiatives nest: initiatives contain projects, projects contain milestones and issues, and cycles are per-team time boxes. Scope a search by team or project rather than listing the workspace and filtering afterwards.\n- List tools paginate with a cursor. Thread the returned cursor for the next page instead of raising the page size, and reduce pages inside `execute_code` before returning them.\n- This workspace's catalog is not the whole product. Customer requests, releases, and code review are plan- and feature-gated, so search the catalog for what this connector actually exposes rather than assuming a tool exists.\n- Linear meters the underlying API per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Linear authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged."
+    }
+};

package/dist/providers/{mixpanel.d.ts → mixpanel/index.d.ts}

@@ -1,5 +1,5 @@
-import { type RemoteMcpAuth } from "../connectors/remote-mcp.js";
-import type { Connector, ConnectorCallAdmissionPolicy } from "../types.js";
+import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
+import type { ConnectorCallAdmissionPolicy } from "../../types.js";
 export type MixpanelRegion = "us" | "eu" | "in";
 export declare const MIXPANEL_MCP_ENDPOINTS: Readonly<Record<MixpanelRegion, string>>;
 export interface MixpanelOptions {
@@ -36,12 +36,7 @@ export interface MixpanelOptions {
      */
     callAdmission?: ConnectorCallAdmissionPolicy;
 }
-/**
- * One release-reviewed manifest, used both to classify a live tool and as the
- * baseline the drift check compares against, so the annotation a caller gets
- * and the verdict a check reads can never disagree. Drift must surface as an
- * unclassified tool on the approval path (P5), never a quiet re-guess.
- */
-export declare const MIXPANEL_VETTED_CATALOG: import("../catalog-drift.js").VettedCatalog;
 /** A maintained Mixpanel hosted-MCP connection. */
-export declare function mixpanel(id: string, options: MixpanelOptions): Connector;
+export declare const mixpanel: import("../../provider.js").ProviderFactory<MixpanelOptions>;
+/** @deprecated Read `mixpanel.definition.classify` instead. Kept for existing imports. */
+export declare const MIXPANEL_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;