mcpField
L
Lightsync Pro

Lightsync Pro

Local
github.com/TagTeamDesignMedia & Design0Updated 34w ago

About Lightsync Pro

Lightsync Pro connects AI clients to a WordPress site’s LightSync Pro MCP endpoint for managing assets from Lightroom, Figma, Dropbox, and Canva with natural-language requests. The README documents token-based setup for several clients and supports connecting multiple sites.

Key features

  1. 01Connect through a tokenized MCP URL
  2. 02Configure Claude.ai, Claude Desktop, Cursor, and Windsurf
  3. 03Connect multiple WordPress sites
  4. 04Use Streamable HTTP or legacy SSE

Use cases

  1. 01Set up an AI client to connect to a WordPress site
  2. 02Connect multiple sites with separate tokens

MCP support

Lightsync Pro exposes an MCP endpoint on a WordPress site and documents Streamable HTTP and legacy SSE connection URLs. AI clients connect using a token in the URL.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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):

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

Markdown supported

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.