1. Conduid
  2. Commerce
  3. com.lightsyncpro/lsp
MCP server · Commerce

com.lightsyncpro/lsp

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

Unclaimed commerce
34Low

Scored 6 months ago · breakdown

About com.lightsyncpro/lsp

com.lightsyncpro/lsp is an MCP server in the Commerce category: sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.

Install

From source
git clone https://github.com/TagTeamDesign/lightsync-pro

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about com.lightsyncpro/lsp

Powered by Claude · Grounded in docs

I know everything about com.lightsyncpro/lsp. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

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.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About com.lightsyncpro/lsp

How do I install com.lightsyncpro/lsp?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is com.lightsyncpro/lsp safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is com.lightsyncpro/lsp still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.