Ext Ops Panel
Open dashboard
Comparison

StockSharp DesktopDriver vs PySide6 MCP

StockSharp DesktopDriver is an MCP server published by StockSharp. Marketplaces we read that list it: 1 (Official MCP Registry). PySide6 MCP is an MCP server published by com55. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplaceStockSharp DesktopDriverPySide6 MCP
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (PyPI): 159
Downloads/week (PyPI): 35
Forks (GitHub): 2
Stars (GitHub): 6
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

StockSharp DesktopDriver vs PySide6 MCP
FactStockSharp DesktopDriverPySide6 MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)6 (better)
Forks (GitHub) (differs)1 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (StockSharp.DesktopDriver.Mcp)On your machine (pyside6-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle2
LicenceNot statedNot stated
Repository (differs)github.com/stocksharp/desktopdriver.mcpgithub.com/com55/pyside6-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

StockSharp DesktopDriver

In its own words, on Official MCP Registry:

Inspect and drive Avalonia, WPF and MAUI desktop applications through local MCP.

PySide6 MCP

In its own words, on Official MCP Registry:

Playwright-style MCP to inspect, control, and debug PySide6 desktop GUIs.

How to run each

StockSharp DesktopDriver

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

Requires: STOCKSHARP_UI_ARTIFACTS, STOCKSHARP_UI_CATALOGUE

PySide6 MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio pyside6-mcp -- uvx pyside6-mcp

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

The marketplaces of PySide6 MCP publish no settings it asks for, so we do not compare settings.

What it can do: StockSharp DesktopDriver · What it can do: PySide6 MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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