X-Ways MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XWAYS_HOME | No | Path to X-Ways installation directory (e.g., C:\xwf). Used to locate executables. | |
| PYTHONIOENCODING | No | Python IO encoding for Unicode support (e.g., utf-8). | utf-8 |
| XWAYS_MCP_SEARCH_ROOTS | No | Semicolon-separated list of directories to search for X-Ways executables (e.g., C:\Program Files\X-Ways;C:\XWFIM). | |
| XWAYS_MCP_ALLOW_EXECUTE | No | Set to '1' to allow launching X-Ways executables (dry-run by default). Must also pass confirm=true in tool call. | 0 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| environmentA | Return server configuration, platform, and execution safety status. |
| case_run_manifest_templateC | Return a generic forensic case-run manifest template for loose tool-adapter integration. |
| redact_local_fileC | Redact a local file to another local file without passing case text through MCP. |
| redaction_statusC | Report whether a local file appears to contain common case-sensitive patterns. |
| public_xways_releaseC | Fetch the public X-Ways release version from X-Ways web pages. |
| manual_statusC | Report local X-Ways manual candidates and the offline manual index status. |
| cache_xways_manualC | Cache and index the X-Ways manual locally for offline model lookup. |
| search_xways_manualC | Search the local X-Ways manual/docs index for command syntax and workflow details. |
| headless_xways_referenceC | Retrieve local manual snippets relevant to X-Ways command-line and scripting automation. |
| plan_xways_operationC | Choose the preferred X-Ways route: headless, native distributed RVS, X-Tension, then UI. |
| create_xtension_scaffoldC | Generate a local X-Tension bridge scaffold with API provenance notes. |
| plan_parallel_xways_jobsC | Plan manual-backed parallel X-Ways workers without launching them. |
| discover_installationsC | Discover X-Ways, WinHex, X-Ways Imager, and XWFIM executables. |
| inspect_xwfim_cacheC | Validate XWFIM Temp ZIP downloads, including truncated viewer archives. |
| validate_archiveC | Validate a ZIP archive and report truncation or bad entries. |
| hash_fileB | Hash a file using comma-separated algorithms such as md5,sha1,sha256. |
| build_case_db_path_string_triage_commandB | Build, but do not run, the local X-Ways case-DB path-string triage PowerShell command. |
| build_path_usage_pattern_triage_commandA | Build, but do not run, the local sanitizer command for XwfPathExport JSONL output. |
| run_case_db_path_string_triageC | Run local case-DB path-string triage only when XWAYS_MCP_ALLOW_CASE_READ=1 and confirm=true. |
| run_path_usage_pattern_triageC | Run local X-Tension JSONL usage-pattern sanitizer only when case-read gate is enabled. |
| create_workspaceB | Create a case workspace with evidence, export, report, log, and script folders. |
| triage_inventoryC | Create a read-only filesystem triage inventory for a folder or mounted evidence tree. |
| build_launch_commandC | Build the X-Ways launch command without executing it. |
| launch_xwaysC | Launch X-Ways only when XWAYS_MCP_ALLOW_EXECUTE=1 and confirm=true. |
| harness_init_caseC | Create a forensic-copilot-compatible manifest, report stub, and audit log. |
| harness_xwfim_preflightC | Run XWFIM preflight and write artifacts, status JSON, report stub, and audit log. |
| harness_folder_triageC | Run read-only folder triage and write forensic-copilot-compatible artifacts. |
| testenv_createC | Create a synthetic disposable fixture environment for windows/linux/macos/generic evidence. |
| testenv_buildC | Create a disposable fixture environment and immediately run harness checks. |
| testenv_runC | Run harness checks against an existing disposable fixture environment. |
| testenv_destroyB | Delete a managed disposable fixture environment only when confirm=true. |
| testenv_listC | List managed disposable fixture environments. |
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/Donovoi/X-Ways-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server