Sync Figma to Contentful: The Production-Grade MCP Integration Claude AI Actually Needs
15 minutes of setup. Zero manual exports after that. One natural language command to Claude, and your Figma assets land in Contentful with optimized metadata, proper compression, and a clear audit trail. That’s what a real MCP integration looks like.
If you’re building on Anthropic’s Model Context Protocol, you’ve probably noticed the gap between demo-quality MCP servers and tools that actually work in production. Most integrations look impressive in a README and fall apart the moment you need them for real work. LightSync Pro exists because Claude AI and MCP users deserve tools that connect AI agents to actual systems, not toy examples.
This guide walks through exactly how to sync Figma to Contentful using LightSync Pro’s MCP server. You’ll see the real setup flow, understand the security architecture that makes this possible, and learn the specific natural language commands that turn Claude into your asset management assistant.
The Real Cost of Manual Figma Uploads for Claude AI and MCP Users
Here’s the workflow most teams are stuck with: export from Figma, rename files to match your naming convention, compress images manually, upload to Contentful, add alt text, tag assets, update references in your content models. For a single design system update with 40 components, that’s easily two hours of repetitive work.
For MCP users specifically, the pain runs deeper. You’ve invested in building AI-powered workflows. You’ve connected Claude to your development environment, maybe your documentation system. But the moment you need to manage visual assets, you’re back to clicking through interfaces manually. The AI agent you’ve built can write code, analyze data, and reason through complex problems. It cannot, however, export a Figma frame and upload it to your CMS.
Until now.
The friction isn’t just time. It’s context switching. Every manual export breaks your flow. Every upload session pulls you away from the architectural thinking that MCP workflows enable. And every missed sync means your Contentful library drifts further from your source of truth in Figma.
LightSync Pro vs Your Other Options
There are a few ways Claude AI and MCP Users can move assets from Figma to Contentful. Here’s how they compare.
| Method | Setup | Ongoing effort | Auto-sync | Cost |
|---|---|---|---|---|
| LightSync Pro | 15 minutes | Zero | Yes | Free / $25 per month |
| Manual download and upload | None | 2-4 hours per week | No | Free (costs your time) |
| Zapier or Make | 2-3 hours | Occasional fixes | Partial | $20-100 per month |
| Custom development | Weeks | Ongoing maintenance | Yes | $2,000 and up |
If you’re syncing Figma to Contentful more than a few times per month, manual upload costs more in time than LightSync Pro costs in money. The math is not close.
Using Claude AI to Manage Your Figma to Contentful Sync
LightSync Pro’s MCP server is listed on the Anthropic registry as com.lightsyncpro/lsp. It’s one of the first production WordPress plugins with a working MCP integration, and it connects Claude directly to a live asset sync pipeline.
What does that mean in practice? You can talk to Claude in natural language and it will execute real operations on your Figma to Contentful sync. Not simulated responses. Actual syncs, actual status checks, actual bulk imports.
Natural Language Commands That Actually Work
Here are concrete examples of what Claude can do through the MCP connection:
- “Browse my Figma projects and show me what’s changed since Monday”: Claude queries your connected Figma account, identifies modified frames and components, and returns a structured report of what needs syncing.
- “Check which assets are unsynced and give me a report”: The sync map tracks every asset’s status across destinations. Claude can read that map and tell you exactly which files exist in Figma but haven’t reached Contentful yet.
- “Run a bulk import of the product icons to Contentful with AVIF compression”: One command triggers a full sync operation. Assets export from Figma, compress to AVIF format (40-60% smaller than JPEG), and upload to your Contentful space with proper metadata.
- “Optimize alt text on my last 20 synced images”: Claude can access the AI image SEO scoring feature to analyze recent uploads and generate or improve alt text based on actual image content.
Single-Token Multi-Surface Activation
Here’s a detail that matters for MCP users: when you connect LightSync Pro in Claude.ai, it automatically activates the AI agent inside your WordPress dashboard. No separate API key. No additional configuration. One authentication event enables both surfaces.
This patent-pending single-token activation has no identified prior art. It solves a real problem in MCP tool design, where users typically need to manage credentials in multiple places. Connect once, operate everywhere.
Why MCP Matters for This Workflow
Most tools that sync Figma to Contentful require you to learn a new interface, configure webhooks, and monitor dashboards. The MCP approach inverts that entirely. Claude becomes the interface. You describe what you want in plain English, and the sync happens.
For developers building AI-native workflows, this is the difference between adding another tool to your stack and extending the capabilities of the AI agent you’ve already built. Your Claude instance gains the ability to manage visual assets across your entire content infrastructure.
“MCP users aren’t looking for another dashboard to check. They want Claude to be the dashboard. When we built the Figma to Contentful sync, the goal was zero UI for the happy path. Tell Claude what you need, get a confirmation, move on. The visual interface exists for edge cases and debugging, not daily operations.”
Kyle, Founder of LightSync Pro
How LightSync Pro Connects Figma to Contentful
The architecture here matters, especially if you’re evaluating MCP tools for production use.
LightSync Pro uses a broker server that sits between your sources (Figma, in this case) and your destinations (Contentful). When you authenticate with Figma, those OAuth tokens live on the broker server. When you configure your Contentful space, those API credentials stay on the broker too.
Your WordPress installation, where the LightSync Pro plugin runs, never stores these credentials. It holds only a broker token that authorizes communication with the intermediary server. If your WordPress site were compromised tomorrow, attackers would find no Figma access tokens, no Contentful API keys, nothing they could use to access your cloud accounts.
This is the patent-pending broker architecture (US App. No. 19/440,404), and it’s why we can offer an MCP integration without the security concerns that would normally accompany giving an AI agent access to your design tools.
Step-by-Step: Setting Up Your Figma to Contentful Sync
The full setup takes under 15 minutes. Here’s the real flow:
Step 1: Install LightSync Pro
Download the free plugin from WordPress.org or grab it directly from lightsyncpro.com. Activate it in your WordPress dashboard. The plugin works as the control center for your sync operations, even if Contentful is a headless CMS separate from WordPress.
Step 2: Authenticate with the Broker
On first connect, you’ll see the broker authentication screen. This is a one-time process. You authenticate once, the broker stores your session, and you never handle OAuth credentials directly again. The credentials stay server-side.
Step 3: Connect Figma as Your Source
Figma is included in the free tier. Click to connect, authorize LightSync Pro to access your Figma account, and select the projects or teams you want to sync from. The plugin will index your available frames, components, and assets.
Step 4: Connect Contentful as Your Destination
Add Contentful as a destination. You’ll need your Space ID and a Content Management API token from Contentful. These credentials go to the broker, not your WordPress database. Select the content type and field where assets should land.
Step 5: Configure Your Sync Map
The sync map is where you define which Figma assets go to which Contentful entries. You can map by project, by frame, or by individual asset. The interface shows a fraction indicator (like 2/3) for assets synced to multiple destinations, making it clear what’s connected and what’s missing.
Step 6: Enable MCP Access (Pro Tier)
If you’re on the Pro tier ($25/month or $199/year), enable the MCP agent layer. Connect your Claude.ai account, and the single-token activation takes effect. Claude can now query and control your sync pipeline.
Step 7: Run Your First Sync
Trigger a manual sync to verify everything works. Watch the assets flow from Figma to Contentful. Check that metadata transferred correctly. Once confirmed, enable auto-sync to keep your libraries in continuous alignment.
The Broker Architecture: Why Security Matters Here
Let’s be direct about why this architecture exists.
MCP integrations give AI agents real capabilities. That’s the point. But real capabilities require real access, and real access to cloud services means API keys and OAuth tokens. The standard approach stores those credentials wherever the integration runs.
For WordPress plugins, that typically means the wp_options table, which is accessible to any plugin on your site, gets included in backups that might sit on less-secure storage, and becomes a target if your site is ever compromised.
The broker architecture eliminates this entire attack surface. Your WordPress site holds a broker token, nothing more. The broker server, which we control and secure, holds the actual credentials. All logging routes through a Logger::debug function that stays silent in production, ensuring no sensitive data appears in server logs.
Zero API keys in WordPress. That’s the security promise, and it’s what makes a production MCP integration responsible rather than reckless.
Key Features That Matter to Claude AI and MCP Users
Not every LightSync Pro feature matters equally for MCP workflows. Here’s what actually moves the needle:
Delta Detection That Works
The sync uses ETag and fileSize as checksums, not timestamps. This prevents false positives where unchanged files get re-synced unnecessarily. When Claude checks your sync Figma to Contentful status, it’s reporting actual changes, not timestamp drift from timezone differences or server clock skew.
AVIF Compression
Pro tier includes automatic AVIF conversion. Files shrink 40-60% compared to standard JPEG exports. For a Contentful space serving images to web applications, that’s meaningful bandwidth savings. And Claude can trigger compressed syncs with a single command.
Multi-Destination Fan-Out
One source asset can sync to multiple destinations simultaneously. Figma to Contentful and Shopify in a single operation. When Claude runs a bulk import, it pushes to every connected destination without separate commands for each.
AI Image SEO Scoring
The Pro tier includes AI-powered analysis of synced images. Claude can access this to generate alt text suggestions, identify images missing metadata, and produce optimization reports. Your Contentful assets get proper accessibility attributes without manual review.
Google Search Console Integration
Connect GSC to see how your synced images perform in search. Claude can pull this data to identify which assets drive traffic and which need attention. The MCP layer makes this queryable through natural language.
What Changes When the Sync Is Automated
The obvious change: you stop doing manual exports. But the second-order effects matter more.
Your Contentful library becomes trustworthy. When the sync runs automatically, triggered by changes in Figma or on a schedule, you know the asset library reflects current designs. No more “is this the latest version?” conversations. No more checking Figma to verify what’s actually in production.
The sync map’s fraction indicator shows the state of every asset at a glance. You see 3/3 and know an asset reached all destinations. You see 2/3 and know exactly where it’s missing. This visibility compounds over time. After a month of automated syncs, you have an audit trail of every asset movement.
With MCP access, you can query that history directly. “Show me everything synced to Contentful in the last week.” “Which assets failed and why?” “What’s the compression savings on my product images?” Claude can answer these questions by pulling from the sync logs and status maps.
There’s a practical quirk worth mentioning: on first Figma connect, you might see a token timeout. The fix is simple. Disconnect and reconnect once. This refreshes the broker token cleanly. It’s a known edge case, documented and resolved in about 30 seconds.
Frequently Asked Questions
Can Claude access my Figma files directly through the MCP connection?
Claude accesses your Figma files through LightSync Pro’s broker architecture. It can browse projects, view frame metadata, and trigger syncs. But the actual OAuth tokens stay on the broker server. Claude never has direct credential access, which is the security model that makes this integration production-safe.
Does the MCP integration work with Contentful’s content models?
Yes. When you configure Contentful as a destination, you specify which content type and asset field should receive synced images. LightSync Pro respects your Contentful schema. Synced assets land in the right place with proper references that your content models expect.
What happens if a sync fails while Claude is running a bulk import?
The sync system handles partial failures gracefully. Successfully synced assets stay synced. Failed assets get flagged in the sync map. Claude can report which specific assets failed and why. You fix the issue (usually a temporary API limit or network timeout) and re-run the sync for just the failed items.
Is the MCP server available on the free tier?
The MCP agent layer requires Pro tier ($25/month or $199/year). Free tier includes Figma as a source and manual sync capabilities, but the Claude AI integration and auto-sync features are Pro-only. The free tier is fully functional for teams who want to try the basic Figma to Contentful workflow before upgrading.
How does LightSync Pro handle Figma components versus frames?
Both components and frames can be synced. When you browse Figma through Claude or the dashboard, you see your full project structure. You can sync individual frames, entire pages, or specific components. The sync map lets you control granularity based on how your Figma files are organized.
Related Sync Guides
Get Started Free Today
The free tier includes Figma as a source, and you can connect Contentful as a destination immediately. Basic sync functionality works without payment. When you’re ready for MCP access, AI-powered features, and auto-sync, Pro tier runs $25/month or $199/year.
For agencies managing multiple client accounts, the Agency tier ($85/month or $699/year) provides 5 independent Pro licenses. Separate credentials, separate sync maps, separate destinations. Each license operates independently.
Download LightSync Pro Free and run your first Figma to Contentful sync in under 15 minutes. Then connect Claude and see what a production-grade MCP integration actually feels like.
LightSync Pro is built for people who are tired of demo-quality tools. The MCP server is real, listed on the Anthropic registry, and connects Claude to actual sync operations. Your Figma assets deserve better than manual exports. Your Contentful library deserves a single source of truth. And your AI workflows deserve tools that actually work.
About the Author: Kyle is the founder of LightSync Pro and has 16 years of experience running Tag Team Design, a full-service web agency. He built LightSync Pro to solve a real workflow problem for his partner, a working photographer, and has since turned it into a patent-pending platform used by photographers, designers, and agencies worldwide.
