The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Lsp listing page.
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.
In Claude.ai settings → Integrations → Add MCP Server:
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):
Add to .cursor/mcp.json in your project root, or to the global config at ~/.cursor/mcp.json:
Add to ~/.codeium/windsurf/mcp_config.json:
You can connect multiple WordPress sites simultaneously. Each needs its own token:
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:
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:
The SSE endpoint supports both GET (stream) and POST (message). Most modern clients should use the standard /mcp endpoint above.