@lovable.dev/mcp-js vs io.github.VomeshAtukuri/copilot-mcp
@lovable.dev/mcp-js is an MCP server published by @lovable.dev. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.VomeshAtukuri/copilot-mcp is an MCP server published by VomeshAtukuri. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 | ||
|---|---|---|
| npm registry (MCP servers) | Listed Version: 3.4.0 Downloads/month (npm): 1 432 879 Downloads/week (npm): 546 524 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | @lovable.dev/mcp-js | io.github.VomeshAtukuri/copilot-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | 2026-10-30 | Not published |
| Where it runs (differs) | On your machine (@lovable.dev/mcp-js) | Remote server (copilot-mcp--0000001.gentlesea-14833e94.westus2.azurecontainerapps.io/mcp) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/lovablelabs/lovable | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 400 |
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
@lovable.dev/mcp-js
Author MCP servers for Lovable apps. Declare tools with defineTool, register them in defineMcp, and a framework adapter (TanStack or Supabase Edge Functions) emits the route(s) at build time.
io.github.VomeshAtukuri/copilot-mcp
MCP server for web development with Khoros, Gainsight, and HigherLogic integrations.
How to run each
@lovable.dev/mcp-js
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.VomeshAtukuri/copilot-mcp As a remote MCP server
claude mcp add --transport sse copilot-mcp https://copilot-mcp--0000001.gentlesea-14833e94.westus2.azurecontainerapps.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.VomeshAtukuri/copilot-mcp 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: @lovable.dev/mcp-js · What it can do: io.github.VomeshAtukuri/copilot-mcp · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.