Remote MCP returns “no edit access” on owned Design files through both Codex plugin and direct MCP
Read-only access through the Figma remote MCP server fails on two Figma Design files, while `whoami` succeeds with the expected account.
Environment:
- macOS 15.7.7, Apple Silicon.
- Codex desktop with the Figma plugin; also tested a separate direct MCP connection to https://mcp.figma.com/mcp using Codex CLI 0.162.1.
- `whoami` reports one plan: Starter, seat View, role admin.
Steps to reproduce:
1. Authenticate with Figma MCP.
2. Confirm identity with `whoami`.
3. Use a direct `/design/` URL and its node ID.
4. Call `create_session` and `get_metadata`. `get_screenshot` was also tested through the plugin.
Actual result:
The file tools return: “Looks like you don't have edit access to this file. The file owner can share it with you and make you an editor.”
The user confirmed owner/edit access in the Figma UI under the connected account. One file is in a team the account belongs to; the other is in that account's Drafts. URLs are Design URLs, not prototype or branch URLs.
Reconnecting the plugin did not resolve the issue. Separately authorizing the direct remote MCP connection succeeded, but `create_session` and `get_metadata` returned the same error there too. No successful file read was observed during this troubleshooting.
Expected result:
Read-only tools should work when permissions and the Starter/View allowance permit them. The published access documentation lists up to 20 monthly read-tool calls for Starter/View:
https://developers.figma.com/docs/figma-mcp-server/rate-limits-access/
Total server-counted monthly usage is unknown. Please investigate whether the error represents quota exhaustion, a permission check, or another issue. Do failed requests count toward the monthly allowance, and can quota exhaustion produce this edit-access message?
Debug UUIDs and affected file URLs can be supplied privately to Figma staff. They are omitted from this public report.
