XRAY MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XRAY_DEBUG | No | Enable debug logging (set to 1 to enable) | |
| XRAY_DB_PATH | No | Custom database location for XRAY |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| explore_repoA | πΊοΈ STEP 1: Map the codebase structure - start simple, then zoom in! PROGRESSIVE DISCOVERY WORKFLOW:
INPUTS:
EXAMPLE 1 - Initial exploration (directory only): explore_repo("/Users/john/project") Returns:/Users/john/project/βββ src/βββ tests/βββ docs/βββ README.mdEXAMPLE 2 - Zoom into src/ with symbols: explore_repo("/Users/john/project", focus_dirs=["src"], include_symbols=True) Returns:/Users/john/project/βββ src/βββ auth.pyβ βββ class AuthService: # Handles user authenticationβ βββ def authenticate(username, password): # Validates credentialsβ βββ def logout(session_id): # Ends user sessionβββ models.pyβββ class User(BaseModel): # User account modelβββ ... and 3 moreEXAMPLE 3 - Limited depth exploration: explore_repo("/Users/john/project", max_depth=1, include_symbols=True) Shows only top-level dirs and files with their symbolsπ‘ PRO TIP: Start with include_symbols=False to see structure, then set it to True for areas you want to examine in detail. This prevents information overload! β‘ PERFORMANCE: Symbol extraction is cached per git commit - subsequent calls are instant! WHAT TO DO NEXT:
|
| find_symbolA | π STEP 2: Find specific functions, classes, or methods in the codebase. USE THIS AFTER explore_repo() when you need to locate a specific piece of code. Uses fuzzy matching - you don't need the exact name! INPUTS:
EXAMPLE INPUTS: find_symbol("/Users/john/awesome-project", "authenticate") find_symbol("/Users/john/awesome-project", "user model") # Fuzzy matches "UserModel" EXAMPLE OUTPUT: [ { "name": "authenticate_user", "type": "function", "path": "/Users/john/awesome-project/src/auth.py", "start_line": 45, "end_line": 67 }, { "name": "AuthService", "type": "class", "path": "/Users/john/awesome-project/src/services.py", "start_line": 12, "end_line": 89 } ] RETURNS: List of symbol objects (dictionaries). Save these objects - you'll pass them to what_breaks()! Empty list if no matches found. WHAT TO DO NEXT: Pick a symbol from the results and pass THE ENTIRE SYMBOL OBJECT to what_breaks() to see where it's used in the codebase. |
| read_interfaceA | π READ INTERFACE: Get a high-level overview of a file without reading implementation. Returns function signatures, class definitions, and docstrings. Perfect for understanding how to USE a module without reading the whole thing. INPUTS:
EXAMPLE: read_interface("/Users/john/project", "src/auth.py") |
| what_breaksA | π₯ STEP 3: See what code might break if you change this symbol. USE THIS AFTER find_symbol() to understand the impact of changing a function/class. IMPROVEMENTS:
INPUT:
EXAMPLE INPUT: First, get a symbol from find_symbol():symbols = find_symbol("/Users/john/project", "authenticate") symbol = symbols[0] # Pick the first result Then pass THE WHOLE SYMBOL OBJECT:what_breaks(symbol) EXAMPLE OUTPUT: { "references": [ { "file": "/Users/john/project/src/api.py", "line": 23, "text": " # Authenticate the user user = authenticate_user(username, password) if not user:", "type": "code" } ], "total_count": 1, "strategy": "structural", "note": "Found 1 references using structural search." } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/srijanshukla18/xray'
If you have feedback or need assistance with the MCP directory API, please join our Discord server