MCP - Lace

Use Lace with Claude and your coding agent. When you resolve a comment in the Review canvas, it becomes a decision — a scoped change request with evidence, spatial context, screenshots, and a suggested fix. The Lace MCP server lets your agent search, filter, and act on those decisions — with full context about canvases and projects — so it sees exactly what needs to change and writes the code.

Connect in Claude

The fastest way to use Lace is the hosted connector at https://mcp.inlace.co. It runs in the cloud and reads your resolved decisions straight from your Lace account, so you don’t need the desktop app open.

Claude.ai
Claude Code

Open Settings → Connectors → Add custom connector.
Enter the URL https://mcp.inlace.co and click Add.
Click Connect and sign in with your Lace account.

Then start a chat and say “Search Lace decisions”.

claude mcp add --transport http lace https://mcp.inlace.co

The first call opens a browser to sign in with your Lace account. After that, say “Search Lace decisions”.

The hosted connector needs a Lace account and at least one resolved decision. Sign-in uses OAuth 2.0, so the first connection opens your browser.

Install from the CLI

Use the Lace CLI to register the right MCP transport for each editor. Claude Code uses the hosted OAuth connector so it can manage authentication in /mcp; Cursor and Codex use the local stdio server for editor-side installs.

Cursor
Claude Code
Codex CLI

Or install from the terminal:

npx lace-mcp install cursor

Restart Cursor, then open a new chat and ask about resolved Lace decisions.

npx lace-mcp install claude

Start a new Claude Code session, run /mcp, and authenticate Lace. Claude Code uses the hosted OAuth connector so its MCP menu can show tools, re-authenticate, clear authentication, reconnect, and disable.

npx lace-mcp install codex

Start a new Codex session and say “Search Lace decisions”.

Cursor and Codex local installs only work while the Lace desktop app is open and you’re signed in. The Claude Code hosted connector at mcp.inlace.co does not need the app open.

How it works

Resolve a comment

In the Review canvas, capture a screenshot, comment on UI elements, and resolve a comment into a decision. It persists with the screenshot, spatial context, and discussion.

Your agent queries Lace

It calls search_decisions to find relevant decisions, picks one, then calls apply_decision to get screenshots, element metadata, and step-by-step instructions.

The agent ships the change

It writes the code change and you review the diff.

Technical reference

MCP server

The Lace MCP server is registered under the name lace and exposes four tools — three for discovery and one for action.

Discovery tools

`search_decisions`

Search and filter resolved decisions with cursor pagination. With no parameters, returns the top 20 decisions ranked by recency. Use the filter parameters to narrow results by canvas, project, app, element, time range, and more. Parameters:

Parameter	Type	Default	Description
`query`	string	—	Text search across headline, body, and element text
`status`	`resolved` \| `suggested` \| `all`	`resolved`	Filter by annotation status
`limit`	number (1–100)	`20`	Results per page
`cursor`	string	—	Pagination cursor from a previous response
`sort`	`relevance` \| `resolved_at_desc` \| `created_at_desc`	`resolved_at_desc`	Sort order
`canvasId`	string (UUID)	—	Exact canvas ID
`canvasTitle`	string	—	Canvas title substring match
`canvasStatus`	`active` \| `archived`	—	Canvas status filter
`pageId`	string (UUID)	—	Exact page ID
`pageName`	string	—	Page name substring match
`projectId`	string (UUID)	—	Exact project ID
`projectName`	string	—	Project name substring match
`threadId`	string (UUID)	—	Filter by thread ID
`appName`	string	—	App name substring match
`windowTitle`	string	—	Window title substring match
`url`	string	—	URL substring match
`anchorState`	`anchored` \| `reanchored` \| `detached`	—	Anchor state filter
`elementEid`	string	—	Exact element accessibility ID
`elementRole`	string	—	Exact element ARIA role
`elementInteractivity`	boolean	—	Filter to interactive elements only
`minEndorsements`	number	—	Minimum endorsement count
`hasReplies`	boolean	—	Filter to decisions with replies
`createdBy`	string (UUID)	—	Creator user ID
`resolvedFrom`	string (ISO date)	—	Lower bound for resolved date
`resolvedTo`	string (ISO date)	—	Upper bound for resolved date
`createdFrom`	string (ISO date)	—	Lower bound for created date
`createdTo`	string (ISO date)	—	Upper bound for created date

All parameters are optional. Returns: a paginated list of decision summaries including headline, element info, canvas/project context, timestamps, and a nextCursor for the next page.

`list_canvases`

List review canvases in the current org. Returns title, project, page names, and decision counts per page. Use canvas titles and IDs to scope search_decisions queries. Parameters:

Parameter	Type	Default	Description
`status`	`active` \| `archived`	`active`	Canvas status filter
`projectId`	string (UUID)	—	Filter by project ID
`limit`	number (1–100)	`50`	Results per page
`cursor`	string	—	Pagination cursor

All parameters are optional. Returns: a list of canvases, each with id, title, status, project info, pages (with per-page decision counts), and timestamps.

`list_projects`

List projects in the current org. Returns name, chat count, and canvas count. Parameters:

Parameter	Type	Default	Description
`limit`	number (1–100)	`50`	Results per page
`cursor`	string	—	Pagination cursor

All parameters are optional. Returns: a list of projects, each with id, name, threadCount, canvasCount, and createdAt.

Action tools

`apply_decision`

Act on a resolved decision. Returns a multimodal response with page screenshots, element metadata, and step-by-step instructions. Control what’s returned with include. Parameters:

Parameter	Type	Default	Description
`id`	string	—	Decision ID from `search_decisions` (required)
`include`	`instructions` \| `crop` \| `discussion` \| `all`	`instructions`	What to return (see below)

include options:

instructions — full page screenshot + element metadata + step-by-step implementation instructions
crop — the full page screenshot plus a cropped element zoom for spatial grounding (falls back to full page only when no element region exists)
discussion — the chat discussion behind the decision; requires the canvas owner to enable chat sharing, otherwise returns empty
all — instructions, crop, and discussion combined

Config file locations

Tool	Config file
Claude Code	`~/.claude.json`
Cursor	`~/.cursor/mcp.json`
Codex CLI	`~/.codex/config.toml`

Troubleshooting

Hosted connector won't connect

Make sure you finished the browser sign-in step. The connector needs a Lace account, and you’ll only see results once you’ve resolved at least one decision.

Local install can't connect to Lace

The Lace desktop app must be open and signed in for the local npx install. Open the app and retry. (The hosted connector does not need the app open.)

No decisions returned

You need to resolve at least one comment first. Open Lace, switch to Review mode, comment on a UI element, and resolve it into a decision.

Agent doesn't recognize the MCP server after install

Restart your coding tool fully (quit and reopen), then confirm the Lace server appears in your MCP settings.

Screenshots are missing from decision details

For the local install, screenshots are stored alongside the Lace app data. If they were deleted or the app was reinstalled, the decision will still return card and targeting data but without images.

Privacy and terms

The Lace MCP server only reads your resolved decisions and never modifies your data. See our Privacy Policy and Terms. Questions or support: hello@inlace.co.

​Connect in Claude

​Install from the CLI

​How it works

​Technical reference

​MCP server

​Discovery tools

​search_decisions

​list_canvases

​list_projects

​Action tools

​apply_decision

​Config file locations

​Troubleshooting

​Privacy and terms

Connect in Claude

Install from the CLI

How it works

Technical reference

MCP server

Discovery tools

`search_decisions`

`list_canvases`

`list_projects`

Action tools

`apply_decision`

Config file locations

Troubleshooting

Privacy and terms