wegene-data-interpreter MCP Endpoint

This MCP service facilitates the analysis of WeGene genetic screening documentation by employing an LLM against an authorized user's information.

Interface Elements (Resources)

Upon successful user authentication, all associated reports become accessible as distinct resources: - A bespoke wegene:// Uniform Resource Identifier scheme is utilized to pinpoint each specific report. - Each report entity possesses a descriptive label, a summary explanation, and is served with an application/json media type.

Operational Functions (Tools)

The server exposes the following functional interfaces:

• wegene-oauth: Initiates the WeGene Open API OAuth authorization workflow within the user's browser environment.
• The LLM requires the user to finalize authorization within 120 seconds to enable subsequent data retrieval.
• wegene-get-profiles: Retrieves the enumeration of distinct personal profiles linked to the authenticated WeGene account.
• The names and unique identifiers of these profiles are returned for LLM reference.
• wegene-get-report-info: Provides metadata concerning available reports, allowing the LLM to ascertain the current inventory.
• This yields a structured list containing report nomenclature, explanatory text, access URIs, and related metadata.
• wegene-get-report: Fetches the resultant data payload for a designated genetic report associated with a specific profile.
• The output conforms to the JSON structure documented on the WeGene Open API documentation portal.
• Required Parameters:
  • report_endpoint: The specific URI path necessary for accessing the report content.
  • report_id: The unique identifier corresponding to the genetic assessment.
  • profile_id: The identifier of the user profile from which the report data originates.

Configuration Prerequisites

Operation mandates possession of valid WeGene Open API credentials (Key and Secret).

1. Duplicate the template file named .env.example to .env.
2. Populate the correct API key and secret within the newly created .env file.

Rapid Deployment Guide

Installation Procedures

Deployment via Smithery

To integrate the WeGene Assistant into Claude Desktop automatically using Smithery:

bash npx -y @smithery/cli install @xraywu/mcp-wegene-assistant --client claude

Local Deployment

Setting Up the MCP Backend

1. Obtain a local copy (clone) of this repository.
2. Execute the command uv sync --dev --all-extras from the root directory of the project.

Claude Desktop Configuration Adjustments

Update the configuration file located at: - macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json - Windows: %APPDATA%/Claude/claude_desktop_config.json

Insert the following JSON structure into the configuration:

{ "mcpServers": { "wegene-assistant": { "command": "uv", "args": [ "--directory", "/path/to/wegene-assistant", "run", "wegene-assistant" ] } } }

---

Contextual Information on XMLHttpRequest (XHR) from Wikipedia: XHR is a JavaScript object-based API designed for transmitting HTTP exchanges between a web browser and a remote server. Its methods enable browser-based programs to dispatch server queries post-page-load and subsequently receive data payloads. XHR forms a foundational element of Ajax methodology. Before Ajax, page navigation primarily relied on traditional hyperlinks and form submissions, typically resulting in a complete page refresh. The foundational concept for XMLHttpRequest was conceived in 2000 by Microsoft Outlook developers and initially materialized in Internet Explorer 5 (1999), albeit using proprietary identifiers like ActiveXObject("Msxml2.XMLHTTP"). By IE 7 (2006), universal support for the standardized XMLHttpRequest identifier was achieved across all major browsers, including Mozilla’s Gecko (2002), Safari 1.2 (2004), and Opera 8.0 (2005). The W3C formalized the specification starting in 2006, with Level 2 enhancements (event progress monitoring, cross-site capabilities, byte stream handling) later integrated back into the primary standard. WHATWG now maintains the active specification using Web IDL since late 2012. Typical usage involves object instantiation, configuration via the open method (setting method, resource URI, and synchronization mode), asynchronous listener setup, request initiation with send, and processing the final result in the responseText property upon reaching state 4 (done). Further control is available via custom headers, data uploads via the send argument, and advanced response parsing options, including premature cancellation or timeout settings.