@ampless/mcp-server 1.0.0-alpha.17 → 1.0.0-alpha.18

package/dist/tools/index.d.ts

@@ -1,127 +0,0 @@
-import { BundleExtractResult } from 'ampless';
-
-interface ResolvedSite {
-    name: string;
-    url?: string;
-    environment: 'prod' | 'stg' | 'dev';
-    siteId: string;
-}
-
-/**
- * Abstract contracts each tool handler depends on. Concrete
- * implementations live elsewhere:
- *
- *   - Stdio CLI: `src/appsync.ts` (Cognito-id-token bearer) and
- *     `src/s3.ts` (default-credential-chain S3 client).
- *   - HTTP transport: `@ampless/admin/api/mcp` wraps the consumer's
- *     existing `generateClient<Schema>()` + S3 client.
- *
- * Both routes satisfy these interfaces structurally (no `implements`
- * needed) — TypeScript's structural typing checks the shape on the
- * call site. Tools never instantiate these themselves; the caller
- * passes a ready `ToolContext` into `dispatchToolCall`.
- */
-interface GraphqlClient {
-    query<T>(operation: string, variables?: Record<string, unknown>): Promise<T>;
-}
-interface StorageObject {
-    /** Full S3 key including any prefix. */
-    key: string;
-    /** Object size in bytes (0 when the backend can't supply it). */
-    size: number;
-    /** ISO 8601 timestamp of the last write, when the backend supplies it. */
-    lastModified?: string;
-}
-interface StorageClient {
-    /**
-     * Upload `body` to the bucket at `key` with `contentType`. Returns
-     * the public URL of the stored object (same format both routes use:
-     * https://{bucket}.s3.{region}.amazonaws.com/{key}).
-     */
-    putObject(key: string, body: Uint8Array, contentType: string): Promise<string>;
-    /**
-     * Remove the object at `key`. Implementations should treat a missing
-     * key as success (S3 DeleteObject is idempotent by default).
-     */
-    deleteObject(key: string): Promise<void>;
-    /**
-     * List every object under `prefix`. Implementations are expected to
-     * paginate internally so the caller gets the full set in a single
-     * resolved promise — the static-bundle tools never expect more than
-     * a few hundred entries per bundle in practice.
-     */
-    listObjects(prefix: string): Promise<StorageObject[]>;
-}
-interface ToolContext {
-    graphql: GraphqlClient;
-    storage: () => StorageClient;
-    site?: ResolvedSite;
-}
-
-/**
- * Server-side zip extractor used by the static-bundle MCP tools. Both
- * the stdio CLI and the Lambda HTTP transport run this — `fflate` is
- * a workspace dependency of `@ampless/mcp-server`, so the import
- * resolves identically in both. The browser-side admin uploader has
- * its own `extractZip(File)` based on JSZip (works on a `File`, not a
- * `Buffer`).
- *
- * Behaviour parity with the admin extractor:
- *  - Skip directory entries (fflate gives byte arrays only, so this
- *    is naturally satisfied unless the zip has empty-byte directory
- *    placeholders — those still get filtered out by validateBundlePath
- *    returning "directory entry" for any path ending with `/`).
- *  - Silently drop OS-specific junk (`__MACOSX/*`, `.DS_Store`,
- *    `Thumbs.db`) so callers don't see them as bundle entries.
- *  - Surface structural issues (absolute paths, parent traversal, null
- *    bytes) so the tool can reject the upload.
- *  - Strip a common single top-level directory (macOS Finder zips
- *    wrap their contents in a folder).
- */
-
-interface ExtractZipOptions {
-    /**
-     * Hard ceiling on uncompressed bundle bytes. Defaults to 50 MB,
-     * matching the browser uploader's MAX_BUNDLE_BYTES. Callers running
-     * inside a tight Lambda envelope (Function URL payload cap ~6 MB
-     * post-base64) can tighten this; setting it lower than the bundle
-     * causes `extractZipFromBuffer` to throw before fully populating
-     * `files`.
-     */
-    maxBytes?: number;
-}
-/**
- * Unzip `buffer` in memory and return the same shape the browser
- * `extractZip(File)` helper returns. Throws if the unzip itself fails
- * (corrupt archive) or if the uncompressed size exceeds `maxBytes`.
- */
-declare function extractZipFromBuffer(buffer: Uint8Array, opts?: ExtractZipOptions): BundleExtractResult;
-/**
- * Decode an extracted file's bytes as UTF-8 text. Used by the tool
- * handler before running cross-file `validateBundle` so we don't
- * instantiate a TextDecoder per entry. fflate provides a fast helper.
- */
-declare function decodeUtf8(data: Uint8Array): string;
-
-interface ToolDefinition {
-    name: string;
-    description: string;
-    inputSchema: Record<string, unknown>;
-    handler: (args: Record<string, unknown>, ctx: ToolContext) => Promise<unknown>;
-    destructive?: boolean;
-}
-declare const tools: ToolDefinition[];
-/**
- * Look up a tool definition by name and invoke its handler. Returns
- * `null` when no tool with that name is registered — callers should
- * surface that as a JSON-RPC "method not found" error.
- */
-declare function dispatchToolCall(name: string, args: Record<string, unknown>, ctx: ToolContext): Promise<unknown>;
-/**
- * `tools` is the canonical registry; `getTools()` returns it for
- * callers that prefer a function over a top-level constant (admin's
- * HTTP factory exposes this through its options shape).
- */
-declare function getTools(): readonly ToolDefinition[];
-
-export { type ExtractZipOptions, type GraphqlClient, type StorageClient, type StorageObject, type ToolContext, type ToolDefinition, decodeUtf8, dispatchToolCall, extractZipFromBuffer, getTools, tools };

package/dist/tools/index.js

@@ -1,16 +0,0 @@
-#!/usr/bin/env node
-import {
-  decodeUtf8,
-  dispatchToolCall,
-  extractZipFromBuffer,
-  getTools,
-  tools
-} from "../chunk-WAP4WAMQ.js";
-import "../chunk-LMMQX4CK.js";
-export {
-  decodeUtf8,
-  dispatchToolCall,
-  extractZipFromBuffer,
-  getTools,
-  tools
-};