# Framelink MCP for Figma vs UXKIN (slim)

> Framelink MCP for Figma scores 66.1 (B) to UXKIN's 57.4 (C) for design components. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-uxkin-agent.md (~4,750 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-uxkin-agent.json · canonical https://www.anchorterminal.com/compare/framelink-figma-mcp-vs-uxkin-agent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Framelink MCP for Figma scores 66.1 (B) on agent readiness against UXKIN's 57.4 (C), and leads in 4 of 7 scored categories. UXKIN leads on security & auth, maintenance & community and transparency & trust. Both do design components.

- Framelink MCP for Figma: B 66.1, rank #386 of 1486 · https://www.anchorterminal.com/tools/framelink-figma-mcp.min.md
- UXKIN: C 57.4, rank #794 of 1486 · https://www.anchorterminal.com/tools/uxkin-agent.min.md
- Framelink MCP for Figma, good for Reading a Figma frame into a coding agent to build matching UI. Ahead on Reliability, 68 against 45; Schema & documentation, 87 against 74; Agent ergonomics, 83 against 67; Payments & pricing, 60 against 12. Also Runs on your own machine; Open source.
- UXKIN, good for A coding agent doing front-end work that needs real examples of a flow or a website's colours and type before it builds. Ahead on Security & auth, 68 against 55; Maintenance & community, 76 against 41; Transparency & trust, 62 against 47. Also A hosted endpoint, with nothing to install.

| Category | Framelink MCP for Figma | UXKIN |
| --- | --- | --- |
| Reliability (16%) | 68 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 74 |
| Agent ergonomics (13%) | 83 | 67 |
| Security & auth (14%) | 55 | 68 |
| Payments & pricing (10%) | 60 | 12 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 41 | 76 |
| Transparency & trust (7%) | 47 | 62 |

| Fact (where they differ) | Framelink MCP for Figma | UXKIN |
| --- | --- | --- |
| Vendor | Framelink (Graham Lipsman) | UXKIN |
| Hosted endpoint | no (local only) | `https://uxkin.com/mcp` |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | Token | OAuth or key |
| Pricing | Free | Paid |
| Licence | MIT | Proprietary hosted service under UXKIN's terms of service (7 October 2026). The skills, plugins and configuration in uxkin/agent are MIT, copyright 2026 UXKIN. The screens in the library belong to the products they show |
| Tools exposed | 2 | 5 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `io.github.GLips/Figma-Context-MCP` | `io.github.uxkin/uxkin` |
| Last release | 2026-06-18 | 2026-10-16 |
| Terms last updated | no document linked | 2026-10-07 |
| Privacy policy last updated | no document linked | 2026-10-07 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 16k stars, 162k npm/wk | none |

Why the edge:
- Payments & pricing, Framelink MCP for Figma +48: Framelink MCP for Figma 60 (By the self-hosted rule. A free MIT package with nothing to buy (20 + 20 + 20), and no payment protocol (0). Figma API use falls under the user's own Figma plan. 60.); UXKIN 12 (No machine payment protocol (0 of 40). Plan prices are public, $9.99 a month or $99 once, with no per-call price (10 of 20). Searching needs a plan and no trial for the server was found. The skills are free, but they aren't the surface graded here (0 of 20). A person signs up and pays through Polar in a browser. Clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 12.)
- Maintenance & community, UXKIN +35: Framelink MCP for Figma 41 (Last release 0.13.2 on 18 June 2026, 141 days before this check (10). No release in the 90 days since 8 August (0). The maintainer merged his own pull requests through June and closed four outside pull requests between July and September, but the three open issues filed since May have no reply and seven outside pull requests from July to October are open without one (8 of 25). In the official MCP registry under the GitHub-verified namespace io.github.GLips, with 0.13.2 as the latest entry (15). CI and tests exist, and the MCP SDK is pinned at 1.29.0 with current dependencies (8 of 10). 10 + 0 + 8 + 15 + 8 = 41.); UXKIN 76 (Version 1.3.1 reached the official MCP registry on 16 October 2026, still the latest on 4 November (30). Repository commits to 2 November add distribution notes, VS Code listing images and an Open VSX publishing workflow, with no new tag or version. Six registry versions between 5 and 16 October (20). GitHub issues and pull requests couldn't be read from this session. Support is an email address and a contact form, and there's no public changelog (5 of 25). Listed in the official MCP registry as `io.github.uxkin/uxkin`, matching the repository owner (15). Three workflows (packaging checks, plugin scan, skill sync with uxkin.com) pin actions by commit, and their results weren't read (6 of 10). The service is about five weeks old. Total 76.)
- Reliability, Framelink MCP for Figma +23: Framelink MCP for Figma 68 (Read with the local-software lines, because the server runs on the user's machine and calls the Figma REST API. Installs from the official npm package figma-developer-mcp, with Node 20.20 or later stated in package.json (20). A CI workflow runs prettier, eslint, a type check and the vitest suite, but only on pull requests, and the five newest runs (outside pull requests from 22 August to 2 October) all failed, so passing on the default branch couldn't be confirmed (15). Eight open issues, the oldest open one a 429 rate-limit thread from November 2025 with 30 comments, and nothing open that reports a crash in the current release (18). Release-please changelog with semver tags and breaking defaults called out, such as the switch to `tree` output in 0.13.0 (15). Version 0.13.2, below 1.0 and not declared stable (0). 20 + 15 + 18 + 15 + 0 = 68.); UXKIN 45 (Read with the hosted lines, because the surface an agent uses is the MCP server at uxkin.com/mcp. UXKIN runs its own status page with four components (library and search, sign-in and accounts, AI app connection over MCP, payments) and 30 days of checks (20). On 4 November 2026 the page listed no incidents, with 100 per cent of checks passed for the library, 98.4 per cent for sign-in and the MCP connection and 99.74 per cent for payments over 30 days. A new status page that has never posted an incident is a short record (15 of 30). No rate limit with numbers is published. The terms say agent access may be limited (0 of 15). No 429, Retry-After or backoff guidance was found, though every tool is read-only (0 of 15). No SLA (0 of 10). The server carries no beta or preview label (10). 20+15+0+0+0+10 = 45.)
- Agent ergonomics, Framelink MCP for Figma +16: Framelink MCP for Figma 83 (Two compact tools (25). Output is sized by `nodeId` and `depth`, and the default `tree` format drops default values and auto-generated layer names and deduplicates repeated styles and subtrees. No pagination, which a single-file read rarely needs (16 of 20). Errors are written for a model to recover from, with Figma's 403 body surfaced and guidance for wrong node IDs from prototype, branch and FigJam links, per the 0.12.0 changelog (16 of 20). `get_figma_data` carries readOnlyHint and `download_figma_images` openWorldHint, with no destructiveHint on the tool that writes files and no note on overwriting (14 of 20). Only `fileKey` is required and one npx line starts it, but there is no SDK, which a two-tool local server doesn't need (12 of 15). 25 + 16 + 16 + 14 + 12 = 83.); UXKIN 67 (Five compact tools in a server card of 17,693 bytes with four prompts and output schemas, read on 4 November 2026 (25 of 25). `limit` sizes results and screenshots are off by default through `include_images`, with no paging or offset (12 of 20). No error codes or messages are documented. The 30 October reading of a 401 naming the resource metadata came from a request to the MCP endpoint, which this benchmark doesn't count, so it is struck (0 of 20). Every tool sets readOnlyHint and idempotentHint, and nothing writes (20 of 20). Each tool has at most one required parameter. No SDK, which an MCP server doesn't need, so 10 of 15. 25+12+0+20+10 = 67.)
- Transparency & trust, UXKIN +15: Framelink MCP for Figma 47 (MIT licence in the repository and on npm (30). No privacy policy or terms on framelink.ai or the docs. Design data goes from Figma to the local model client, and the docs describe what telemetry sends, but there is no data statement to agree with (8 of 30). No deprecation policy. Breaking defaults are called out in the changelog (5 of 20). Telemetry to PostHog (us.i.posthog.com) has been on by default since 0.10.0 on 10 April 2026. The configuration page discloses it with three ways to opt out, while the README doesn't mention it, and an open issue of 16 April 2026 reports that `error_message` can include file keys and node IDs, which the source's redaction (credentials only) doesn't cover (14 of 20). 30 + 8 + 5 + 14 = 57.); UXKIN 62 (The service is closed and the skills and plugins are MIT. The terms are clear on use, refunds and liability but name only 'UXKIN', with no legal entity, address or state, so it's unclear who the contract is with (12 of 30). The privacy policy gives retention for each kind of data, says search words from AI apps aren't stored and agrees with the README. No DPA (24 of 30). No deprecation policy, and the terms allow any part of the service to change or go at any time (0 of 20). Six service providers are named with what each does, with no data locations (14 of 20). Total 50.)
- Schema & documentation, Framelink MCP for Figma +13: Framelink MCP for Figma 87 (Both tools have typed zod input schemas in src/mcp/tools, with regex checks on fileKey, nodeId and fileName (25). docs.framelink.ai serves llms.txt and a Markdown copy of each page (10). The tool reference explains what each tool returns and how the two chain through `imageDownloadArguments`, and the `depth` parameter says not to use it unless the user asks. The `get_figma_data` description itself is one line and says nothing about when not to call it (14 of 20). Required fields and patterns are typed, and `fileName` must end in .png, .svg or .gif, with no enum for output format at call time (13 of 15). Config and request examples in the docs, a documented `Error fetching file:` prefix and purpose-built 403 and 429 messages, but no list of error cases (10 of 15). Semver releases and a public changelog (15). 25 + 10 + 14 + 13 + 10 + 15 = 87.); UXKIN 74 (The public server card gives every tool a typed JSON Schema input with `additionalProperties: false` and an output schema (25). No llms.txt (uxkin.com/llms.txt is 404). The skills are served as Markdown at /.well-known/agent-skills/ and the repository has llms-install.md (5 of 10). Tool descriptions say what each returns, how to phrase queries and when to use `get_journey` after a search, with less on when not to call (17 of 20). Inputs carry required fields, defaults and limits (`limit` 1 to 50 and 1 to 25) and no free-form objects (14 of 15). Descriptions and the MCP guide give query examples and a sample result. Error responses aren't documented (8 of 15, a partial kept for the examples). Versions 1.0.0 to 1.3.1 are in the registry and manifests, with no public changelog (5 of 15). Total 74.)