@scayver/specshot-mcp-server 0.13.0 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -179,6 +179,20 @@ Approved concepts (build a design SpecShot generated):
179
179
  - `update_concept_status({ conceptId, status: "sent" | "built", buildNote? })` — mark a build started or complete.
180
180
  - `add_build_note({ conceptId, note })` — log build progress on a concept.
181
181
 
182
+ Project tasks (tasks for people, the team's and the client's; your own queue stays `get_agent_tasks`):
183
+
184
+ - `list_project_tasks({ projectId, filter?, pageId?, limit?, offset? })`: the project's tasks with their status, assignee, due date and page. `filter` is `open` (the default), `mine`, `done` or `all`. Also the teammates a task can go to (never a viewer), the client's contacts, each page's due date and owner, the review rounds and the target launch. Read only.
185
+ - `create_project_task({ projectId, title, notes?, pageId?, assignee?, contactId?, dueOn?, status? })`: add a task. `assignee` is a teammate's userId or `client` (with `contactId` for a person at the client). Set a date or an assignee only when a person gave it to you. Read/write token.
186
+ - `update_project_task({ projectId, taskId, title?, notes?, status?, assignee?, contactId?, dueOn?, pageId? })`: change only the fields sent; `none` clears an assignee, a date or a page. Read/write token.
187
+ - `complete_project_task({ projectId, taskId })`: mark a task done. Read/write token.
188
+ - `set_page_schedule({ projectId, pageId, dueOn?, ownerUserId? })`, `set_round_due_date({ projectId, roundId?, dueOn })` and `set_target_launch({ projectId, targetLaunchOn })`: the dates beside the tasks; `none` clears one. The client sees the open round's date and the target launch. Read/write token.
189
+
190
+ Every change shows in the project's activity as your agent's. A task never moves a page or decides on one: approving and asking for changes stay with people.
191
+
192
+ The Etch site audit (run through the Etch Connector, like a build):
193
+
194
+ - `get_etch_audit({ remove?, scanPages? })`: a script that reads every page, template and component of the open Etch site and reports classes with no style record, SpecShot's own unused styles, stylesheets and components, where each SpecShot component is used, and assets outside a collection. It changes nothing unless `remove` names keys from a report's `removable` list that the person confirmed, and it never offers the site's own items.
195
+
182
196
  ## Build a full website wireframe (no AI key)
183
197
 
184
198
  Any connected LLM can build the whole site itself and save it back. Nothing calls an AI provider on the SpecShot side.