Ext Ops Panel
Open dashboard
Comparison

ty-python-lsp vs Locus

ty-python-lsp is a plugin bundle for AI coding tools published by andres-ortizl. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Locus is an MCP server published by paladini. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacety-python-lspLocus
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Downloads/month (npm): 154
Downloads/week (npm): 29
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

ty-python-lsp vs Locus
Factty-python-lspLocus
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@paladini/locus-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/andres-ortizl/ty-lsp-claude-code-plugingithub.com/paladini/locus-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

ty-python-lsp

In its own words, on Claude Code: claude-plugins-community:

Wires up Astral's ty, an extremely fast Python type checker, as an LSP server for Claude Code's built-in LSP tool. On .py / .pyi / .pyw files Claude can use hover (inferred types and docstrings), go-to-definition, go-to-implementation, find-references, document and workspace symbol search, and call hierarchy. Configuration is auto-detected from pyproject.toml; no extra LSP settings required. Requires ty on PATH (uv tool install ty or pip install ty).

Locus

In its own words, on Official MCP Registry:

Lightweight MCP server for LSP code intelligence — symbol lookup, refs, types, diagnostics.

How to run each

ty-python-lsp As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ty-python-lsp@claude-community

Locus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio locus-mcp -- npx -y @paladini/locus-mcp serve

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

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: ty-python-lsp · What it can do: Locus · 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.

Where the data comes from: how the catalog is built