Ext Ops Panel
Open dashboard
Comparison

origin-mcp vs LMCP

origin-mcp is an MCP server published by Ge-Shun. Marketplaces we read that list it: 1 (PyPI (MCP servers)). LMCP is an MCP server published by local-mcp.com. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers), Community GitHub marketplaces). 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

Where each is published
Marketplaceorigin-mcpLMCP
PyPI (MCP servers) Listed
Version: 0.1.4
Downloads/month (PyPI): 603
Downloads/week (PyPI): 180
Forks (GitHub): 9
Stars (GitHub): 153
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.0.442
Downloads/month (npm): 13 815
Downloads/week (npm): 7 040
Forks (GitHub): 11
Stars (GitHub): 79
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.0.442
Downloads/month (npm): 13 815
Downloads/week (npm): 7 040
Forks (GitHub): 11
Stars (GitHub): 79
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

origin-mcp vs LMCP
Factorigin-mcpLMCP
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)153 (better)79 (worse)
Forks (GitHub) (differs)9 (worse)11 (better)
Last release (differs)Not published2026-11-09
Where it runs (differs)On your machine (origin-mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)Not a bundle16
LicenceMITMIT
Repository (differs)github.com/ge-shun/origin-mcpgithub.com/colibird-ai/local-mcp-releases
Changes in the last 7 days (differs)013
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 45 h ago returned HTTP 200

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

origin-mcp

In its own words, on PyPI (MCP servers):

Local MCP server that lets AI assistants automate Origin/OriginPro for data import, worksheet editing, plotting, analysis, and export on Windows.

LMCP

In its own words, on Official MCP Registry:

Mac & Windows: let ChatGPT, Claude & Cursor use your email, calendar, iMessage, Teams, files.

How to run each

origin-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

LMCP As a remote MCP server

Claude Code
claude mcp add --transport http local-mcp https://local-mcp.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only LMCP 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

The marketplaces of origin-mcp publish no settings it asks for, so we do not compare settings.

What it can do: origin-mcp · What it can do: LMCP · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built