{
  "markdown": "# Configuration Examples\n\nReady-to-use config snippets for connecting LightSync Pro MCP to your AI client.\n\nReplace `YOUR_TOKEN` with the token from your LightSync Pro plugin settings under **AI & Tools → MCP Settings**.\n\n---\n\n## Claude.ai (Connector URL)\n\nIn Claude.ai settings → **Integrations** → **Add MCP Server**:\n\n```\nhttps://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN\n```\n\nThis uses the Streamable HTTP transport — no additional setup required.\n\n---\n\n## Claude Desktop\n\nAdd to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\\Claude\\claude_desktop_config.json` (Windows):\n\n```json\n{\n  \"mcpServers\": {\n    \"lightsync-pro\": {\n      \"type\": \"url\",\n      \"url\": \"https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN\"\n    }\n  }\n}\n```\n\n---\n\n## Cursor\n\nAdd to `.cursor/mcp.json` in your project root, or to the global config at `~/.cursor/mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"lightsync-pro\": {\n      \"type\": \"url\",\n      \"url\": \"https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN\"\n    }\n  }\n}\n```\n\n---\n\n## Windsurf\n\nAdd to `~/.codeium/windsurf/mcp_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"lightsync-pro\": {\n      \"type\": \"url\",\n      \"url\": \"https://yoursite.com/wp-json/lsp-client/v1/mcp?token=YOUR_TOKEN\"\n    }\n  }\n}\n```\n\n---\n\n## Multiple Sites\n\nYou can connect multiple WordPress sites simultaneously. Each needs its own token:\n\n```json\n{\n  \"mcpServers\": {\n    \"lightsync-main\": {\n      \"type\": \"url\",\n      \"url\": \"https://yoursite.com/wp-json/lsp-client/v1/mcp?token=TOKEN_1\"\n    },\n    \"lightsync-staging\": {\n      \"type\": \"url\",\n      \"url\": \"https://staging.yoursite.com/wp-json/lsp-client/v1/mcp?token=TOKEN_2\"\n    }\n  }\n}\n```\n\n> **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.\n\n---\n\n## Verifying the Connection\n\nAfter configuring, ask your AI client:\n\n> \"Check my LightSync Pro connection status\"\n\nA successful response looks like:\n\n```json\n{\n  \"site_url\": \"https://yoursite.com\",\n  \"plan\": \"pro\",\n  \"connected\": [\"lightroom\", \"dropbox\", \"figma\"]\n}\n```\n\nIf you get a 404, verify the plugin is active on your WordPress site and the token matches what's in the plugin settings.\n\n---\n\n## SSE Legacy Transport (Advanced)\n\nFor clients that require the SSE transport instead of Streamable HTTP:\n\n```\nhttps://yoursite.com/wp-json/lsp-client/v1/mcp/sse?token=YOUR_TOKEN\n```\n\nThe SSE endpoint supports both GET (stream) and POST (message). Most modern clients should use the standard `/mcp` endpoint above.\n",
  "bytes": 2669,
  "sha": "506abbf8ce0156db4d283c4c8cdd4e70af8011a825269418a9b6656c391a78f5",
  "repo_slug": "tagteamdesign/lightsync-pro",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_lightsyncpro_lsp_32607e18/readme"
}