Skip to main content
Glama
Flux-Frontiers

SwiftKG MCP Server

Related Servers

Alternatives to SwiftKG MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to query a local, continuously updated symbol graph of a codebase, providing ranked search, caller/callee exploration, dependency paths, and git-diff impact analysis through MCP tools.
      627
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides code intelligence by indexing source code into SQLite and offering MCP tools for symbol search, flow tracing, and context retrieval to assist with code navigation and understanding.
      -
    • F
      license
      Not graded
      quality
      F
      maintenance
      Provides a local code knowledge graph for Java projects, enabling querying of classes, methods, fields, calls, inheritance, and imports via MCP tools like query, context, impact, and cypher.
      1
      -

    TDQS

    A4.2/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct capability: querying (query_codebase, query_ranked, pack_snippets), structural analysis (centrality, rank_nodes, bridge_centrality), node lookup (get_node, find_node, list_nodes), and explanation (explain, explain_rank). There is some overlap between centrality and rank_nodes, but their descriptions clearly differentiate SIR vs. CodeRank, preventing ambiguity.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., list_nodes, find_node, get_node, explain_rank, snapshot_list). Verbs like query, explain, compute, and find are used predictably, and all names are lowercase snake_case throughout.

    Tool Count3/5

    With 21 tools, the count is on the heavier side, but each tool has a distinct analytical purpose that justifies its inclusion. The number is borderline above the ideal range, but the server's broad scope (from querying to snapshots) makes it reasonable. It does feel slightly inflated with multiple ranking/centrality variants.

    Completeness5/5

    The tool surface covers the full lifecycle of codebase analysis: discovery (graph_stats, list_nodes), lookup (get_node, find_node), explanation (explain), querying (query_codebase, pack_snippets), ranking (rank_nodes, centrality, query_ranked), and temporal monitoring (snapshot_list, snapshot_show, snapshot_diff). The only minor gap is a lack of direct mutation tools, but that is not expected for a read-only analysis server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues