Skip to main content
Glama
srijanshukla18

XRAY MCP

by srijanshukla18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to XRAY MCP

No user-submitted related servers found.

    Related Servers

    • mcp-codebase-intelligence

      g-tiwari
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.
      3 npm
      1
      MIT

    • nexus-serena-mcp

      jitendrakumar-ai
      A
      license
      C
      quality
      A
      maintenance
      Enables AI IDEs and coding agents to navigate code at the AST symbol level, perform surgical, collision-free refactoring, and resolve live library documentation. It also supports project onboarding memory, giving agents semantic precision without regex guesswork or heavy dependencies.
      5
      1
      MIT

    • MCP Codebase Server

      dimitriy-tolstikov
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to navigate and refactor a codebase through an AST index, offering project overviews, symbol and usage search, module dependency exploration, and LSP-backed operations such as rename, go-to-definition, diagnostics, and extract-method. Supports TypeScript/JavaScript and C# with automatic reindexing and watch mode.
      MIT
    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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose in the code exploration workflow: explore_repo maps structure, find_symbol locates specific symbols, read_interface provides file overviews, and what_breaks analyzes dependencies. The tools are clearly sequenced and complementary, with no ambiguity in their roles.

    Naming Consistency4/5

    Three tools use snake_case with descriptive verbs (explore_repo, find_symbol, read_interface), while what_breaks uses snake_case but with a less conventional verb phrase. The naming is mostly consistent and readable, with only minor deviation in style for what_breaks.

    Tool Count5/5

    Four tools is well-scoped for a code exploration server, covering the essential workflow from mapping structure to analyzing impacts. Each tool earns its place without redundancy, and the count aligns with the progressive discovery approach described.

    Completeness5/5

    The tool set provides complete coverage for codebase exploration: explore_repo for initial mapping, find_symbol for searching, read_interface for understanding files, and what_breaks for impact analysis. There are no obvious gaps, and the tools support a full workflow from discovery to dependency checking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources