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.
Potencialize seu agente
A URL do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
https://lightsyncpro.com/connectO botão do Claude acima abre o Claude com o nome e a URL preenchidos. Você ainda precisa confirmar lá.
claude mcp add --transport http io.github.kyletaggart-lsp https://lightsyncpro.com/connectRun in a terminal.
{ "mcpServers": { "io.github.kyletaggart-lsp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://lightsyncpro.com/connect" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
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.
Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.
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.
Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.
{ "mcpServers": { "io.github.kyletaggart-lsp": { "url": "https://lightsyncpro.com/connect", "headers": {} } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração http para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Lsp é acessado por HTTP.
Última verificação: 2026-11-09. Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.