Hi Figma team and community,

I am trying to use Figma MCP (Model Context Protocol) integration in VS Code, but I’m running into a persistent issue that prevents the connection from working.

Problem Description

When I configure mcp.json like this:

{ "inputs": [], "servers": { "figma": { "url": "https://mcp.figma.com/mcp", "type": "http" } } }

and start the server in VS Code, I get the following error:

Server exited before responding to `initialize` request. Error sending message to https://mcp.figma.com/mcp: Error: Protected Resource Metadata resource "https://mcp.figma.com" does not match MCP server resolved resource "https://mcp.figma.com/mcp". The MCP server must follow OAuth spec https://datatracker.ietf.org/doc/html/rfc9728#PRConfigurationValidation

Attempts to use SSE mode or a local proxy have not worked because VS Code MCP strictly validates the resource URL against the protected resource metadata. Any change to the URL (including using localhost or removing /mcp) results in either a 404 error or the same resource mismatch error.

Root Cause

Based on investigation:

• The .well-known/oauth-protected-resource file at https://mcp.figma.com/.well-known/oauth-protected-resource declares:

{ "resource": "https://mcp.figma.com" }

• However, the actual MCP endpoint is at https://mcp.figma.com/mcp.

• VS Code MCP enforces an exact match between the metadata resource and server URL, including protocol, domain, and path.

• This mismatch prevents any client from connecting until the metadata is updated.

Workarounds Tried

• Switching "type": "sse" in mcp.json → does not bypass the validation

• Local proxy rewriting metadata → VS Code MCP rejects non-matching host/protocol

• Removing /mcp from URL → breaks the actual endpoint

None of these approaches work because the client strictly follows RFC 9728 §5.2.2.

Request

It seems this is a server-side metadata issue. To fix MCP integration in VS Code:

1. Update the .well-known/oauth-protected-resource file to declare:

{ "resource": "https://mcp.figma.com/mcp" }

2. Ensure the resource metadata matches the MCP endpoint path exactly.

Additional Info

• VS Code version: [your version here]

• MCP extension version: [your version here]

• OS: [your OS here]

• MCP config:

{ "inputs": [], "servers": { "figma": { "url": "https://mcp.figma.com/mcp", "type": "http" } } }

Impact:

• Cannot use Figma Dev Mode + MCP in VS Code

• Blocks programmatic access to components, tokens, and design data via MCP

I hope the Figma team can update the metadata to resolve this issue so MCP integration works as intended.

Thanks in advance for any guidance!