Lsp

io.github.KyleTaggartPublished by GitHub account KyleTaggartv2.8.0Updated Oct 25, 2026

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

The publisher's own server: Lsp

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

A remote MCP endpoint for LightSync Pro that lets an assistant sync Lightroom, Figma, Dropbox and Canva assets into WordPress and Shopify.

What you can do
Sync creative assets from connected sources such as Lightroom, Dropbox, Figma and Canva into WordPress and Shopify through natural-language requests, per the description; no individual tools are listed in the manifest. Check the connection status of a configured site, which reports the site URL, plan and connected sources. Connect several WordPress sites at once, each with its own token, subject to a known client limitation with duplicate tool names.
When to use it
Useful when you run a WordPress site or Shopify store with the LightSync Pro plugin and want an assistant to move or publish assets from Lightroom, Figma, Dropbox or Canva without manual uploads.
Requirements
A remote Streamable HTTP endpoint on your own WordPress site (the plugin's MCP path), with an SSE legacy alternative. Requires the LightSync Pro plugin active on that site and a token from its AI & Tools → MCP Settings, passed in the connection URL. No local runtime or package needed.
Before you install
The token is placed in the connection URL, so treat the full URL as a secret and avoid sharing it. The server can write assets into WordPress and Shopify, so changes may go live on a production site; test on staging first. Asset data from connected services is sent to your site and through the MCP endpoint.

Installation

In SourceWeft

  1. Open Lsp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.KyleTaggart%2Flsp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lsp": {
      "type": "http",
      "url": "https://lightsyncpro.com/connect"
    }
  }
}

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):

json
{  "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:

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:

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:

json
{  "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:

json
{  "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.

Source: README.md at commit e3396a6

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.8.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Lightsyncpro integrations