
Lsp
- Updated March 6, 2026
- TagTeamDesign/lightsync-pro
LightSync Pro LSP is a MCP server that syncs Lightroom, Figma, Dropbox, and Canva assets to WordPress and Shopify via natural language over streamable HTTP.
About
LightSync Pro LSP (com.lightsyncpro/lsp) is a remote Model Context Protocol server that moves assets from Lightroom, Figma, Dropbox, and Canva into WordPress and Shopify using natural language inside your agent. ecommerce and content developers often lose hours exporting, renaming, and uploading the same hero images and brand files; this MCP centralizes that handoff behind one HTTP remote. During build, you register lightsyncpro.com/mcp-connect in Claude Code or Cursor, connect your LightSync Pro accounts for the listed sources and destinations, and let the agent orchestrate sync steps instead of clicking through each platform. Version 2.8.1 signals an actively maintained connector. It complements storefront skills: you still own theme and merchandising decisions, while LSP handles cross-tool asset delivery. Skip it if your stack is headless-only with no WordPress or Shopify, or if you do not use the supported design sources.
- Syncs Lightroom, Figma, Dropbox, and Canva into WordPress and Shopify
- Natural-language asset workflows over streamable-http at lightsyncpro.com/mcp-connect
- Server version 2.8.1; repo github.com/TagTeamDesign/lightsync-pro
- Remote MCP—no local daemon required for the published connector
- Creative-to-store pipeline MCP, not a theme codegen skill alone
Lsp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http lsp https://lightsyncpro.com/mcp-connectAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
| Last updated | March 6, 2026 |
| Repository | TagTeamDesign/lightsync-pro ↗ |
What it does
Sync creative assets from Lightroom, Figma, Dropbox, and Canva into WordPress and Shopify stores using natural-language commands through MCP.
Who is it for?
Best when you're running WordPress or Shopify and already work in Figma, Canva, Dropbox, or Lightroom and want agent-driven asset publishing.
Skip if: Pure API backends with no WordPress/Shopify, or teams that only need Git-based static assets without creative-cloud connectors.
What you get
After you connect LightSync Pro and add the MCP remote, agents can trigger cross-platform asset syncs from a single conversational workflow.
- Agent-orchestrated uploads and syncs into WordPress or Shopify
- Unified NL control across four creative sources and two commerce targets
By the numbers
- Server version 2.8.1
- Four creative sources and two publish targets named in description
- Single streamable-http remote: lightsyncpro.com/mcp-connect
README.md
Configuration Examples
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.
Claude.ai (Connector URL)
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.
Claude Desktop
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"
}
}
}
Cursor
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"
}
}
}
Windsurf
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"
}
}
}
Multiple Sites
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.
Verifying the Connection
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.
SSE Legacy Transport (Advanced)
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.
Recommended MCP Servers
How it compares
Multi-source creative sync MCP, not a one-way image optimizer or static site generator skill.
FAQ
Who is LightSync Pro LSP for?
Developers and small teams on WordPress or Shopify who want agents to move assets from Lightroom, Figma, Dropbox, or Canva without manual uploads.
When should I use LightSync Pro LSP?
Use it while building or refreshing storefronts and content sites when design sources and live CMS assets must stay in sync.
How do I add LightSync Pro LSP to my agent?
Add the streamable-http remote https://lightsyncpro.com/mcp-connect in your MCP client and complete LightSync Pro account linking for your sources and stores.