@absolutejs/mcp 0.17.8 → 0.18.0

package/dist/src/apps.d.ts

@@ -33,3 +33,5 @@ export declare const appResourceContent: (resource: McpAppResource, uri: string)
     };
 };
 export { createBillingApps } from "./billingApps";
+export { createWorkflowApps } from "./workflowApps";
+export { createWorkflowTools, projectSetupStatus, projectWorkPreview, type McpSetupStatus, type McpWorkPreview, type McpWorkPreviewRequest, } from "./workflowTools";

package/dist/src/index.d.ts

@@ -49,3 +49,5 @@ export { createCheckoutHandoffTool, createPurchaseStatusTool, type McpPurchaseSt
 export { createBillingReportTools, createBillingManagementTool, } from "./billingTools";
 export { MCP_APP_MIME, clientSupportsMcpApps, withMcpApp, type McpAppResource, type McpAppsConfig, } from "./apps";
 export { createBillingApps } from "./billingApps";
+export { createWorkflowApps } from "./workflowApps";
+export { createWorkflowTools, projectSetupStatus, projectWorkPreview, type McpSetupStatus, type McpWorkPreview, type McpWorkPreviewRequest, } from "./workflowTools";

package/dist/src/workflowApp.generated.d.ts

@@ -0,0 +1,2 @@
+export declare const workflowAppScript: string;
+export declare const workflowAppCss: string;

package/dist/src/workflowApps.d.ts

@@ -0,0 +1,6 @@
+import { type McpAppResource } from "./apps";
+import type { McpToolRegistry } from "./types";
+export declare const createWorkflowApps: () => {
+    resources: Record<string, McpAppResource>;
+    decorateTools: (tools: McpToolRegistry) => McpToolRegistry;
+};

package/dist/src/workflowTools.d.ts

@@ -0,0 +1,26 @@
+import type { McpToolRegistry } from "./types";
+export type McpSetupStatus = {
+    business: string | null;
+    businessCount: number;
+    portalAccess: boolean;
+    availableCredits: number;
+};
+export type McpWorkPreviewRequest = {
+    operation: string;
+    maxCredits: number;
+};
+export type McpWorkPreview = McpWorkPreviewRequest & {
+    summary: string;
+    availableCredits: number;
+    eligible: boolean;
+    reason: string;
+};
+export declare const projectSetupStatus: (value: unknown) => McpSetupStatus;
+export declare const projectWorkPreview: (value: unknown) => McpWorkPreview;
+/** Readers must close over the authenticated identity. No executor, reservation,
+ * checkout or account-selector callback belongs in this read-only contract. */
+export declare const createWorkflowTools: (readers: {
+    setup: () => Promise<McpSetupStatus>;
+    operations: readonly string[];
+    preview: (request: McpWorkPreviewRequest) => Promise<McpWorkPreview>;
+}) => McpToolRegistry;

package/docs/commerce-host-rules.md

@@ -287,3 +287,84 @@ conditions. This does not change the global direct-MCP default. The complete
 native handoff now passes after accounting for Windows' external-site dialog;
 no link defect or need for an upstream link fix was established. Rich-view
 startup remains a separate tracked issue.
+
+## September 12 individual Copilot paid-work review
+
+The [bounded paid-work review](reviews/vscode-individual-paid-work.md) separately
+covers user-requested service work funded by existing service credits for the
+reviewed individual Copilot direct-MCP channel. Deployments must bind the exact
+registration/account and enforce budgets, retries and recovery. It expires
+October 12, 2026. It does not enable the shared default or expand checkout,
+organization-account or other-host eligibility.
+
+## Launch evidence checklist — September 12, 2026
+
+This checklist separates reusable package guarantees from deployment activation.
+The September 10 survey remains the full host inventory; this follow-up rechecked
+the highest-priority restrictions and existing Copilot review boundary. It does
+not certify the untested hosts or broaden any executable commerce profile.
+
+### Current source checks
+
+- Claude still documents purchases through interactive connectors as unsupported.
+  Its help page does not settle the separate external credit-checkout question.
+  Keep that flow unverified pending clarification; non-commerce report rendering
+  is a separate capability. [Claude help](https://support.claude.com/en/articles/13454812-use-interactive-connectors-in-claude).
+- ChatGPT plugin guidelines still exclude digital-credit sales and transactional
+  links. Entitlement explanations and informational destinations are distinct
+  from purchase initiation. Do not turn an informational destination into an
+  automatic checkout redirect. [Plugin guidelines](https://developers.openai.com/plugins/app-guidelines#commerce-and-monetization).
+- Direct Codex documents remote MCP and OAuth. That technical documentation alone
+  does not establish commerce eligibility for a particular account/distribution.
+  Keep its separate review pending; neither automatically apply hosted-plugin
+  rules to every direct connection nor infer an exemption.
+  [Direct MCP documentation](https://learn.chatgpt.com/docs/extend/mcp?surface=cli).
+- Cursor Marketplace still excludes direct and indirect plugin-access fees in
+  section 3.1. Review directly configured MCP separately; a working connection
+  does not resolve the marketplace restriction.
+  [Publisher terms](https://cursor.com/marketplace-publisher-terms).
+- GitHub still directs individual Copilot users to ToS section J and Business /
+  Enterprise users to different terms. The two scoped individual Copilot reviews
+  remain the package's interpretation, expiring October 12, 2026; this check
+  does not extend their expiry or authorize organization accounts.
+  [Applicable agreements](https://docs.github.com/en/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot).
+- VS Code issue #335908 remains open. Retain the tested affected-version fallback
+  until a released editor passes the documented fresh-load and remount tests.
+  [Upstream issue](https://github.com/microsoft/vscode/issues/335908).
+
+### Evidence required for each advertised host
+
+| Gate | Required evidence | Owner |
+| --- | --- | --- |
+| Distribution and policy | Exact host surface, account agreement, category, actions, official sources, dated interpretation and expiry | Package review; deployment supplies verified binding |
+| Authentication | Real signup/consent return, exact registration/account, refresh, revoked access and cross-account rejection | Auth package primitives and consumer integration |
+| Presentation | Installed version, actual negotiated capabilities, visible first load, refresh, pagination and text fallback | MCP package fixture; real host test |
+| Funded access | Subscription-free access, portal denial, explicit budget, settlement, retry conflict and recovery at zero | Billing package and consumer services |
+| Checkout, if eligible | Own HTTPS origin, explicit browser confirmation, server-priced intent, idempotent grant and uncertain-outcome recovery | Shared handoff plus consumer gateway |
+| Work effects | Immutable approval version, ownership, expiry, repeat-safe execution and durable status; rendering performs no action | Shared workflow contract and consumer handler |
+| Operations | Manual or automated validation, deployment readiness, reconciliation, support procedure and rollback preserving financial records | Consumer deployment |
+
+Mark each gate **passed**, **qualified**, **pending** or **not offered**, with a
+link to evidence. A successful report fixture is not OAuth certification; a
+successful payment is not proof of paid model metering. Never count a member or
+complimentary account as a production subscription-free canary. No additional
+live charge is required merely to review or document a host.
+
+The package commerce regression suite was rerun: 18 tests / 43 assertions passed,
+including discovery/execution guards, policy rechecks, restrictive profile
+intersection, expiry, spoofed metadata and failure handling. This is regression
+evidence for the policy mechanism, not vendor approval or a live host test.
+
+### Recommended implementation order for consumers
+
+Build non-commerce setup and work previews using shared Apps primitives and
+identical structured/text contracts first. Then add version-bound approval and
+durable results, followed by attributed spend/outcome reporting. Bind each
+consumer's domain services rather than duplicating policy, ledger or bridge
+code. Test an eligible conversational, IDE and terminal channel separately;
+record unavailable hosts as pending. Keep deferred background effects outside
+bounded work until their reservation and recovery lifecycle is implemented.
+
+This documentation update changes no runtime API, profile, feature flag or
+published package version. It is available in the shared repository and will
+ship with the next package release through the existing documentation allowlist.

package/docs/mcp-apps.md

@@ -58,3 +58,27 @@ Primary references checked September 11, 2026: [stable Apps specification](https
 ## Real-host canaries
 
 See [the reusable host canary and observed results](host-canaries.md) for isolated connection instructions, acceptance criteria and remaining rollout gates.
+
+## Read-only setup and work previews
+
+`createWorkflowTools` binds authenticated setup and preview readers; `createWorkflowApps`
+decorates those tools and supplies offline resources. Merge its resources into the
+server Apps configuration alongside billing resources. Both tools return text and
+projected structured data when no Apps capability is negotiated. Setup reports
+business context, portal access and available credits. Preview requires an allowed
+operation and a positive proposed maximum, reports current eligibility, and never
+reserves or executes. A maximum is not a price estimate or approval.
+
+Readers must close over the authenticated account and resolve domain ownership.
+Unknown operations and extra arguments (including account IDs) reject before reads.
+The package strips extra reader fields. There is no executor callback. Consumers
+keep these tools outside the zero-credit work gate with a bounded read rate limit.
+Execution independently validates authorization, balance, stable work ID and budget.
+Neither view contains checkout links, setup mutations or outbound actions.
+
+The official Apps bridge delivers initial results without automatic tool calls.
+Only explicit Refresh invokes the same read tool; preview refresh preserves the
+operation and budget. Errors clear stale eligibility and point back to the assistant.
+Known affected VS Code builds retain the shared text fallback. The visible-browser
+fixture is `bun test/fixtures/workflowServer.ts` (loopback port 4418); it uses zero
+credits and no gateway or database.

package/docs/reviews/vscode-individual-paid-work.md

@@ -0,0 +1,69 @@
+# VS Code individual Copilot: bounded paid service work
+
+Reviewed September 12, 2026; expires October 12, 2026. Channel: native VS Code,
+manually configured remote MCP, individual Copilot subscription. Scope:
+user-requested work delivered by the connected service, paid from that service's
+existing credit balance. This review is separate from
+[external checkout](vscode-individual-external-checkout.md).
+
+## Decision
+
+Eligible for a deployment-specific `paid_access` binding for `usage_credits` and
+`digital_service` under the conditions below. This is our interpretation of the
+reviewed terms, not vendor certification or express approval of every paid MCP.
+The reviewed terms do not identify a specific prohibition on this bounded use
+of an independently operated service. Re-review account type, distribution,
+service behavior and changed terms before expanding the scope.
+
+## Primary sources and interpretation
+
+- [GitHub additional product terms](https://docs.github.com/en/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)
+  directs individual Copilot users to GitHub ToS section J; organizational
+  agreements are outside this review.
+- [GitHub ToS](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)
+  distinguishes third-party relationships in B.5. Section H prohibits API abuse
+  and certain data uses; J covers AI output responsibility and individual data
+  controls. Our inference: the user's separate service agreement can govern
+  metered service work, while the user's Copilot obligations continue to apply.
+- [GitHub acceptable-use policies](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies)
+  restrict resale of GitHub services, spam, privacy misuse and abusive activity.
+  The reviewed service sells its own work. It must not sell Copilot access,
+  share accounts, evade usage limits, or obtain GitHub data for prohibited sales
+  or solicitation. Ordinary task drafts do not authorize sending outreach.
+- [VS Code MCP documentation](https://code.visualstudio.com/docs/agent-customization/mcp-servers)
+  documents remote-server configuration and host trust/tool interaction.
+  Technical support for a tool is not commercial permission. Preserve the host's
+  approvals; the service's ledger must independently enforce its budget.
+
+## Required deployment controls
+
+1. Bind the reviewed origin, verified OAuth registration and authenticated
+   account on the server. Client names, `clientInfo`, prompts, tool arguments or
+   claimed host capabilities cannot select the review. Unknown clients stay
+   ineligible. Organization accounts require a separate review.
+2. Make service-credit charging clear before work starts. Require a stable work
+   ID and an explicit maximum service-credit budget. Service credits are not
+   Copilot tokens or a promise of monetary return. Never infer an unlimited
+   spending authorization from authentication, a tool result or a chat claim.
+3. Reserve and settle atomically, cap the account's charge, and deduplicate
+   retries. Replaying a completed work ID returns its stored result. Reject
+   changed inputs under the same ID. Preserve uncertain work for reconciliation;
+   do not release its hold and repeat its effects without verification.
+4. Keep account ownership, cancellation/deletion, entitlement and balance checks
+   on the server. Exhaustion blocks new paid work but preserves bounded status
+   and recovery access. Background work needs its own durable budget propagation;
+   exclude handlers that cannot uphold the cap across detached work.
+5. This review grants only `paid_access`; checkout needs its own review. It does
+   not permit card collection in chat, saved-card charges, subscriptions,
+   automatic refill, bulk outreach or arbitrary third-party purchases. Retain
+   any separate approval needed for outbound effects and sensitive actions.
+6. Limit outputs to information the user is authorized to access. Treat host
+   transcripts as retained data. Apply the service's privacy obligations and do
+   not expose credentials, capability links or unrelated account records in
+   diagnostics or reusable canary evidence.
+
+A deployment must validate its ledger migration, actual host/account connection,
+retry behavior, budget limits and recovery before activation. A review alone
+neither activates tools nor certifies their accounting. This document does not
+change the shared `direct-mcp` default or restrictions for Claude, ChatGPT,
+marketplaces, organization-managed Copilot or other hosts.

package/package.json

@@ -90,5 +90,5 @@
     "canary:checkout": "bun canary/checkout.ts"
   },
   "types": "./dist/src/index.d.ts",
-  "version": "0.17.8"
+  "version": "0.18.0"
 }