Command Palette

Search for a command to run...

UnylyUnyly
Browse all

LightSync Pro

FreeNot checked

Sync Lightroom, Figma, Dropbox, and Canva assets to WordPress and Shopify.

GitHubEmbed

About

Sync Lightroom, Figma, Dropbox, and Canva assets to WordPress and Shopify.

README

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 → IntegrationsAdd 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.

from github.com/tagteamdesign/lightsync-pro

Installing LightSync Pro

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/tagteamdesign/lightsync-pro

FAQ

Is LightSync Pro MCP free?

Yes, LightSync Pro MCP is free — one-click install via Unyly at no cost.

Does LightSync Pro need an API key?

No, LightSync Pro runs without API keys or environment variables.

Is LightSync Pro hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install LightSync Pro in Claude Desktop, Claude Code or Cursor?

Open LightSync Pro on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare LightSync Pro with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All design MCPs