StockSharp DesktopDriver

MCP开发工具

提供方 未标注

开发工具 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

Local MCP server for Avalonia, WPF and MAUI UI automation, control inspection, screenshots and testing. Browse StockSharp DesktopDriver MCP Server for...

一句话选型结论

按资料字段整理

StockSharp DesktopDriver 属于开发工具类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Development

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
StockSharp DesktopDriver当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

7.3 KB
来自项目仓库与上游目录的原文,未做删改

StockSharp DesktopDriver

Drive desktop applications built on Avalonia, WPF or MAUI from tests, from a command line, or from an AI
agent over MCP.

DesktopDriver reads the interface, not the screen. A table answers with its columns and rows, a tree with
its items, a workspace with its panels - in words that do not change with a theme, a font or a language.
Input goes through the toolkit's own pipeline, and only into a run that cannot reach anything real.
Pictures are there for a person to look at; tests check what the controls say.

How it works

  1. An application that can be driven references the bootstrap of its toolkit. Started the ordinary way it
    opens nothing. Started with --ui-automation, it opens a local named-pipe endpoint restricted to the
    current OS user, and writes where the endpoint is to the file named by --ui-automation-endpoint=.
  2. A runner - a test, the command line, the MCP server - starts the application that way (or attaches to
    one somebody else started), checks the product, instance and protocol in the session handshake and asks:
    which windows are open, what is in this one, what does this table show. It can then click, type, press
    keys and scroll, and wait for the answer to change.
  3. Adapters turn controls into what the protocol knows: grids, trees, lists, pickers, workspaces, charts,
    documents, diagrams. An application registers adapters for its own controls through the same
    interface the standard ones use.

NuGet packages

Install the CLI or MCP server with the .NET 10 SDK:```sh
dotnet tool install StockSharp.DesktopDriver.Cli --tool-path tools
dotnet tool install StockSharp.DesktopDriver.Mcp --tool-path tools


The commands are `tools/desktop-driver` and `tools/desktop-driver-mcp`. To add automation to an
application, reference the bootstrap package for its toolkit. To drive it from code, use the client,
runner and testing packages.

For MCP Registry publication and Claude Desktop extensions, see MCP distribution.

| Package | What it is |
|---|---|
| StockSharp.DesktopDriver.Contracts | The protocol: requests, answers, states, addresses |
| StockSharp.DesktopDriver.Runtime | Reading, identity, revisions and waiting, independent of any toolkit |
| StockSharp.DesktopDriver.Host | The endpoint inside the application, and `UiAutomationLaunch` to read how it was started |
| StockSharp.DesktopDriver.Client | The typed client every runner talks through |
| StockSharp.DesktopDriver.Runner | Starts, finds and reaches applications; the catalogue of what may be started |
| StockSharp.DesktopDriver.Testing | What an MSTest suite needs on top of the runner |
| StockSharp.DesktopDriver.Cli | The command line |
| StockSharp.DesktopDriver.Mcp | The MCP server, see its README |
| StockSharp.DesktopDriver.Avalonia | Avalonia: reading, input and pictures of the standard controls |
| StockSharp.DesktopDriver.Avalonia.ProDataGrid | Avalonia: the `DataGrid` from ProDataGrid, read as a table |
| StockSharp.DesktopDriver.Avalonia.Dock | Avalonia: a Dock.Avalonia workspace, read as panels and groups |
| StockSharp.DesktopDriver.Avalonia.Headless | Avalonia: input for headless tests |
| StockSharp.DesktopDriver.Bootstrap.Avalonia | Avalonia: one call that makes an application drivable |
| StockSharp.DesktopDriver.Wpf | WPF: reading, input and pictures of the standard controls |
| StockSharp.DesktopDriver.Bootstrap.Wpf | WPF: one call that makes an application drivable |
| StockSharp.DesktopDriver.Maui | MAUI: reading, input and pictures of the standard controls |
| StockSharp.DesktopDriver.Bootstrap.Maui | MAUI on Windows: one call that makes an application drivable |

## Make an application drivable

Avalonia, once the main window exists (the sample does the same with the
grid module alone):```csharp
public override void OnFrameworkInitializationCompleted()
{
    if (ApplicationLifetime is IClassicDesktopStyleApplicationLifetime desktop)
    {
        desktop.MainWindow = new MainWindow();

        if (UiAutomationLaunch.TryRead(desktop.Args) is { } launch)
        {
            _automation = AvaloniaAutomationBootstrap.Start(
                UiAutomationStartup.For("my.app", version, fixtureId: null, hasLiveOutsideWorld: false, isTestProfile: false),
                launch.EndpointFile,
                [binder => new DataGridAutomationModule(binder), binder => new DockAutomationModule(binder)]);
        }
    }

    base.OnFrameworkInitializationCompleted();
}

Dispose the returned runtime when the application exits. WpfAutomationBootstrap and
MauiAutomationBootstrap take the same arguments.

The sample applications show startup and shutdown for all three toolkits. The WPF
and MAUI Windows samples also have tests that start their executables, connect over the local pipe,
read their controls, send input and retrieve screenshots.

UiAutomationStartup.For decides whether input is allowed. An application that talks to nothing outside
its own process is always safe to click through. One that connects to something real - a broker, a
store, a service - is safe only when it was started on a test profile that replaces it; otherwise the
endpoint still reads, but every input is refused.

Many applications ship two builds: an ordinary one with no driver in it, and one made to be driven. The
driver is only referenced by the second, so the first has nothing listening by construction.

Drive it

From a test:```csharp
await using var app = await DrivenApplication.StartAsync(executable, extraArguments: null, TimeSpan.FromSeconds(60), cancellationToken);
await using var client = await app.ConnectAsync("my.app", cancellationToken);

var windows = await client.GetSurfacesAsync(cancellationToken);


From a command line, against an application somebody started with `--ui-automation`:```sh
tools/desktop-driver find --endpoint endpoint.json --kind grid
tools/desktop-driver grid-rows --endpoint endpoint.json --node window:MainWindow/Instruments --limit 5

desktop-driver with no arguments prints every operation.

From an agent: register the MCP server, see DesktopDriver.Mcp.

Its MCP name is StockSharp.DesktopDriver, and its display title is StockSharp DesktopDriver.

Documents

  • How the driver is built
  • The protocol
  • What answers for which control, and how to add an adapter
  • The command line
  • The MCP server
  • Builds, test suites and releases
  • Sample applications and Windows integration tests

Build and test```sh

dotnet build DesktopDriver.slnx
dotnet test DesktopDriver.Runtime.Tests --filter "FullyQualifiedName~Revision"


The MAUI projects need the MAUI Windows workload. MCP application tests, WPF screenshot tests and
`DesktopDriver.Windows.Tests` need an interactive Windows desktop session. Run the filtered suites
with hang and session timeouts using `./.github/scripts/Test.ps1 -Suite Headless` or `-Suite Desktop`
after a Release build.

## Packages from source```sh
dotnet pack DesktopDriver.slnx -c Release -o artifacts/packages

Sources instead of packages

A product checked out beside this repository can reference the projects themselves:xml <ProjectReference Include="..\DesktopDriver.Mcp\DesktopDriver.Bootstrap.Avalonia\DesktopDriver.Bootstrap.Avalonia.csproj" />

A product that builds a second, drivable copy of itself by passing a property on the command line adds
GlobalPropertiesToRemove="" to the reference: the driver has no build of its own for it, and
would otherwise be built twice into the same folder.

License

See LICENSE.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
StockSharp DesktopDriver 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

StockSharp DesktopDriver 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

StockSharp DesktopDriver 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

StockSharp DesktopDriver 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

StockSharp DesktopDriver 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

StockSharp DesktopDriver 能提供哪些能力?

资料显示能力标签包括 Development。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。