flint vs com.lightsyncpro/lsp
flint is a plugin bundle for AI coding tools published by tryflint. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.lightsyncpro/lsp is an MCP server published by lightsyncpro.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  flint |  com.lightsyncpro/lsp |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.8.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | flint | com.lightsyncpro/lsp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.tryflint.com/mcp) | Remote server (lightsyncpro.com/mcp-connect) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/tryflint/claude-code-plugin | github.com/tagteamdesign/lightsync-pro |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 1 h ago, requires a key | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
flint
Build and manage websites with Flint's AI website builder through natural conversation.
com.lightsyncpro/lsp
Sync Lightroom, Figma, Dropbox & Canva assets to WordPress and Shopify via natural language.
How to run each
flint As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install flint@claude-communitycom.lightsyncpro/lsp As a remote MCP server
claude mcp add --transport http lsp https://lightsyncpro.com/mcp-connectCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only flint has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: flint · What it can do: com.lightsyncpro/lsp · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.