Skip to content

fix(core): configure Figma MCP OAuth client#38360

Open
rekram1-node wants to merge 4 commits into
v2from
figma-plugin
Open

fix(core): configure Figma MCP OAuth client#38360
rekram1-node wants to merge 4 commits into
v2from
figma-plugin

Conversation

@rekram1-node

@rekram1-node rekram1-node commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add a true built-in V2 plugin that supplies OpenCode's registered OAuth client ID for configured mcp.figma.com servers
  • have the plugin reapply configured Figma servers through the existing MCP service after plugin activation
  • preserve explicit client_id values and oauth: false
  • configure the Figma remote MCP server in the existing .opencode/opencode.jsonc

Root cause

The first V2 plugin mutated decoded config after MCP had already captured it, so the SDK attempted dynamic client registration and Figma returned plain-text 403 Forbidden. The plugin now updates configured Figma servers through MCP.add, without importing the plugin from MCP or adding a new plugin framework.

Testing

  • bun typecheck (packages/core)
  • bun test test/plugin/figma.test.ts (packages/core)
  • bun test test/mcp.test.ts (packages/core)
  • fresh development service: mcp list reports figma needs authentication
  • mcp auth figma emits a Figma authorization URL containing the registered client ID and waits for the loopback callback

Note

This carries the client ID from #32676 into V2 for checkout and team validation. The ID remains dependent on Figma approving OpenCode's OAuth client registration.

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.

1 participant