@neopress/mcp 1.6.0 → 1.7.0

package/README.md

@@ -22,7 +22,10 @@ Stdio MCP can use `neopress_asset_upload_file` because it runs on the same
 machine as the agent and can read local file paths.
 
 The tool surface includes site/layout/page/collection/entry/form/asset/publish
-operations plus analytics queries and saved event/funnel configuration. Use
+operations, analytics queries and saved event/funnel configuration, plus custom
+domains, Search Console connection, billing handoffs, team management, form
+responses, entity history, saved-funnel results, selective publish, unpublish,
+and undeploy. Use
 `neopress_analytics_event_update` with `eventId` and `name` to rename an existing
 event without changing its historical tracking behavior; display changes use a
 separate call. Create a new event when tracking conditions need to change. Use
@@ -30,6 +33,15 @@ separate call. Create a new event when tracking conditions need to change. Use
 page and form targets. Event and funnel creation accepts the same camelCase
 definition inputs as the dashboard; reads preserve stored snake_case fields.
 
+The first-party API is the authorization boundary: all MCP calls re-check the
+current site membership, action-level work access, and plan entitlements. MCP
+access starts at Launch; Growth is required for deep analytics such as saved
+funnel results. Billing is Owner-only, while team and domain management require
+Owner/Admin. Consequential public, account, billing, team, delete, and restore
+tools advertise destructive/open-world annotations so supporting hosts can put
+them behind user approval. OAuth, DNS-provider credentials, checkout, and the
+billing portal remain user-completed handoffs.
+
 ## Remote HTTP
 
 Use this for hosted MCP clients that connect over Streamable HTTP.