Hey David, Gayani here from Figma. You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet. You can see the current list in our MCP catalog at figma.com/mcp-catalog. If you'd like Pi considered for a future addition, please fill out this form: forms.gle/qSvUawwznWyoj8….
原文
Gayani @ Figma on X: "Hey David, Gayani here from Figma. You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet. You can see the current list in our MCP catalog at https://t.co/T0hj2nTIWa. If you'd like Pi considered for a future addition, please fill out this form: https://t.co/Gl37eDGNVI."
@figma please fix thistoday in MCP land ... thing are better compared to a year ago, but also worse.- Hey David, Gayani here from Figma. You're right that our remote MCP server only accepts clients on our supported list, and Pi isn't on it yet. You can see the current list in our MCP catalog at figma.com/mcp-catalog. If you'd like Pi considered for a future addition, please fill out this form: forms.gle/qSvUawwznWyoj8….
- Hey @GayaniFigma , I think in spirit, when I created MCP, I envisioned an open ecosystem. That to me feels core. Seeing restrictions like this is sad and I hope Figma can get to a point where it’s more open or at least make the process of getting into the allowlist very easy.
Why should the specific harness that someone is using matter at all to the server? This is like making sure only Firefox can access your website - makes no sense at all.
