Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Taisly Agent KitFramelink MCP for Figma

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Google Search Console MCP Server for SEOsMCP100 RecommendedPlaywright MCPMCP100 RecommendedHugging Face MCPMCP100 RecommendedAsana MCPMCP100 RecommendedsanityMCP100 RecommendedNotion MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Taisly Agent KitShortlist candidate	Framelink MCP for FigmaMCP100 Recommended
Task fit
Best for	Using the repository's documented social-media posting workflow from an MCP-compatible agent	Providing coding agents with Figma node structure, styles, variables, and design assets needed for implementation
Not ideal for	Unattended campaigns, bulk engagement, moderation, or analytics requiring official platform guarantees	Replacing designer review or guaranteeing pixel-perfect production code from arbitrary files
Avoid when	Account credentials, draft content, audience selection, or platform-policy compliance cannot be reviewed before publishing	The connected Figma account exposes confidential files that should not be sent to the AI client
Provenance
Provenance details	Community implementation io.github.taisly · Publisher source ↗	Community implementation io.github.GLips · Publisher source ↗
Maintenance
Maintenance details	Repo: Jul 6, 2026 Package: Jul 6, 2026	Repo: Sep 18, 2026 Package: Sep 21, 2026
Popularity evidence
GitHub stars	255 GitHub stars · checked 2026-08-14T18:46:26.000Z	15,901 GitHub stars · checked 2026-09-24T04:14:16.257000Z
Package downloads / 30 days	No reliable download data	288,200 package downloads / 30 days · checked 2026-09-24T04:17:38.982000Z
Shared-package downloads / 30 days	589 shared-package downloads / 30 days (not MCP-specific) · checked 2026-08-14T18:46:26.000Z	Not documented
External adoption evidence	Not documented	npm: package downloads: 350,316Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Remote HTTP uses OAuth. Local setup stores a Taisly agent credential or uses TAISLY_API_KEY in ~/.taisly/config.json.	Uses a personal access token through FIGMA_API_KEY or X-Figma-Token, or an OAuth bearer token. HTTP also supports per-request token headers.
Cost	The package is free to install and has a free starting tier without a credit card. Paid plans exist, but exact prices are not in the reviewed README.	The MIT-licensed server lists no MCP fee. Figma plan and API limits, client, and model costs are separate.
Permissions	Connects social accounts and validates, publishes, schedules, lists, and checks videos across TikTok, Instagram, YouTube, X, Facebook, and other connected platforms. Local mode can read local videos.	Reads Figma file and node data through the Figma API and downloads PNG, SVG, or GIF assets into a configured local image directory; no Figma write capability is documented.
Data handling	Remote mode sends public video URLs, captions, schedules, account identifiers, and posting requests through Taisly and social platforms. Local stdio reads local video files; retention is not documented.	Figma metadata and API responses are returned to the MCP client; raw tools write figma-raw.json locally and image tools save assets locally. Telemetry sends server, platform, session, and event metadata by default; retention is not documented.
Limitations
Tradeoffs	A shared posting interface can reduce repetitive work, but credential handling and irreversible public actions create account, reputation, privacy, and platform-policy risk.	Structured design context reduces screenshot guesswork, but output quality still depends on file organization and granting access to Figma data.
Risk context	Posting and scheduling create external account changes. Follow the documented authenticate, validate, confirm, create flow; posts:create requires confirmed:true, and destinations, captions, and schedules need review.	Private design data and assets can reach the MCP client or model and local raw logs; telemetry adds metadata transmission. Protect tokens, restrict the image directory, and review downloaded and raw files.
Evidence date
Editorial review	2026-08-11	2026-08-11
Candidate evidence	2026-08-14T18:46:26.000Z	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →