This is a WordPress plugin that exposes an MCP endpoint for syncing design assets from Lightroom, Figma, Dropbox, and Canva into WordPress and Shopify stores. You authenticate with a token from the plugin settings, then use natural language to move images, graphics, and files between your creative tools and your content platforms. The connection works via Streamable HTTP at a wp-json endpoint, and you can wire up multiple WordPress sites simultaneously if you're managing staging and production environments. Useful if you're running an e-commerce workflow where designers hand off assets and you want to skip the manual upload dance.
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.
ray0907/git-mcp-server
cyanheads/git-mcp-server
io.github.b1ff/atlassian-dc-mcp-bitbucket
io.github.b1ff/atlassian-dc-mcp-jira
com.mcparmory/atlassian-jira
sirlordt/vscode-terminal-mcp