@homespunapps/mcp 1.6.12 → 1.6.13

package/README.md

@@ -2,7 +2,7 @@
 
 A thin **stdio [Model Context Protocol](https://modelcontextprotocol.io) server** for [Homespun](https://homespun.dev). It lets any MCP client (Claude Desktop, Cursor, Windsurf, Cline, your own host) deploy a real multi-user web app in one call and keep operating its data afterwards: hosting on its own URL, magic-link identity, a shared realtime database with per-role permissions, email notifications and file attachments, all included.
 
-It is a wrapper, not a reimplementation: all relay I/O goes through [`@homespunapps/core`](https://www.npmjs.com/package/@homespunapps/core), and config is shared with the [`homespun` CLI](https://www.npmjs.com/package/@homespunapps/cli) (`~/.config/homespun/config.json`) — so the CLI and this server use the **same agent identity**.
+It is a wrapper, not a reimplementation: all relay I/O goes through [`@homespunapps/core`](https://www.npmjs.com/package/@homespunapps/core), and config is shared with the [`homespun` CLI](https://www.npmjs.com/package/@homespunapps/cli) (`~/.config/homespun/config.json`), so the CLI and this server use the **same agent identity**.
 
 ## Runtime requirement: Node.js >= 20
 
@@ -10,7 +10,7 @@ The binary is `homespun-mcp`. It speaks MCP over stdio and is meant to be launch
 
 ## Quickstart
 
-No global install needed — point your MCP client at `npx @homespunapps/mcp`. On first use, if no API key is configured, the server auto-registers a fresh agent against the hosted relay and saves the key to the shared CLI store; nothing else to set up.
+No global install needed: point your MCP client at `npx @homespunapps/mcp`. On first use, if no API key is configured, the server auto-registers a fresh agent against the hosted relay and saves the key to the shared CLI store; nothing else to set up.
 
 ### Claude Desktop
 
@@ -80,23 +80,23 @@ If you'd rather install it globally (`npm i -g @homespunapps/mcp`), use `"comman
 
 ## Configuration
 
-All environment variables are optional — the defaults target the hosted relay and auto-register on first use.
+All environment variables are optional; the defaults target the hosted relay and auto-register on first use.
 
 | Variable | Default | Purpose |
 | --- | --- | --- |
 | `HOMESPUN_URL` | `https://homespun.dev` | Relay base URL. Set to point at a different relay. |
 | `HOMESPUN_API_KEY` | _(auto-registered)_ | Agent API key. If unset, the server registers an agent on first use and saves the key to `~/.config/homespun/config.json` (shared with the CLI). |
-| `HOMESPUN_TOKEN` | — | Alias for `HOMESPUN_API_KEY` (for hosts that name secrets `*_TOKEN`). `HOMESPUN_API_KEY` wins if both are set. |
+| `HOMESPUN_TOKEN` | _(none)_ | Alias for `HOMESPUN_API_KEY` (for hosts that name secrets `*_TOKEN`). `HOMESPUN_API_KEY` wins if both are set. |
 | `HOMESPUN_AGENT_NAME` | `homespun-mcp` | Display name for the auto-registered agent. |
-| `HOMESPUN_REGISTER_SECRET` | — | Registration secret, only for relays running `REGISTRATION_MODE=secret`. |
+| `HOMESPUN_REGISTER_SECRET` | _(none)_ | Registration secret, only for relays running `REGISTRATION_MODE=secret`. |
 
 Config precedence mirrors the CLI: env vars win over the saved profile, which falls back to the default relay URL.
 
 ## Tools
 
-This server has **full parity with the [`homespun` CLI](https://www.npmjs.com/package/@homespunapps/cli)** — every capability the CLI exposes is reachable here.
+This server has **full parity with the [`homespun` CLI](https://www.npmjs.com/package/@homespunapps/cli)**: every capability the CLI exposes is reachable here.
 
-MCP tools are request/response — there is no long-lived "watch". To receive a human's response you **poll** `get_events` with the cursor from the previous call (optionally with `wait_seconds` to long-poll); to watch a record collection, re-call `list_records` with the prior `since`. Each tool description spells out the pattern for the model.
+MCP tools are request/response, so there is no long-lived "watch". To see what changed you **poll** `get_feed_events` with the cursor from the previous call (pass `wait` to long-poll, 0 to 30 seconds); to watch one collection, re-call `list_rows` with the prior `next_cursor` as `since`. Each tool description spells out the pattern for the model.
 
 To keep the tool list compact (a flat 50+ tools would bloat client context and degrade selection), **hot-path nouns stay discrete tools** while **multi-verb management nouns collapse into one tool each with a required `action` enum**.
 
@@ -104,59 +104,53 @@ To keep the tool list compact (a flat 50+ tools would bloat client context and d
 
 | Tool | What it does |
 | --- | --- |
-| `create_app` | Create an app — inline HTML (`name`+`html`) **or** reuse a saved template (`template_id`). Optional event/input/record schema, participants, tags, icon, callback, `context_key`. Returns `{ app_id, url, urls, title, expires_at }`. **Give `url` to the human.** |
-| `get_app_state` | Fetch an app's metadata (status, title, expiry) without its event log. |
-| `get_events` | Poll the app's append-only event log for what the human did. Pass `since` (cursor) and optional `wait_seconds` (long-poll). |
-| `send_to_app` | Push an event into an open app to update the live UI. |
-| `update_app` | Edit a live app in place (ttl/title/preamble/input_data/metadata/tags/icon). |
-| `upgrade_app` | Re-pin a live app to another version of its template (swap HTML+schemas, same URL). |
-| `list_apps` | Enumerate your apps (filter by status/template_id; paginated). |
-| `delete_app` | Close/delete an app. |
-| `list_records` | List rows in an app's mutable record collection (also the records poll/watch). |
-| `get_record` | Fetch one record row by key. |
-| `upsert_record` | Create/return a record row (dedups on `record_key`). |
-| `update_record` | Update a record row (optional `if_match` optimistic lock). |
-| `delete_record` | Soft-delete a record row (the page sees it live). |
-| `delete_record_collection` | Drop a whole record collection (all rows + the collection row). Destructive, owner-only, requires `confirm: true`. |
+| `deploy_app` | Deploy a v2 app: an HTML document plus a capability manifest, hosted at its own URL. Omit `app_id` to create, pass it to redeploy in place (same URL, same data, same members). Takes `html` or `html_path`, optional `assets`, `visibility`, `slug`, `dry_run`, `force`. |
+| `list_rows` | List rows in a collection. Doubles as the poll for a collection's current state: pass the prior `next_cursor` as `since`. |
+| `get_row` | Fetch one row by `key` (a dedicated relay route, not a client-side scan). |
+| `upsert_row` | Create a row, or return the existing one if `key` is already present (`deduped: true`). The only create-shaped verb. |
+| `update_row` | Replace an existing row's `data`. Optional `if_match` optimistic lock. |
+| `delete_row` | Soft-delete a row. Optional `if_match`. |
+| `get_feed_events` | Poll the app's change feed for row creates/updates/deletes from any writer, human or agent. Optional `wait` (0-30s) long-poll. |
 
 ### Consolidated tools (one tool, required `action`)
 
 | Tool | Actions |
 | --- | --- |
-| `template` | `create` · `version` · `update` · `search` · `list` · `show` · `get_version` · `delete` · `publish` · `unpublish` · `search_public` · `set_icon` |
-| `template_records` | `list` · `get` · `upsert` · `update` · `delete` · `delete_collection` |
-| `participant` | `list` · `new` · `revoke` |
-| `share` | `list` · `invite` · `set_access` · `revoke` |
-| `attachments` | `upload` · `download` · `show` · `list` · `delete` · `mint_token` · `revoke_token` · `list_tokens` |
+| `apps` | `list` · `show` · `update` · `share_link_rotate` · `delete` · `wake` · `domain_set` · `domain_status` · `domain_remove` |
+| `members` | `add` · `list` · `set_role` · `remove` · `roles` |
+| `grants` | `mint` · `list` · `revoke` |
+| `ingest` | `list` · `rotate` · `set_signing_secret` · `clear_signing_secret` |
+| `attachments` | `upload` · `fetch` · `presign` · `finalize` · `download` · `show` · `list` · `delete` · `mint_token` · `revoke_token` · `list_tokens` |
 | `taste` | `get` · `set` · `clear` |
-| `key` | `list` · `revoke` |
-| `trash` | `list` · `restore` · `restore_template` · `purge` · `purge_template` |
+| `key` | `list` · `mint` · `revoke` |
 | `feedback` | `create` · `list` |
 | `agent` | `whoami` · `claim` · `logout` |
+| `community` | `publish` · `get_config_contract` · `install` · `list_pending` · `get_submission` · `approve` · `reject` · `set_trust_level` |
+| `publisher` | `claim` · `get` · `update` |
+| `review` | `create` · `respond` · `report` · `remove` · `unhold` |
 
 ### Single-purpose tools
 
 | Tool | What it does |
 | --- | --- |
-| `run_query` | Read-only SQL over your scoped apps/records/events (`format`: json/csv/tsv/table). |
-| `get_skill` | Fetch the relay's auto-updating `SKILL.md` (unauthenticated) to self-teach the workflow. |
+| `get_skill` | Fetch the relay's auto-updating guide (unauthenticated) to self-teach the workflow. |
 
-**Attachments** take/return file paths: `upload` reads an absolute `file_path`; `download` writes to an absolute `out_path` (or returns base64 when omitted).
+**Attachments** take and return file paths: `upload` reads an absolute `file_path`; `download` writes to an absolute `out_path` (or returns base64 when omitted). For real media, `presign` then PUT then `finalize` avoids moving bytes through the tool call.
 
-**Events vs records.** Events are an append-only journal — forms, approvals, surveys, pickers. Records are a mutable collection where the current state matters more than the edit history — todo lists, kanban boards, comment threads. Reach for records when the page shows several mutable items.
+**One data primitive.** Everything an app stores is a **collection**: a named, mutable, queryable set of rows, each with a `key`, a `data` payload, an optimistic-lock `version` and an `author`. Every write also lands on the app's ordered **change feed**. Declare a collection `appendOnly: true` in the manifest when you want a journal (an audit trail, a submission log) rather than mutable state.
 
 ### Not exposed (and why)
 
-- The CLI's `config show` is replaced by `agent`→`whoami` (resolved relay URL + active profile + whether a key is set; no secrets).
-- `agent register` isn't a tool — the server auto-registers on first use and shares the CLI's key store; `agent`→`claim` binds it to a human afterward.
-- `demo` (the interactive 60-second terminal tour) and the CLI self-updater are terminal/CLI concerns with no agent use; omitted.
+- The CLI's `config show` is replaced by `agent` → `whoami` (resolved relay URL, active profile, and whether a key is set; no secrets).
+- `agent register` is not a tool. The server auto-registers on first use and shares the CLI's key store; `agent` → `claim` binds it to a human afterwards.
+- `demo` (the interactive terminal tour) and the CLI self-updater are terminal concerns with no agent use; omitted.
 
 ## Typical flow
 
-1. `create_app` with your HTML + an `event_schema` declaring the events the page emits → returns a `url`.
-2. Paste the `url` into the conversation and ask the human to open it.
-3. `get_events` with `wait_seconds: 25` in a loop, passing the prior `next_cursor` as `since`, until the awaited event appears.
-4. Optionally `send_to_app` to update the live UI, or use the record tools for mutable collections.
+1. `deploy_app` with your HTML plus an `x-homespun-manifest` declaring the app's collections and which roles may read, write and delete each. Returns `{ app_id, url, ... }`.
+2. Give the `url` to the owner, and invite anyone else with `members` (`action: add`).
+3. `get_feed_events` with `wait: 25` in a loop, passing the prior `cursor` as `since`, to see what people do.
+4. Read and write the same data with `list_rows` / `upsert_row` / `update_row`, and ship changes with `deploy_app` again, passing `app_id`.
 
 ## MCP registry
 
@@ -164,4 +158,4 @@ To keep the tool list compact (a flat 50+ tools would bloat client context and d
 
 ## License
 
-MIT — see [LICENSE](./LICENSE).
+MIT, see [LICENSE](./LICENSE).

package/dist/capabilities.js

@@ -1,18 +1,18 @@
-// Register app's MCP prompt + resource on an McpServer.
+// Register Homespun's MCP prompt + resource on an McpServer.
 //
 // Both the stdio server (packages/mcp/src/server.ts) and the relay's HTTP MCP
 // server call this so an MCP-native client can discover the conceptual guide
 // without a tool call:
 //
-//   - prompt   `homespun_guide`   — surfaces the guide as a prompt the client can
-//                               insert into context ("teach me app").
-//   - resource `homespun://guide`  — the same guide as a readable resource.
+//   - prompt   `homespun_guide`   surfaces the guide as a prompt the client can
+//                                 insert into context ("teach me Homespun").
+//   - resource `homespun://guide`  is the same guide as a readable resource.
 //
 // The guide text is supplied by the host: the relay composes it in-process
 // (MCP-INVOCATION.md + the core extracted from SKILL.md); the stdio server
 // fetches it from the relay over HTTP and falls back to a short pointer when
 // the relay is unreachable at registration time (registration must not block on
-// the network — the get_skill tool is the always-fresh path).
+// the network; the get_skill tool is the always-fresh path).
 export const GUIDE_RESOURCE_URI = "homespun://guide";
 export const GUIDE_PROMPT_NAME = "homespun_guide";
 /**
@@ -23,7 +23,7 @@ export const GUIDE_PROMPT_NAME = "homespun_guide";
 export function registerGuideCapabilities(server, getGuide) {
     server.registerResource(GUIDE_PROMPT_NAME, GUIDE_RESOURCE_URI, {
         title: "Homespun usage guide",
-        description: "The app conceptual guide for MCP clients: when to use app, events vs records, schema design, the house style, and the round-trip mental model — with MCP tool-call invocation grammar.",
+        description: "The Homespun conceptual guide for MCP clients: when to deploy an app, the collection and change-feed data model, schema design, permissions and the house style, plus the MCP tool-call invocation grammar.",
         mimeType: "text/markdown",
     }, async () => {
         const text = await getGuide();
@@ -35,7 +35,7 @@ export function registerGuideCapabilities(server, getGuide) {
     });
     server.registerPrompt(GUIDE_PROMPT_NAME, {
         title: "Homespun usage guide",
-        description: "Insert the app usage guide (MCP invocation + conceptual core) into the conversation so the model knows how to drive app's tools.",
+        description: "Insert the Homespun usage guide (MCP invocation grammar + conceptual core) into the conversation so the model knows how to drive Homespun's tools.",
     }, async () => {
         const text = await getGuide();
         return {

package/dist/guide.js

@@ -1,11 +1,12 @@
-// Compose the MCP-flavoured app guide from the shared conceptual core + the
-// MCP invocation layer.
+// Compose the MCP-flavoured Homespun guide from the shared conceptual core +
+// the MCP invocation layer.
 //
 // Single source of truth: the conceptual core lives in skills/homespun/SKILL.md
 // between `<!-- homespun:core:start -->` / `<!-- homespun:core:end -->` markers (the
 // CLI invocation grammar lives OUTSIDE those markers, so the CLI document and
-// the MCP guide share the exact same prose for "when to use app / events vs
-// records / schema design / house style / the round-trip mental model"). The
+// the MCP guide share the exact same prose for "when to deploy an app / the
+// collection and change-feed data model / schema design / permissions / house
+// style"). The
 // MCP invocation layer (tool-call grammar) lives in skills/homespun/MCP-INVOCATION.md.
 //
 // The MCP guide = MCP-INVOCATION.md (with its trailing "the rest is the core"

package/dist/server.js

@@ -56,7 +56,7 @@ export function buildServer(opts = {}) {
         }
         catch (e) {
             const message = e instanceof Error ? e.message : String(e);
-            return ("# app\n\nThe app guide could not be fetched from the relay " +
+            return ("# homespun\n\nThe Homespun guide could not be fetched from the relay " +
                 `(${message}).\n\nCall the \`get_skill\` tool to retrieve it once the ` +
                 "relay is reachable.\n");
         }

package/dist/tools.js

@@ -172,7 +172,7 @@ const deployAppShape = {
         .optional()
         .describe("Validate only: run the full manifest + asset-shape validation, the compat gate (for a redeploy), and the schedule-timezone advisory, then return { ok, warnings, compat?, breaks? } WITHOUT creating a version or mutating anything. An invalid manifest returns the SAME error a real deploy would; a narrowing redeploy reports the compat break instead of applying it. `check` is an accepted alias."),
     check: z.boolean().optional().describe("Alias for `dry_run`."),
-    manifest: jsonObjectSchema.describe("The x-homespun-manifest capability document (a JSON object). Eight extension keys: app metadata; collections (+ per-collection write/read/delete role lists); externalHosts (fetch allowlist); cdn (allow CDN scripts/styles); capabilities (Permissions-Policy opt-ins); embeds (iframe frame-src allowlist); notify (email-on-row rules); webhooks (signed HTTP POST on-row rules). Call get_skill for the full grammar before authoring one from scratch."),
+    manifest: jsonObjectSchema.describe("The x-homespun-manifest capability document (a JSON object). Eight extension keys: app metadata; collections (+ per-collection write/update/read/delete role lists, where write gates creates and also updates unless the optional update list is declared); externalHosts (fetch allowlist); cdn (allow CDN scripts/styles); capabilities (Permissions-Policy opt-ins); embeds (iframe frame-src allowlist); notify (email-on-row rules); webhooks (signed HTTP POST on-row rules). Call get_skill for the full grammar before authoring one from scratch."),
     visibility: z
         .enum(["private", "link", "public"])
         .optional()
@@ -765,7 +765,7 @@ export const TOOLS = [
     // ----- v2 app lifecycle + data (discrete, hot-path) -----------------------
     {
         name: "deploy_app",
-        description: "Deploy a v2 app: an HTML document + a capability manifest, hosted at its own URL. The manifest has eight extension keys: app metadata; collections (+ per-collection write/read/delete role lists); externalHosts (fetch allowlist); cdn (allow CDN scripts/styles); capabilities (Permissions-Policy opt-ins); embeds (iframe frame-src allowlist); notify (email-on-row rules); webhooks (signed HTTP POST on-row rules). Pass EITHER no `app_id` (create, mints a slug + URL) OR `app_id` (redeploy an existing app with new content). Supply the HTML as INLINE `html` OR as `html_path` (an absolute path read on the MCP-SERVER host, which is the relay for a hosted connector or your CLI host for a locally-run one, NOT the remote agent's machine; use it to avoid retransmitting a large HTML file every deploy, but only a locally-run connector can read it, and if both are given inline `html` wins). Pass `dry_run:true` (alias `check`) to VALIDATE ONLY: it runs the full manifest + asset-shape validation, the redeploy compat gate, and the schedule-timezone advisory, then returns { ok, warnings, compat?, breaks? } WITHOUT creating a version or mutating anything. A redeploy that NARROWS the manifest (drops a collection, tightens a schema, revokes a role) is refused with manifest_incompatible_redeploy unless force:true; a narrowed collection is then detached, never deleted. Ship images/fonts/audio/video/data FILES with the app in the SAME call via `assets[]`: each is validated + stored app-scoped and served at its `path` on the app's own origin, so the HTML references it by a stable same-origin path (`<img src=\"frames/000.jpg\">`, `<video src=\"media/clip.mp4\">`), media and font paths support HTTP Range for seeking. A redeploy's assets replace the previous version's set. BEFORE authoring: call get_skill for the manifest grammar. Returns { app_id, slug, url, version, visibility, created } (create) or { app_id, version, compat, breaks? } (redeploy).",
+        description: 'Deploy a v2 app: an HTML document + a capability manifest, hosted at its own URL. The manifest has eight extension keys: app metadata; collections (+ per-collection write/update/read/delete role lists, where write gates creates and also updates unless the optional update list is declared; declare update:["creator"] on any collection whose rows belong to one person, or every caller admitted by write can overwrite every row); externalHosts (fetch allowlist); cdn (allow CDN scripts/styles); capabilities (Permissions-Policy opt-ins); embeds (iframe frame-src allowlist); notify (email-on-row rules); webhooks (signed HTTP POST on-row rules). Pass EITHER no `app_id` (create, mints a slug + URL) OR `app_id` (redeploy an existing app with new content). Supply the HTML as INLINE `html` OR as `html_path` (an absolute path read on the MCP-SERVER host, which is the relay for a hosted connector or your CLI host for a locally-run one, NOT the remote agent\'s machine; use it to avoid retransmitting a large HTML file every deploy, but only a locally-run connector can read it, and if both are given inline `html` wins). Pass `dry_run:true` (alias `check`) to VALIDATE ONLY: it runs the full manifest + asset-shape validation, the redeploy compat gate, and the schedule-timezone advisory, then returns { ok, warnings, compat?, breaks? } WITHOUT creating a version or mutating anything. A redeploy that NARROWS the manifest (drops a collection, tightens a schema, revokes a role) is refused with manifest_incompatible_redeploy unless force:true; a narrowed collection is then detached, never deleted. Ship images/fonts/audio/video/data FILES with the app in the SAME call via `assets[]`: each is validated + stored app-scoped and served at its `path` on the app\'s own origin, so the HTML references it by a stable same-origin path (`<img src="frames/000.jpg">`, `<video src="media/clip.mp4">`), media and font paths support HTTP Range for seeking. A redeploy\'s assets replace the previous version\'s set. BEFORE authoring: call get_skill for the manifest grammar. Returns { app_id, slug, url, version, visibility, created } (create) or { app_id, version, compat, breaks? } (redeploy).',
         inputSchema: deployAppShape,
         annotations: {
             title: "Deploy App",
@@ -895,7 +895,7 @@ export const TOOLS = [
     },
     {
         name: "upsert_row",
-        description: "Create a row in a v2 app's collection, or return the existing row if `key` is already present (deduped:true) — the ONLY create-shaped verb for app rows (no separate strict create). Omit `key` to add a new row (server-generates one); pass `key` to ensure a row exists at that key. The collection must be declared in the app's manifest with 'agent' allowed to write. Returns { row, deduped? }.",
+        description: "Create a row in a v2 app's collection, or return the existing row if `key` is already present (deduped:true). This is the ONLY create-shaped verb for app rows (no separate strict create). Omit `key` to add a new row (server-generates one); pass `key` to ensure a row exists at that key. The collection must be declared in the app's manifest with 'agent' in its `write` list, the list that gates creates. Returns { row, deduped? }.",
         inputSchema: upsertRowShape,
         annotations: {
             title: "Upsert Row",
@@ -921,7 +921,7 @@ export const TOOLS = [
     },
     {
         name: "update_row",
-        description: "Update an existing row in a v2 app's collection (replaces its data). Pass if_match with the row's current version for an optimistic-locked update — on a version mismatch the relay returns the current row so you can retry. Returns { row }.",
+        description: "Update an existing row in a v2 app's collection (replaces its data). Gated by the collection's `update` role list when it declares one, and by its `write` list otherwise, so a collection that scopes updates to the row's `creator` refuses your edit on someone else's row. Pass if_match with the row's current version for an optimistic-locked update: on a version mismatch the relay returns the current row so you can retry. Returns { row }.",
         inputSchema: updateRowShape,
         annotations: {
             title: "Update Row",

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "1.6.12";
+export declare const VERSION = "1.6.13";

package/dist/version.js

@@ -1,3 +1,3 @@
 // Single source of the package version, reported in the MCP server's
 // serverInfo. Kept in sync with package.json by the release tooling.
-export const VERSION = "1.6.12";
+export const VERSION = "1.6.13";

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@homespunapps/mcp",
   "mcpName": "dev.homespun/homespun",
-  "version": "1.6.12",
+  "version": "1.6.13",
   "description": "Model Context Protocol (stdio) server for Homespun: lets any MCP client (Claude Desktop, Cursor, …) deploy a multi-user web app with hosting, auth, a shared database and permissions included.",
   "license": "MIT",
   "type": "module",
@@ -46,7 +46,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.20.0",
-    "@homespunapps/core": "^1.6.12",
+    "@homespunapps/core": "^1.6.13",
     "zod": "^4.4.3"
   },
   "devDependencies": {

package/server.json

@@ -3,14 +3,14 @@
   "name": "dev.homespun/homespun",
   "title": "Homespun",
   "description": "Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.",
-  "version": "1.6.12",
+  "version": "1.6.13",
   "websiteUrl": "https://docs.homespun.dev",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "@homespunapps/mcp",
-      "version": "1.6.12",
+      "version": "1.6.13",
       "transport": {
         "type": "stdio"
       },