docs: Figma trademark compliance — rename to "Limitless MCP for Figma"#39
Merged
Conversation
Per Figma's brand guidelines (https://www.figma.com/using-the-figma-brand/): "Don't put our name (or part of our name) in your ... product name" — the permitted form is descriptive ("... plugin for Figma"). So the DISPLAY name "Figma Limitless MCP" (Figma as a name prefix) becomes the compliant descriptive "Limitless MCP for Figma" across the plugin manifests (Figma-menu name), READMEs, workspace + product AGENTS, AI-GUIDE, and the e2e script. The technical slug `figma-limitless-mcp` (manifest id, package names, MCP registration key) is kept — it's an identifier, not a consumer brand name, and changing it would break `claude mcp add figma-limitless-mcp`. Also: - Non-affiliation disclaimer added to both READMEs ("not affiliated with, endorsed, or sponsored by Figma; 'Figma' used descriptively; local/private tool, not distributed via Figma Community"). - Softened absolute "no rate limits" claims (which sat awkwardly against Developer Terms §4(e)'s reserved right to rate-limit) to the accurate "no REST rate limits — uses the local Plugin API". - GitHub repo description updated to the compliant name + "unofficial". Plugin's conduct was already within the Developer Terms for local/private use (§7 distribution obligations don't apply — non-distributed; no data exfiltration). This closes the naming/marketing gap surfaced by the audit. Not legal advice. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the project into line with Figma's brand/trademark guidelines and Developer Terms, surfaced by a provenance/ToS audit.
Why: Figma's guidelines say "Don't put our name (or part of our name) in your … product name" — the permitted form is descriptive ("… for Figma"). The display name "Figma Limitless MCP" used Figma's mark as a name prefix.
Changes (display name only — the
figma-limitless-mcpslug/MCP-registration key is unchanged):execute_codebridge can't pass Community review anyway).The plugin's conduct was already within the Developer Terms for local/private use (§7 distribution obligations don't apply — non-distributed, no data exfiltration). Docs/naming-only; plugin builds clean;
figma-limitless-mcpidentifier preserved soclaude mcp add figma-limitless-mcpstill works. (Not legal advice.)🤖 Generated with Claude Code