Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Returns only the unit tests affected by your current Kotlin/Android code changes.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"ariadne": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/mikhailhal/ariadne:0.4.0"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add ariadne -- docker run -i --rm ghcr.io/mikhailhal/ariadne:0.4.0Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"ariadne": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/mikhailhal/ariadne:0.4.0"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"ariadne": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/mikhailhal/ariadne:0.4.0"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub MikhailHal, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.4.0) llegó al registro hace 3 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Reelsaw
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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".
git diff internallybrew 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 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.
Download ariadne- -all.jar from Releases (requires JDK 21+) and configure your client with "command": "java", "args": ["-jar", "/path/to/ariadne- -all.jar"].
git clone --recursive https://github.com/MikhailHal/ariadne.git
cd ariadne ./gradlew shadowJar # fat JAR: build/libs/ariadne- -all.jar
Once configured, AI agents can use the get_affected_tests tool:
get_affected_testsParameters:
project_path (required) — Path to the Kotlin projectscope (optional, deep | shallow, default deep) — how far back to look:base_branch (committed *and* uncommitted). Safest; the whole branch is covered so nothing you already committed slips through unverified. May select more tests.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:
Agent request:
{
"name": "get_affected_tests", "arguments": { "project_path": "/path/to/your/kotlin/project" } }
Response:
com.example.UserServiceTest.testCreateUser
com.example.UserRepositoryTest.testSave
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ MCP Client │ ──▶ │ ariadne │ ──▶ │ sazanami │ │ (Agent) │ │ (MCP Server)│ │ (Analysis) │ └─────────────┘ └─────────────┘ └─────────────┘ │ ▼ ┌─────────────┐ │ git diff │ └─────────────┘
git diff --unified=0 against base branchMeasured against Now in Android (Google's reference Android app — 34 modules, ~268 Kotlin files):
| Metric | Result |
|---|---|
| Recall audit — 19 target functions across all layers | 18/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 discovery | 34 modules via settings.gradle.kts, incl. nested modules and type-safe accessor dependencies |
| Source sets | main, 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:
core:common's asResult() selects 14 tests across three modules, including ViewModel tests reachable only through val uiState = ...stateIn(...)PopulatedNewsResource.asExternalModel() selects 14 tests, including 11 repository tests reachable only through .map(Type::mapper) chainsEvery 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 style | Selected |
|---|---|
| Plain unit tests (construct the object, call it) | 13 / 13 valid targets |
| Robolectric / Compose screenshot tests | 12 / 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.
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:
| Pattern | Status |
|---|---|
Framework-invoked callbacks — Fragment/Activity lifecycle (launchFragmentInContainer), lint Detector methods, Application.onCreate | Not traced: no call written in the test |
| Reflection / DI-container wiring | Not 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 sets | Not analyzed — reported explicitly in the tool response |
| Same-name top-level extensions in one package | Over-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.
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 #1Copyright 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.