Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Compress, resize, crop, and convert images with the Tinify.dev API from any MCP client.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TINIFY_API_KEY, TINIFY_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tinify": {
"command": "npx",
"args": [
"-y",
"@tinify-dev/mcp"
],
"env": {
"TINIFY_API_KEY": "your-value",
"TINIFY_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add tinify --env TINIFY_API_KEY=your-value --env TINIFY_BASE_URL=your-value -- npx -y @tinify-dev/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tinify": {
"command": "npx",
"args": [
"-y",
"@tinify-dev/mcp"
],
"env": {
"TINIFY_API_KEY": "your-value",
"TINIFY_BASE_URL": "your-value"
}
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tinify": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tinify-dev/mcp"
],
"env": {
"TINIFY_API_KEY": "your-value",
"TINIFY_BASE_URL": "your-value"
}
}
}
}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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
TINIFY_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified against the domain tinify.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: TINIFY_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.7) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
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
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
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.
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.
MCP (Model Context Protocol) server for the Tinify.dev image API. Lets ChatGPT, Claude, Cursor, and other MCP clients compress, resize, crop, and convert images — with honest results.
You: compress the screenshots in ~/Desktop/launch/
Claude: 312.4 KB → 97.1 KB (-68.9%), wrote /Users/you/Desktop/launch/hero.min.png 84.2 KB → 84.2 KB — logo.png is already as small as Tinify.dev can make it (optimized: false), so no file was written.
optimized: false) instead of writing a byte-identical "optimized" copy. .min. beside the input, or to an explicit output_path. Replacing a file requires overwrite: true.Not affiliated with TinyPNG. This server talks to the Tinify.dev API.
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": { "tinify": { "command": "npx", "args": ["-y", "@tinify-dev/mcp"], "env": { "TINIFY_API_KEY": "tnf_live_..." } } } }
claude mcp add tinify -e TINIFY_API_KEY=tnf_live_... -- npx -y @tinify-dev/mcp
Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):
{
"mcpServers": { "tinify": { "command": "npx", "args": ["-y", "@tinify-dev/mcp"], "env": { "TINIFY_API_KEY": "tnf_live_..." } } } }
The same five tools are available as a hosted streamable-HTTP MCP server - no install, works from ChatGPT connectors, the claude.ai directory, and any registry that expects a URL:
Endpoint: https://api.tinify.dev/mcp
Auth: OAuth 2.1 (PKCE + dynamic client registration), or Authorization: Bearer tnf_live_... (or tnf_test_...)
Two ways to authenticate:
https://api.tinify.dev/mcp) and pick OAuth; the client discovers the authorization and token endpoints automatically from the server's .well-known metadata, registers itself, and opens a Connect Tinify page where you paste your Tinify API key. Your key stays the credential - the client only ever holds an opaque token that maps back to it server-side.Authorization: Bearer tnf_live_... (or tnf_test_...) and skip OAuth entirely. Unchanged.https://api.tinify.dev/mcp. Use Tinify to compress this image for the web. Show the original size,
result size, and percentage saved.
The hosted server cannot access local paths, so each image tool accepts exactly one of:
image — the ChatGPT attachment object. ChatGPT fills this automatically because the descriptor advertises openai/fileParams.image_base64 — a portable fallback for other MCP clients, capped at ~28 MB decoded.ChatGPT attachment downloads are HTTPS-only, reject private/reserved network targets and redirects, time out after 30 seconds, and are capped at the Tinify API's 40 MB limit. Successful operations return exact byte metrics and a temporary MCP result link. Existing base64 callers also receive structuredContent.image_base64 for backwards compatibility. get_usage is identical to the local version. Nothing is written to the user's filesystem.
Try it with curl:
curl -s https://api.tinify.dev/mcp \
-H "Authorization: Bearer tnf_live_..." \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
For local files, prefer the stdio server above - it reads and writes them directly with no base64 round-trip and no 28 MB cap.
This repository intentionally supports both OpenAI and Claude:
An OpenAI-only repository would duplicate the Tinify logic and make behavior drift more likely. OpenAI-specific descriptor metadata stays as a small additive layer in the hosted adapter; a separate repository is not needed.
For public OpenAI submission, set the portal-provided domain token as OPENAI_APPS_CHALLENGE_TOKEN in /etc/tinify/mcp-http.env and deploy the matching nginx location from deploy/nginx-location.conf. The endpoint returns only that token at /.well-known/openai-apps-challenge; do not commit the real portal token.
| Tool | Arguments | Does |
|---|---|---|
compress_image | path (absolute), output_path?, quality_mode? (balanced/best_quality/lossless), target_size_kb? (beta), overwrite? | Compresses PNG/JPEG/WebP/AVIF. Writes .min. beside the input. When the API returns optimized: false, nothing is written (unless you asked for an explicit output_path). |
resize_image | path, width?/height?/scale? (at least one), keep_aspect_ratio?, output_path?, overwrite? | Resizes and writes the result. |
crop_image | path, x, y, width, height, output_path?, overwrite? | Crops to a rectangle and writes the result. |
convert_image | path, format (avif/webp/jpeg/png), quality_mode?, output_path?, overwrite? | Converts formats (beta — the endpoint is rolling out server-side). Default output: .min. . |
get_usage | — | Plan, billing period, operations used and remaining. |
All image tools require absolute paths (MCP servers run with an unpredictable working directory) and pre-check the 40 MB API limit locally. API errors come back as readable tool errors with the error code and request_id to quote to support.
env block of your MCP config.get_usage to see the period end./Users/you/img.png, not ./img.png.~/Library/Logs/Claude/mcp-server-tinify.log.MIT © Stian Larsen
Cursor: Add to Cursor - then set your real key in Cursor's MCP settings.
VS Code:
code --add-mcp '{"name":"tinify","command":"npx","args":["-y","@tinify-dev/mcp"],"env":{"TINIFY_API_KEY":"tnf_live_..."}}'
Codex CLI:
codex mcp add tinify --env TINIFY_API_KEY=tnf_live_... -- npx -y @tinify-dev/mcp
or in ~/.codex/config.toml:
[mcp_servers.tinify]
command = "npx" args = ["-y", "@tinify-dev/mcp"]
[mcp_servers.tinify.env] TINIFY_API_KEY = "tnf_live_..."
Claude Code plugin (MCP + image-optimization skill):
/plugin marketplace add Stianlars1/tinify-claude-plugin
/plugin install tinify@tinify
More: https://tinify.dev/mcp