Skip to main content
Glama
whyy9527

ariadne

by whyy9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ariadne

  • FileScopeMCP

    admica
    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
    -

  • TempoGraph

    Elmoaid
    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
    1
    AGPL 3.0

  • ontomics

    EtienneChollet
    A
    license
    A
    quality
    C
    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
    43
    MIT

Related Servers

  • ariadne mcp-server

    sazanami-lab
    A
    license
    A
    quality
    C
    maintenance
    ariadne is an MCP (Model Context Protocol) server that provides AI agents with the ability to identify affected tests.(including Android, Backend-Kotlin and more)
    1
    3
    Apache 2.0

  • oss-mcp

    Abbilville
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables cross-repository architecture discovery and dependency routing across multi-service codebases, with automated scanning and batch AST indexing for AI agents to trace request lifecycles and navigate service boundaries.
    5 npm
    MIT

  • polycodegraph

    smochan
    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.
    19
    MIT

  • gpkg-mcp

    truongtnn404
    F
    license
    Not graded
    quality
    D
    maintenance
    A knowledge graph MCP server for Moleculer and Go microservice projects that scans codebases, extracts service metadata, seeds Neo4j, and exposes tools for LLM clients to query and understand service architecture.
    -

  • servicegraph

    LM20230311
    A
    license
    Not graded
    quality
    B
    maintenance
    Local-first cross-service code intelligence engine for AI agents, connecting frontend, gateways, backend services, and databases to enable impact analysis and change planning.
    Apache 2.0
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

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
ResponsivenessResponsive

Resources