lace-mcp 0.0.2-alpha.11

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.
Files changed (4) hide show
  1. package/README.md +67 -0
  2. package/SKILL.md +23 -0
  3. package/dist/cli.js +22916 -0
  4. package/package.json +32 -0
package/README.md ADDED
@@ -0,0 +1,67 @@
1
+ # lace-mcp
2
+
3
+ MCP server for [Lace](https://inlace.co). Connects your coding agent to approved product decisions so it can see exactly what needs to change and ship the fix.
4
+
5
+ ## How it works
6
+
7
+ 1. You review your product in Lace and approve a decision on the [Decision Canvas](https://docs.inlace.co/concepts/decision-canvas)
8
+ 2. Your coding agent calls `list_decisions` to see what's been approved
9
+ 3. It calls `apply_decision` to get screenshots, element targeting, and step-by-step instructions
10
+ 4. The agent writes the code change and you review the diff
11
+
12
+ ## Install
13
+
14
+ ```bash
15
+ npx lace-mcp install claude
16
+ ```
17
+
18
+ Also supports `cursor`, `claude-desktop`, and `codex`:
19
+
20
+ ```bash
21
+ npx lace-mcp install cursor
22
+ npx lace-mcp install codex
23
+ ```
24
+
25
+ The Lace desktop app must be open and signed in for the MCP server to work.
26
+
27
+ ## MCP tools
28
+
29
+ | Tool | Description |
30
+ | --- | --- |
31
+ | `list_decisions` | Returns all approved decisions as a summary list |
32
+ | `apply_decision` | Everything needed to implement a decision: screenshots, targeting, and step-by-step instructions |
33
+ | `get_decision_detail` | On-demand detail for a decision: cropped element image, thread context, or both |
34
+
35
+ Use `apply_decision` when implementing. Use `get_decision_detail` only when you need a cropped element image or thread context.
36
+
37
+ ## Usage
38
+
39
+ Once installed, ask your coding agent:
40
+
41
+ ```
42
+ "List Lace decisions"
43
+ ```
44
+
45
+ Or to implement directly:
46
+
47
+ ```
48
+ "Implement the approved Lace decision"
49
+ ```
50
+
51
+ ## Requirements
52
+
53
+ - macOS
54
+ - [Lace desktop app](https://inlace.co) (open and signed in)
55
+ - Claude Code, Cursor, or Codex CLI
56
+
57
+ ## Docs
58
+
59
+ Full documentation at [docs.inlace.co](https://docs.inlace.co)
60
+
61
+ - [Getting started](https://docs.inlace.co/getting-started)
62
+ - [Decision Canvas](https://docs.inlace.co/concepts/decision-canvas)
63
+ - [MCP reference](https://docs.inlace.co/reference/mcp)
64
+
65
+ ## License
66
+
67
+ Proprietary
package/SKILL.md ADDED
@@ -0,0 +1,23 @@
1
+ ---
2
+ name: lace
3
+ description: Use when implementing approved Lace decisions, applying approved UI changes, or checking what changes have been approved in the Lace overlay
4
+ ---
5
+
6
+ # Lace — Approved Decision Implementation
7
+
8
+ Lace surfaces adoption insights as actionable decisions. When a decision is approved in the Lace overlay, this skill turns it into a code change.
9
+
10
+ ## Steps
11
+
12
+ 1. Call the `list_decisions` MCP tool to see all approved decisions.
13
+ 2. If there is exactly one decision, proceed with it. If there are multiple, ask the user which one to implement.
14
+ 3. Call the `apply_decision` MCP tool with the chosen decision ID.
15
+ 4. Follow the implementation instructions returned by `apply_decision` exactly — they include screenshots, element targeting, and constraints.
16
+ 5. Implement the minimal code change described. Do not refactor or modify anything outside the target element.
17
+ 6. If you need a cropped image of a specific UI element (e.g., for embedding in a prototype), call `get_decision_detail` with the decision ID and `include: "image"`.
18
+ 7. If you need to understand why a decision was made or what alternatives were considered, call `get_decision_detail` with the decision ID and `include: "context"`.
19
+
20
+ ## Troubleshooting
21
+
22
+ - If `list_decisions` returns an authentication error, tell the user to run `npx lace-mcp install <editor>` to re-authenticate.
23
+ - If no decisions are returned, the user may need to approve a decision in the Lace overlay first.