Skip to main content
Glama
Flux-Frontiers

SwiftKG MCP Server

by Flux-Frontiers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SwiftKG MCP Server

No user-submitted related servers found.

    Related Servers

    • Symbra

      sitharaj88
      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.
      15 npm
      Apache 2.0

    • ThingForce Graph Studio

      McComics-Servics
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables people and AI agents to query local code repositories as graphs through stdio MCP tools for project listing, search, dependency tracing, impact analysis, bridge detection, node inspection, bounded code reading, and optional LSP definition/reference lookups.
      MIT

    • local-code-intel-mcp

      tungvt93
      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.
      -

    • CodeGB

      Killian-Filippov
      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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation3/5

    The tool set spans distinct areas (discovery, query, explanation, ranking, snapshots), but there is meaningful overlap within clusters: query_codebase, pack_snippets, and query_ranked all perform hybrid semantic/structural queries with different output formats, and centrality/rank_nodes/explain_rank all compute graph centrality. An agent could struggle to choose among these similar tools despite detailed descriptions.

    Naming Consistency2/5

    Naming conventions are inconsistent. Several tools follow verb_noun (list_nodes, find_node, get_node, analyze_repo), but many are noun-only (callers, type_hierarchy, centrality, graph_stats), and the snapshot tools are reversed noun_verb (snapshot_list, snapshot_show, snapshot_diff). The mixed styles and inconsistent word order make the API harder to predict.

    Tool Count3/5

    21 tools is on the heavy side. The server covers a broad domain (code graph query, ranking, snapshots, explanations), so many tools are justified, but consolidation of the overlapping ranking/query tools (query_codebase, query_ranked, pack_snippets; centrality, rank_nodes, explain_rank) would make the surface tighter and reduce cognitive load.

    Completeness4/5

    For a read-only code analysis server, the surface is remarkably complete: discovery (list/find/get), query (semantic/structural), reverse lookup (callers), type relationships (type_hierarchy), public API, stats, multi-faceted centrality, and temporal snapshots. Minor gaps exist (e.g., no direct edge query between two nodes, no file-level summary beyond find_definition_at), but these are workable and do not block typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources