English Français العربية

com.lightsyncpro/lsp

Official registry E-commerce

Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http lsp 'https://lightsyncpro.com/mcp-connect'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "lsp": {
            "type": "http",
            "url": "https://lightsyncpro.com/mcp-connect"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Configuration Examples
  2. Claude.ai (Connector URL)
  3. Claude Desktop
  4. Cursor
  5. Windsurf
  6. Multiple Sites
  7. Verifying the Connection
  8. SSE Legacy Transport (Advanced)

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.

Frequently asked questions

What is com.lightsyncpro/lsp?

Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.

How do I install com.lightsyncpro/lsp?

It runs as a remote server. In Claude Code: claude mcp add --transport http lsp 'https://lightsyncpro.com/mcp-connect'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does com.lightsyncpro/lsp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is com.lightsyncpro/lsp open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains com.lightsyncpro/lsp?

It is published by TagTeamDesign. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.