Skip to main content
Glama

Ariadne

License: MIT MCP ariadne MCP server Awesome MCP Servers

아리아드네의 실 — 마이크로서비스 미로를 빠져나가는 길.

Spring Boot + TypeScript 마이크로서비스 스택을 위한 서비스 간 API 의존성 그래프입니다. AI 코딩 어시스턴트(Claude Code, Cursor, Windsurf)를 위한 MCP stdio 서버이며, CLI 버전도 제공합니다. 로컬 SQLite + TF-IDF를 사용하며, ML 의존성이 전혀 없습니다.

Ariadne 데모 — Spring PetClinic 마이크로서비스를 스캔하고 "owner"를 검색


기능

계약 계층(contract layer) — GraphQL 뮤테이션, REST 엔드포인트, Kafka 토픽, 프론트엔드 쿼리를 인덱싱합니다. 그 외의 것은 인덱싱하지 않으므로 결과가 AI 컨텍스트 윈도우에 적합합니다.

Claude에게 *"createOrder가 스택 전체에서 어디에 위치하는가?"*라고 물어보면 query_chains가 다음을 반환합니다:

Top Cluster #1  [confidence: 0.91]
  Services: gateway, orders-svc, billing-svc, web
  - [web]          Frontend Mutation: createOrder
  - [gateway]      GraphQL Mutation:  createOrder
  - [orders-svc]   HTTP POST /orders: createOrder
  - [orders-svc]   Kafka Topic:       order-created
  - [billing-svc]  Kafka Listener:    order-created → chargeCustomer

왕복 약 500 토큰입니다. 4개의 저장소에 걸쳐 grep -r createOrder를 실행하면 DTO, 테스트, 설정 파일 등에서 40개 이상의 일치 항목이 약 2000 토큰으로 반환되며, 계약 계층은 묻히게 됩니다.

지원: GraphQL · Spring HTTP/Kafka/RestClient · TypeScript Apollo/fetch/axios · Cube.js.


Related MCP server: TempoGraph

30초 만에 체험하기 (설정 불필요)

pip install ariadne-mcp
ariadne-mcp demo

spring-petclinic-microservices를 ~/.cache/ariadne-mcp/demo에 복제하고 스캔한 뒤, owner에 대한 최상위 클러스터(실제 서비스 간 호출 체인)를 출력합니다. 설정 파일이나 워크스페이스 설정이 필요 없습니다.


자신의 워크스페이스에 설치

pip install ariadne-mcp
cp "$(python -c 'import ariadne_mcp, os; print(os.path.join(os.path.dirname(ariadne_mcp.__file__), "ariadne.config.example.json"))')" ariadne.config.json
# edit ariadne.config.json (list the repos you want indexed)
ariadne-mcp install ariadne.config.json ~/your-workspace

Claude Code를 재시작하세요. install은 멱등성을 가지므로, 새 코드를 가져온 후 다시 실행하거나 stale_warning 발생 시 어시스턴트가 rescan을 호출하도록 하세요.


설정

{ "repos": [
    { "path": "../gateway" },
    { "path": "../orders-svc" },
    { "path": "../web" }
]}

스캐너는 각 저장소의 최상위 파일(pom.xml / build.gradle / package.json / SDL)을 통해 추론됩니다. 감지 테이블 및 재정의 구문은 docs/CONFIG.md를 참조하세요.


공개 샘플로 테스트

examples/spring-petclinic/ — 공개 spring-petclinic-microservices 샘플을 복제하고, 설정을 넣고, 스캔하고, 쿼리하세요. 1분 이내에 엔드투엔드로 재현 가능합니다.


아키텍처, MCP 도구, 점수 산정 방식, 피드백 부스트 → docs/ARCHITECTURE.md. 커스텀 스캐너(Go, Rust 등) → docs/CUSTOM_SCANNERS.md.

Available Tools

5 tools
expand_nodeA

One-hop neighbours of a known node (endpoint / Kafka topic / GraphQL operation / frontend call), with similarity scores and file paths. Read-only; no writes except a local exploration row if called within 10 min of a matching query_chains. Returns up to 3 matched source nodes × up to 10 neighbours (edges with score ≥ 0.08), plus a stale_warning field — call rescan if non-null.

Use AFTER query_chains when you already have a concrete node name and want to trace one hop further. Use query_chains (not this) when starting from a business term or when you don't yet know a node name. Partial, case-insensitive match against node id and raw_name; ambiguous inputs return multiple source groups.

Inputs: name (required).

query_chainsA

Query cross-service chains by business term or endpoint name. Returns candidate clusters of related GraphQL operations, HTTP endpoints, Kafka topics, and frontend queries across all services indexed by the local Ariadne DB. Use this when you need to understand which APIs, topics, or frontend operations are involved in a business feature.

Inputs: hint (required), top_n.

rate_resultA

Record whether Ariadne results were useful. Call this after using query_chains or expand_node to log feedback for future improvement. If node_ids is omitted after a recent query_chains call, Ariadne infers node_ids from hint + cluster_rank. Feedback is stored locally in feedback.db and survives DB rebuilds.

Inputs: hint (required), accepted (required), node_ids, cluster_rank.

rescanA

Refresh the Ariadne index from inside the conversation. Call this when query_chains or expand_node returned a stale_warning, or after you know the user's code has changed. Re-scans every repo listed in the install-time ariadne.config.json, rebuilds TF-IDF token edges, and invalidates cached DB handles so the next query sees fresh data. No arguments; zero configuration.

Inputs: no named parameters.

show_helpA

Return a quick setup and usage guide for Ariadne. Call this first when you are unsure how to use Ariadne, how to index your own microservices, or why query_chains returned no results. Always safe to call — no DB required.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: query_chains for discovery from a business term, expand_node for one-hop traversal from a known node, rescan for index refresh, rate_result for feedback, and show_help for guidance. The descriptions explicitly disambiguate the closest pair (query_chains vs expand_node) by stating when to use each. No two tools overlap in function.

    Naming Consistency4/5

    Four of five names follow a clear verb_noun pattern (expand_node, query_chains, rate_result, show_help). The lone 'rescan' is a bare verb without a noun object, a minor deviation that stays readable and consistent in style. Overall predictable and snake_case throughout.

    Tool Count5/5

    Five tools is well-scoped for a code-relationship exploration server, covering discovery, traversal, maintenance, feedback, and help. Each tool earns its place with no redundant or filler entries. The surface is focused rather than bloated.

    Completeness4/5

    The lifecycle is well covered: discovery (query_chains), traversal (expand_node), freshness (rescan), and feedback (rate_result) plus onboarding help. Minor gaps exist — e.g. no way to list indexed repos or enumerating all nodes — but core workflows are supported. A read-only exploration domain reasonably needs no create/update/delete operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      A TypeScript tool that ranks files in your codebase by importance, tracks dependencies, and provides file summaries to help understand code structure through Cursor's Model Context Protocol.
      14
      302
      -
    • A
      license
      A
      quality
      C
      maintenance
      Code graph context engine that parses codebases with tree-sitter (170+ languages), builds structural dependency graphs, and provides 24 MCP tools for code intelligence. One prepare_context call gives your AI agent the right files for any task. Includes focus, blast radius, hotspots, dead code detection, and hybrid search.
      24
      48 PyPI
      1
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Extract domain knowledge from codebases to reduce LLM token consumption by 20x and time in agentic search by 10x — gathers and makes concepts, naming conventions, and vocabulary queryable via MCP.
      19
      44
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Multi-language code-graph MCP server with 18 tools for structural code queries — find_symbol, callers, callees, blast_radius, dead_code, and cross-stack dataflow_trace from HTTP request through service layers to SQL. Tree-sitter parsing for Python, TypeScript, JavaScript, and Go; local-first, no API key required.
      18
      MIT