Figma Context MCP
by GLips
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Runs on your computer★ 16,165MITUpdated 5 months ago
Install
Scry
Overview
Description from the maker (original English)
Search your team's Storybook components by text or image, so agents reuse what exists.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Design, images & audio
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.scrymore.com/mcpRun this in your terminal
claude mcp add --transport http scry https://mcp.scrymore.com/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"scry": {
"url": "https://mcp.scrymore.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"scry": {
"type": "http",
"url": "https://mcp.scrymore.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.scrymore.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account epinnock, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Design, images & audioi
- More stars than 0% of the other 2204 servers in this category
- Published to the registry more recently than 33% of the other 2204 servers in this category
- Basic checks equal to or better than 100% of the other 2204 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Scry safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Claude Real Video
by HUANGCHIHHUNGLeo
Let any LLM watch a video locally — and search everything it has ever watched.
Runs on your computer★ 2,284MITUpdated 2 months ago
Install
Figma MCP Server
by figma
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Runs in the cloud★ 2,152Updated 13 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Scry MCP Server
A spec-compliant remote MCP server on Cloudflare Workers that exposes multi-modal vector search over the Scry component database. Authenticates users via Firebase and issues its own OAuth tokens to MCP clients.
Compatible with Claude Desktop, ChatGPT, Cursor, and any MCP client via mcp-remote.
Architecture
Claude Desktop / ChatGPT / Any MCP Client│ │ (stdio via mcp-remote) ▼ mcp-remote (local proxy) │ │ (Streamable HTTP + OAuth 2.1) ▼ Cloudflare Worker ──────────────► Firebase Auth (upstream IdP) ├─ OAuthProvider (token mgmt) ├─ FirebaseAuthHandler (login UI + token verify) └─ ScryMCP (Durable Object) │ ▼ Scry Search API (Next.js) ├─ POST /api/search — vector search (text, image, hybrid) ├─ GET /api/image/... — image proxy (CDN auth) └─ POST /api/image/presign — presigned URL generation
The Worker acts as both an OAuth server to MCP clients (issuing its own tokens) and an OAuth client to Firebase (authenticating users upstream). The MCP client never sees the Firebase token.
Tools
| Tool | Description |
|---|---|
search_components | Text-based semantic + keyword hybrid search over UI components. scope: "project" (default) never widens; scope: "org" also returns opted-in, readable sibling projects' rows, marked crossProject. versions: "latest" (default) returns one result per screen (the newest indexed copy, with versionCount and a Versions: N indexed line); versions: "all" lists every indexed version |
search_by_image | Visual similarity search using base64 image input; same scope and versions semantics |
get_component_screenshot | Fetch a component screenshot (returns image block + presigned URL) |
generate_image | Gemini image generation (fast / quality), billed in AI credits; routed through Cloudflare AI Gateway when LLM_GATEWAY_URL is set |
whoami | Returns the authenticated user's info |
get_more_tools | Tell Scry what capability you needed that no tool offers (recorded for the team; nothing runs). Only with ANALYTICS_AGENT_ARGS="on" (staging and production) |
Issue resolution tools (stage; ISSUE_TOOLS_ENABLED="1")
Design-drift issues a human has promoted in the dashboard, resolvable in code or in Figma. All six call the dashboard's /api/agent/issues/* with a signed X-Scry-Caller (audience scry-dashboard-agent, claims sub = uid and agent_client = the MCP client's name); the dashboard checks membership and role and records actor_kind: "agent". Needs SCRY_DASHBOARD_API_URL, SCRY_AGENT_ASSERTION_SECRET (a secret shared only with the dashboard, separate from the search secret; unset = SERVER_MISCONFIGURED) and, for the protected stage dashboard, the SCRY_DASHBOARD_BYPASS_TOKEN secret. Writes are capped at 30/min/user on top of the 60 req/min limit.
| Tool | Description |
|---|---|
list_design_issues | Promoted issues in a project, filterable by link, Figma node, story, fix side, status, side status, severity, assignee, changed_since |
get_design_issue | One issue with both crops, Figma file key + node id, story + source files, expected value, tracks, last re-check, how to fix |
claim_design_issue | Claim (15-min lease) or release the code or design side |
mark_design_issue_fixed | Record a fix with a PR URL / commit / Figma version |
request_verify | Re-check now (free, 20/project/hour, 200/day) or rediff: true (10 credits) |
comment_design_issue | Timeline comment, optionally proposing a fix side |
Snip capture tools (stage; CAPTURE_TOOLS_ENABLED="1")
Screenshots the user took with Scry Snip, read by an agent ("fix the screenshot I just took"). Four tools, no more. They call the dashboard's /api/agent/captures/* over the same signed X-Scry-Caller hop and the same env vars as the issue tools; the dashboard decides who may read a snip (the owner, or an audience the owner turned on) and writes nothing about it to a log. Production has no flag until the feature's Gate B. delete_capture is capped at 10/min/user.
Every result starts with a text block (capture id, how old, who took it, size), then the picture (WebP, long edge at most 1280 px, about 70 KB, inlined only up to 75,000 bytes (about 100k base64 characters); both numbers live in src/captures/constants.ts as CAPTURE_AGENT_IMAGE), and a signed link to the original that expires in one hour. A picture that is over budget or cannot be fetched degrades to the link only. The Sync app produces the rendition; this server does no image processing.
| Tool | Description |
|---|---|
latest_capture | The caller's own newest capture in one project. Use once when the user says they just snipped something; never in a loop. maxAgeMinutes (default 15) widens the window |
get_capture | One capture by id (own, or shared with the caller) |
list_captures | Text list, newest first. scope mine (default) or shared, project_id, limit (max 50), before. Surfaces projectsTruncated and its note when the unscoped shared list hit the 50-project cap |
delete_capture | Permanently delete a capture the caller took (owner only) |
latest_clipboard | /sc: the newest item on the caller's shared clipboard from Scry Sync (a Scry Copy or the newest snip, whichever is newer). Optional project_id picks the snip's project |
latest_clipboard (feature mcp-clipboard) is registered only when SYNC_CLIPBOARD="on" as well (stage on, production "off" until the release; off or unset, the tool is not listed). It calls the dashboard's GET /api/agent/clipboard/latest, which answers 404 while the caller's sync-clipboard switch is off (CLIPBOARD_OFF, "Clipboard sharing is not on for your account.") and reads nothing else. The result is a text block (one-line summary, then the content labelled as untrusted data from the user's clipboard: text, else HTML, else RTF, cut at 60 000 characters, or 8 000 when a picture is attached, so the whole result stays under Claude Code's 25k-token tool-output cap: CLIPBOARD_TEXT in src/captures/constants.ts), then the picture (PNG, JPEG, WebP or GIF; any other type, an SVG say, is link-only; redirects are not followed) inline only up to the capture tools' budget (CAPTURE_AGENT_IMAGE.inlineMaxBytes, 75,000 bytes), else a line with its signed link (valid 5 minutes); a snip over the budget also says get_capture returns its agent picture. A snip item names its capture id for get_capture. An empty clipboard is a normal result; a dashboard 429 is RATE_LIMITED.
Errors are JSON {error, message, retryable} with isError: CAPTURE_STALE (newest is older than the window; carries its id and age), AMBIGUOUS_PROJECT (the message lists the projects), CAPTURE_NOT_READY (still uploading), CAPTURE_NOT_FOUND (a missing capture and one the caller may not see are byte-identical), CAPTURE_NOT_OWNER (delete), plus the generic RATE_LIMITED, SERVER_MISCONFIGURED, TIMEOUT, DASHBOARD_UNREACHABLE. The note a user typed is returned quoted and labelled as untrusted data. No log line carries a capture id, note, app name or URL.
Stock picture search (stage; STOCK_TOOLS_ENABLED="1")
One tool, search_stock(query, type?, provider?, limit?): a live search of free stock libraries (Pixabay, Unsplash, Openverse; Pexels when the service enables it) through the scry-stock Worker (STOCK_SERVICE_URL, secret STOCK_SERVICE_TOKEN). The call carries the service bearer, a 60-second X-Scry-Caller assertion with audience scry-stock (signed with SCRY_CALLER_ASSERTION_SECRET, the secret the stock Worker verifies) and the call's request id, and is abandoned after 3 s. Each result has provider, title, creditLine, creditParts (the credit as ordered {text, href?} parts), pageUrl, providerUrl, previewUrl, type, licenseLabel and licenseUrl, plus a status per provider. The text output prints the credit as markdown with its links (Unsplash photographer and Unsplash links carry the utm_source=scry pair), the licence as a link when the service gives a deed URL, a Sources: line, and the provider notices the terms require (Openverse: "made with Openverse, not endorsed or certified by Openverse"; Pexels: "Photos provided by Pexels"); the same notices are in structuredContent.notices. The tool description tells the agent to show the credit exactly as given, links included, and to open pictures on the provider's site. Nothing is stored, and the query is never logged: it travels only in the POST body, and the tool does not get the injected analytics context / conversation_id arguments (NO_AGENT_ARGS_TOOLS). Staging only; production sets neither variable, so the tool is absent there until the feature's Gate B. Source: src/stock/.
Errors are JSON {error, message, retryable} with fixed text per status (never the service's body): RATE_LIMITED, VALIDATION_ERROR, STOCK_TIMEOUT, STOCK_UNREACHABLE, STOCK_SERVICE_ERROR, STOCK_PROVIDERS_UNAVAILABLE, SERVER_MISCONFIGURED.
Usage analytics
Each tool handler invocation records one Workers Analytics Engine data point for use by the dashboard's staff-only KPI page. The only recorded values are the tool name (blob1), environment (blob2), and Firebase uid (blob3 and index1), plus double1 = 1 for counting. Missing environment/uid values become unknown and anonymous. No query text, prompts, image data, tokens, or other tool data is sent to Analytics Engine. Internal diagnostic logs do not add usage points. Missing or failing analytics bindings never affect tool responses.
The MCP_USAGE binding writes to scry_mcp_usage in production and scry_mcp_usage_staging in staging. Query production with the Analytics Engine SQL API (substitute the staging dataset name for staging):
SELECT blob1 AS tool, count() AS n FROM scry_mcp_usage WHERE timestamp > NOW() - INTERVAL '30' DAY GROUP BY toolAnalytics
Feature mcp-analytics. Every tool call produces ONE vendor-neutral event, mcp_tool_call.v1 (src/analytics/event.ts), built from an allow-list. The event goes to the sinks named in ANALYTICS_SINKS (comma-separated). The log sink is always on, whatever the value says (none, off and unset all mean log only), so keep it listed; an unknown name is ignored and logs one warning line.
| Sink | What it does | Where |
|---|---|---|
log | One schema-v1 line msg:"mcp_tool_call" (route = tool, status, ms, err_code, uid_hash, client = name/version). Joins the msg:"request" line by request_id. Default. | R2 log store (scry-logs.py --request-id) |
posthog | $mcp_tool_call, $mcp_initialize, $mcp_tools_list, $mcp_missing_capability and $exception through PostHog's MCP analytics SDK. No-op without the POSTHOG_PROJECT_TOKEN secret, and it refuses to start (one warning line) without the SCRY_LOG_SALT secret, because every event would be anonymous. A failed SDK load is retried after 60 s, one warning line per failure. | PostHog project 625583 (staging). Production sends nothing until Gate B |
What is collected: tool name, outcome, latency, error code, the confirmed project id, a salted hash of the user id (uid_hash, never the uid or email), MCP client name/version/protocol, the calling model when the client states it (Codex only), argument NAMES, the response SIZE, and a session id (the Durable Object id). PostHog also gets the agent's optional context sentence, scrubbed of emails, URLs and key-shaped strings and capped at 300 characters. Logs never carry it.
What is never collected: argument values, response bodies, image data, queries, raw uid, email, tokens.
Client labels (client name/version, protocol version, model) are sent only when they are a short safe token (letters
Only the beginning is shown; read the rest in the repo