[Requests and ideas] Connecting Figma's remote MCP server from the Copilot desktop app fails with ...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😔
**Category:** Requests and ideas
Connecting Figma's remote MCP server from the Copilot desktop app fails with Failed to register OAuth client. Figma allowlists MCP clients (VS Code, Cursor, Claude Code) — its registration endpoint returns 403 for anyone else, so Copilot's OAuth is rejected. Not a user/config/plan issue.
Please work with Figma to get the Copilot app added to their MCP Catalog/allowlist.
---
| Field | Value |
| --- | --- |
| App version | 1.0.5 |
| OS | macOS 26.5.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 5 |
Contributor guide
Research direction
Start from the Copilot desktop app's /chat path and reproduce the Figma remote MCP connection failure in app version 1.0.5. Confirm that Figma's registration endpoint returns 403 because Copilot is not allowlisted, then coordinate with Figma to add Copilot to its MCP Catalog/allowlist. Done means OAuth registration succeeds from the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- figma
- Domain
- authentication, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100