Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.
MCPpedia last refreshed this data
com.lightsyncpro/lsp is an MCP server that sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language. Its tool list has not been published yet over sse and http, requires no API key, and scores 60/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"lightsync-pro": {
"url": "https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN",
"type": "url"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in design / ecommerce
Design tokens from any live site: colours, type, spacing, components, drift against a baseline.
Draw and visually collaborate with your agents on tldraw's canvas.
MeiGen-AI-Design-MCP — Turn Claude Code / OpenClaw into your local Lovart. Local ComfyUI, 1,400+ prompt library, multi-direction parallel generation.
Image & PDF tools for AI agents: compress, convert, resize, PDF, AI vision, pipeline.
MCP Security Weekly
Get CVE alerts and security updates for com.lightsyncpro/lsp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Ready-to-use config snippets for connecting LightSync Pro MCP to your AI client.
Replace YOUR_TOKEN with the token from your LightSync Pro plugin settings under AI & Tools → MCP Settings.
In Claude.ai settings → Integrations → Add MCP Server:
https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN
This uses the Streamable HTTP transport — no additional setup required.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"lightsync-pro": {
"type": "url",
"url": "https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN"
}
}
}
Add to .cursor/mcp.json in your project root, or to the global config at ~/.cursor/mcp.json:
{
"mcpServers": {
"lightsync-pro": {
"type": "url",
"url": "https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN"
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"lightsync-pro": {
"type": "url",
"url": "https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN"
}
}
}
You can connect multiple WordPress sites simultaneously. Each needs its own token:
{
"mcpServers": {
"lightsync-main": {
"type": "url",
"url": "https://yoursite.com/wp-json/lsp-client/v1/mcp?token=TOKEN_1"
},
"lightsync-staging": {
"type": "url",
"url": "https://staging.yoursite.com/wp-json/lsp-client/v1/mcp?token=TOKEN_2"
}
}
}
Note: Claude.ai currently deduplicates servers with identical tool names. If connecting multiple sites in Claude.ai, this is a known limitation — the workaround is to use one site at a time via the connector URL.
After configuring, ask your AI client:
"Check my LightSync Pro connection status"
A successful response looks like:
{
"site_url": "https://yoursite.com",
"plan": "pro",
"connected": ["lightroom", "dropbox", "figma"]
}
If you get a 404, verify the plugin is active on your WordPress site and the token matches what's in the plugin settings.
For clients that require the SSE transport instead of Streamable HTTP:
https://yoursite.com/wp-json/lsp-client/v1/mcp/sse?token=YOUR_TOKEN
The SSE endpoint supports both GET (stream) and POST (message). Most modern clients should use the standard /mcp endpoint above.