Skip to content

docs: note browser permissions required for local MCP connection#136

Open
Taragryen wants to merge 1 commit into
ecomfe:mainfrom
Taragryen:docs/mcp-browser-permissions
Open

docs: note browser permissions required for local MCP connection#136
Taragryen wants to merge 1 commit into
ecomfe:mainfrom
Taragryen:docs/mcp-browser-permissions

Conversation

@Taragryen

Copy link
Copy Markdown

Background

Closes #135.

The local MCP WebSocket connection silently fails when the browser has not granted figma.com access to the local network. The TemPad Dev panel just stays Unavailable with no hint that a site permission is the cause.

Changes

  • Add a note in the Setup guide (after enabling the MCP server) explaining that Chrome's site permission popup for figma.com must have both Apps on device and Local network enabled for the local MCP connection to work.

@vercel

vercel Bot commented Jun 29, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the EFE Team on Vercel.

A member of the Team first needs to authorize it.

Co-Authored-By: Claude <noreply@anthropic.com>
@Taragryen Taragryen force-pushed the docs/mcp-browser-permissions branch from 5dd56c3 to 08bdd4d Compare June 29, 2026 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TemPad Dev MCP enabled in Figma UI but tools fail with NO_ACTIVE_EXTENSION

1 participant