English Français العربية

com.lightsyncpro/lsp

Registre officiel E-commerce

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

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

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

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  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.

Questions fréquentes

Qu'est-ce que com.lightsyncpro/lsp ?

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

Comment installer com.lightsyncpro/lsp ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http lsp 'https://lightsyncpro.com/mcp-connect'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour com.lightsyncpro/lsp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

com.lightsyncpro/lsp est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient com.lightsyncpro/lsp ?

Il est publié par TagTeamDesign. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.