@ductape/mcp 0.1.0

package/README.md

@@ -0,0 +1,82 @@
+# Ductape MCP Server
+
+MCP (Model Context Protocol) server that exposes **Ductape SDK** operations as tools. All calls go through the **Ductape backend proxy** at a fixed URL; the SDK never runs in the MCP process. It is completely stateless; you provide your **Publishable Key** per execution.
+
+## Prerequisites
+
+- Ductape backend (proxy and users services) reachable at `https://api.ductape.app` (handled automatically)
+- A workspace **Publishable Key** (from your Ductape workspace)
+
+## Install
+
+```bash
+cd platform/mcp-server
+npm install
+```
+
+**MCP SDK:** `npm install` pulls in `@modelcontextprotocol/sdk` and `zod` (v1, recommended). For the v2 alpha server package instead, use `npm install @modelcontextprotocol/server zod @cfworker/json-schema`.
+
+## Configuration & Run
+
+```bash
+npm run build && node dist/index.js
+```
+
+Or with tsx:
+
+```bash
+npm run dev
+```
+
+The server uses **stdio** transport (stdin/stdout), so it is intended to be spawned by an MCP client (e.g. Cursor).
+There are no environment variables required to run the server.
+
+## Cursor configuration
+
+In Cursor, add the server in MCP settings (e.g. `~/.cursor/mcp.json` or project `.cursor/mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "ductape": {
+      "command": "node",
+      "args": ["/absolute/path/to/Ductape/platform/mcp-server/dist/index.js"]
+    }
+  }
+}
+```
+
+Use an absolute path for `args[0]`. 
+
+## Tools
+
+The server exposes **three tools**:
+
+1. **`ductape_execute`**:
+   - It runs any allowed SDK module method via the backend proxy.
+   - **Arguments:** 
+     - `publishable_key` (string, required for authentication)
+     - `module` (e.g. `databases`, `storage`, `vector`)
+     - `method` (e.g. `query`, `list`, `findSimilar`)
+     - `params` (array of positional arguments matching the SDK).
+   - **Full reference:** The tool description embeds the complete list of modules, allowed methods, and their expected parameters for quick reference. (See **[docs/TOOLS.md](docs/TOOLS.md)** if using a client that requires it).
+
+2. **`ductape_generate_payload`**:
+   - Calls backend `POST /integrations/v1/payloads/generate`.
+   - Returns canonical executable payload templates with schema metadata (`{ payload, meta }`).
+   - Intended for MCP-assisted code snippet generation and payload prefill in agent workflows.
+   - **Arguments:**
+     - `workspace_id`, `user_id`, `public_key`
+     - `product_tag`, `env_slug`
+     - `operation_family`, `method`
+     - optional `targets`, `schema_mode`, `include_session`, `include_cache`, `input_hint`
+
+3. **`ductape_generate_snippet`**:
+   - Calls `ductape_generate_payload` flow and returns:
+     - generated payload/meta
+     - ready-to-copy SDK snippet in `typescript` or `python`
+   - Intended for engineers and copilots that need executable examples quickly.
+
+## Security
+
+- Passing the `publishable_key` on a per-request basis guarantees that each execution is isolated. This architecture safely supports deployments that multiplex multiple user connections in a single server thread (e.g., SSE), avoiding cross-tenant leakage.

package/dist/index.d.ts

@@ -0,0 +1,11 @@
+#!/usr/bin/env node
+/**
+ * Ductape MCP Server
+ *
+ * Exposes Ductape SDK operations as MCP tools by calling the backend proxy.
+ *
+ * Authentication:
+ * Requires passing a `publishable_key` with every `ductape_execute` payload.
+ */
+export {};
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;;;;;GAOG"}