原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

ariadne

作者:MikhailHal版本 0.4.0i★ –i在你的电脑上运行
注册名称io.github.MikhailHal/ariadne

安装

概览

作者提供的说明(英文原文)

Returns only the unit tests affected by your current Kotlin/Android code changes.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "ariadne": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/mikhailhal/ariadne:0.4.0"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add ariadne -- docker run -i --rm ghcr.io/mikhailhal/ariadne:0.4.0

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "ariadne": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/mikhailhal/ariadne:0.4.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "ariadne": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/mikhailhal/ariadne:0.4.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 MikhailHal 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32606 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32606 个服务器的 19% 更新
  • 基础检查结果等于或优于此分类中其他 32606 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

ariadne 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.4.0)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Georgia MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新
安装

Georgia MCP

作者:abgeo

An MCP server for Georgian public data, read from the organizations that publish it.

电脑或云端今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

ariadne

MCP Server for Affected Test Selection

ariadne is an MCP (Model Context Protocol) server that provides AI agents with the ability to identify affected tests. Powered by sazanami, it analyzes code changes and returns only the tests that need to be run.

[!IMPORTANT]

## ⚠️ MUST READ: Speed over Completeness

ariadne is built for the agent inner loop — edit, verify, commit — where fast

feedback matters more than exhaustive selection. Static analysis cannot trace

every execution path: reflection, DI frameworks, and data-flow indirection

(e.g., Flux/MVI dispatch) can hide dependencies from any

affected-test-selection tool, not just ariadne.

Always keep a final line of defense in CI. Run the full test suite (or a

conservative selection) before merging. ariadne narrows what an agent runs

while iterating; it is not a replacement for CI.

When ariadne detects changes it cannot analyze (build scripts, resources,

unscanned source sets), it says so explicitly in the tool response instead of

silently reporting "no affected tests".

Features

  • MCP Integration — Works with Claude Code, Claude Desktop, and other MCP-compatible clients
  • Automatic Git Diff — No need to pass diff manually; ariadne runs git diff internally
  • Powered by sazanami — Uses Kotlin Analysis API for accurate static analysis

Installation

Homebrew (recommended)
brew install mikhailhal/tap/ariadne

Then register it with your MCP client — for Claude Code:

claude mcp add ariadne -- ariadne

Or add to your MCP client configuration manually (e.g., Claude Desktop):

{

"mcpServers": { "ariadne": { "command": "ariadne" } } }

Docker
docker run -i --rm -v /path/to/project:/workspace ghcr.io/mikhailhal/ariadne

Mount the project you want analyzed and pass /workspace as project_path. The image is also listed in the official MCP Registry as io.github.MikhailHal/ariadne.

Manual (release JAR)

Download ariadne- -all.jar from Releases (requires JDK 21+) and configure your client with "command": "java", "args": ["-jar", "/path/to/ariadne- -all.jar"].

Build from Source
git clone --recursive https://github.com/MikhailHal/ariadne.git

cd ariadne ./gradlew shadowJar # fat JAR: build/libs/ariadne- -all.jar

Usage

Once configured, AI agents can use the get_affected_tests tool:

Tool: get_affected_tests

Parameters:

  • project_path (required) — Path to the Kotlin project
  • scope (optional, deep | shallow, default deep) — how far back to look:
  • `deep` — all changes since base_branch (committed *and* uncommitted). Safest; the whole branch is covered so nothing you already committed slips through unverified. May select more tests.
  • `shallow` — uncommitted changes only (diff against HEAD). Fastest, for the tight edit loop. Verifying already-committed work is left to the caller. base_branch is ignored.
  • base_branch (optional, deep scope only) — Branch to compare against. When omitted, ariadne uses the repository's default branch (origin/HEAD). If that is not set (e.g. a repo with no remote), it returns an error asking you to pass base_branch explicitly rather than guessing.

Returns:

  • List of affected test FQNs (fully qualified names), sorted
  • If the diff contains changes outside the analyzed Kotlin sources (build scripts, resources, unscanned source sets), a note is appended recommending a full test run for those changes
  • Analysis is bounded by a 120s timeout; on timeout an explicit error is returned
Example

Agent request:

{

"name": "get_affected_tests", "arguments": { "project_path": "/path/to/your/kotlin/project" } }

Response:

com.example.UserServiceTest.testCreateUser

com.example.UserRepositoryTest.testSave

How It Works

┌─────────────┐     ┌─────────────┐     ┌─────────────┐

│ MCP Client │ ──▶ │ ariadne │ ──▶ │ sazanami │ │ (Agent) │ │ (MCP Server)│ │ (Analysis) │ └─────────────┘ └─────────────┘ └─────────────┘ │ ▼ ┌─────────────┐ │ git diff │ └─────────────┘

  1. Agent calls tool — Passes project path to ariadne
  2. Run git diff — ariadne executes git diff --unified=0 against base branch
  3. Analyze with sazanami — Build call graph and find affected tests
  4. Return results — List of test FQNs returned to agent

Real-World Validation: Now in Android

Measured against Now in Android (Google's reference Android app — 34 modules, ~268 Kotlin files):

MetricResult
Recall audit — 19 target functions across all layers18/18 valid targets detected (the 19th had no exercising unit test; correctly not selected)
End-to-end response time~4s (module discovery + call-graph build + BFS)
Module discovery34 modules via settings.gradle.kts, incl. nested modules and type-safe accessor dependencies
Source setsmain, debug, prod, benchmark, testDemo, … discovered per module (androidTest* excluded by design)

Verified patterns include repositories behind project interfaces, a library-interface override (androidx.datastore.Serializer), operator fun invoke use cases, @Composable functions, extension mappers, ViewModel property-initializer chains, and callable references. Two representative results:

  • Changing core:common's asResult() selects 14 tests across three modules, including ViewModel tests reachable only through val uiState = ...stateIn(...)
  • Changing the mapper PopulatedNewsResource.asExternalModel() selects 14 tests, including 11 repository tests reachable only through .map(Type::mapper) chains
Test-class selection rate

Every unit-test class in Now in Android was measured by changing a function in the class it tests and checking whether that test class was selected:

Test styleSelected
Plain unit tests (construct the object, call it)13 / 13 valid targets
Robolectric / Compose screenshot tests12 / 12
Framework-dispatched callbacks (lint Detector)0 / 2 — see below

Robolectric turned out not to be a barrier: those tests call the composable themselves (setContent { NiaTheme { ... } }), so the call exists in the source. What decides coverage is not the test runner but whether the test's own code contains the call.

What ariadne cannot see

The rule of thumb: if the framework calls your code instead of your test calling it, ariadne cannot connect them. These are limits of static analysis, not bugs — plan your CI safety net around them:

PatternStatus
Framework-invoked callbacks — Fragment/Activity lifecycle (launchFragmentInContainer), lint Detector methods, Application.onCreateNot traced: no call written in the test
Reflection / DI-container wiringNot traced
UDF dispatch (Flux/MVI)dispatch → collect is never an edge, but wiring in init (or a start() the test calls) is covered conservatively via constructor chains. Subscriptions started by DI/lifecycle are not covered (sazanami#38)
stateIn / shareIn chains (map, onEach, flatMapLatest, combine)Covered — verified with exact selection
Instrumented tests (androidTest*)Out of scope by design
Build scripts, resources, unscanned source setsNot analyzed — reported explicitly in the tool response
Same-name top-level extensions in one packageOver-selected (receiver types are not part of top-level FQNs) — safe direction
KMP source sets (commonMain, expect/actual)Enumerated, but resolution quality unverified (#1)

Full audit notes: sazanami#29, sazanami#38.

Requirements

  • JDK 21 or later
  • Git — For diff detection

Limitations

  • Module discovery is convention-based: it parses settings.gradle(.kts) includes, enumerates src/ /{kotlin,java} layouts, and reads project(":x") / type-safe accessor dependencies from build files. Dynamic includes, projectDir remapping, custom srcDirs, and dependencies injected by convention plugins are not detected — see #1
  • Full graph rebuild on each request (no caching yet); analysis is capped at 120s
  • See What ariadne cannot see for analysis-level gaps

License

Copyright 2025 ariadne contributors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

See LICENSE for the full text.

问 PopNx