@formstr/mcp 0.4.0 → 0.5.1

package/README.md

@@ -2,8 +2,10 @@
 
 A standalone [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server that
 exposes the **Formstr** super-app (forms, calendar, pages, drive, polls) to any MCP host —
-Claude Code/Desktop, Cursor, and others. It builds on `@formstr/core` and the super-app's
-service layer and talks to Nostr relays directly. Transport: **stdio**.
+Claude Code/Desktop, Cursor, and others. It builds on `@formstr/agent` (the shared service
+layer + tool registry) and `@formstr/core` (Nostr primitives), and talks to Nostr relays
+directly. Transport: **stdio**. Source lives in
+[`formstr-hq/common-packages`](https://github.com/formstr-hq/common-packages/tree/main/packages/mcp).
 
 Identity is powered by [`@formstr/signer`](https://www.npmjs.com/package/@formstr/signer) —
 the same login engine the Formstr web app uses. Local keys are stored **NIP-49 encrypted
@@ -32,8 +34,8 @@ npm registry for a newer release:
 
 ```text
 $ formstr-mcp version
-@formstr/mcp 0.4.0
-Update available: 0.5.0 (you have 0.4.0).
+@formstr/mcp 0.5.0
+Update available: 0.6.0 (you have 0.5.0).
 Upgrade: npm install -g @formstr/mcp@latest
 Or just re-run via: npx -y @formstr/mcp@latest
 ```
@@ -41,7 +43,7 @@ Or just re-run via: npx -y @formstr/mcp@latest
 The update check is best-effort — if you're offline or the registry is unreachable it
 prints the installed version and a note, never an error. If you run the server via
 `npx -y @formstr/mcp` you already get the latest published version on each launch; pin a
-version (`@formstr/mcp@0.4.0`) in your host config if you'd rather control upgrades.
+version (`@formstr/mcp@0.5.0`) in your host config if you'd rather control upgrades.
 
 ## Sign-in
 
@@ -89,6 +91,12 @@ After `login`, no key belongs in the config:
 Add `"--allow-writes"` to `args` to enable the gated (destructive/outward) tools, and
 `"--relays", "wss://a,wss://b"` to override relays.
 
+> **Note:** the default (no `--allow-writes`) is _not_ read-only. Create/import tools
+> (`create_form`, `create_calendar_event`, `create_calendar`, `create_poll`, `create_page`,
+> `import_form_from_naddr`) are always enabled and publish events on your identity. The
+> flag gates the tools that modify or delete existing data or act toward other people
+> (update / delete / share / submit / RSVP).
+
 ### Passing the ncryptsec passphrase
 
 If your active account is an `ncryptsec` key (Create / Import login), the server needs its
@@ -224,9 +232,16 @@ actions; see the source under `src/tools/`.
 Destructive / outward tools are **not registered** unless `--allow-writes` (or
 `FORMSTR_ALLOW_WRITES=true`) is set, AND each such call additionally requires
 `"confirm": true`. Without `confirm`, the tool returns a structured "confirmation
-required" message naming the irreversible effect instead of executing. `share_form`
-distributes only the view key (read access) — never the signing key. Logging goes to
-stderr (stdout is the MCP transport).
+required" message naming the irreversible effect instead of executing.
+
+**Create tools are always on.** `--allow-writes` gates updates, deletions, shares,
+submissions, and RSVPs — not creation. Creating a new form/event/calendar/poll/page
+(and importing a form) publishes to relays on your identity even without the flag,
+because a fresh entity can't clobber existing data. If you need a strictly read-only
+server, don't connect an identity that matters.
+
+`share_form` distributes only the view key (read access) — never the signing key.
+Logging goes to stderr (stdout is the MCP transport).
 
 ## Tests