About lsp
LightSync Pro connects AI clients to a WordPress site’s MCP endpoint for managing connected asset services. It supports Streamable HTTP and a legacy SSE endpoint, with separate tokens for multiple sites.
Key features
- 01WordPress MCP endpoint
- 02Streamable HTTP and legacy SSE
- 03Separate tokens for multiple sites
- 04Connection status check
Use cases
- 01Connect an AI client to a WordPress site
- 02Use separate connections for production and staging
MCP support
Exposes a token-protected MCP endpoint on WordPress for AI clients. Clients can use Streamable HTTP or the legacy SSE transport.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://lightsyncpro.com/mcp-connectclaude mcp add --transport http com-lightsyncpro-lsp https://lightsyncpro.com/mcp-connect{"mcpServers":{"com-lightsyncpro-lsp":{"type":"http","url":"https://lightsyncpro.com/mcp-connect"}}}Open in Cursor{"servers":{"com-lightsyncpro-lsp":{"type":"http","url":"https://lightsyncpro.com/mcp-connect"}}}Open in VS Code{"mcpServers":{"com-lightsyncpro-lsp":{"type":"http","url":"https://lightsyncpro.com/mcp-connect"}}}{"mcpServers":{"com-lightsyncpro-lsp":{"serverUrl":"https://lightsyncpro.com/mcp-connect"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEConfiguration 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.