Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

ariadne

by MikhailHalversion 0.4.0i★ –iRuns on your computer
Registry nameio.github.MikhailHal/ariadne

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account MikhailHal, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32599 servers in this category
  • Published to the registry more recently than 19% of the other 32599 servers in this category
  • Basic checks equal to or better than 100% of the other 32599 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ariadne safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

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

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

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

Runs in the cloud★ 211Updated 2 days ago
Install

Zendesk

by pipeworx-io

Zendesk MCP Pack — tickets, users, organizations via OAuth.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Ask PopNx