Wegene Assistant

This MCP server lets you access and analyze Wegene genetic testing reports through a structured set of resources and tools. It enables an automated OAuth flow to read your Wegene profiles and reports, so a client can reason over your genetic data to provide insights.

How to use

To use this MCP server from an MCP client, start by initiating the Wegene OAuth flow to grant access to your Wegene account. After authorization completes, you can request the list of available profiles, then inspect the available reports for each profile. Finally, fetch a specific report’s results to supply context for your assistant’s analyses.

Available tools and their typical usage:

• wegene-oauth: Open a browser-based Wegene Open API OAuth process. Complete the authorization within 120 seconds so subsequent tool calls can access your reports.

• wegene-get-profiles: Retrieve the list of Wegene profiles you own. Each item should include the profile name and its id for subsequent requests.

• wegene-get-report-info: Get metadata about available reports under your profiles. Expect a list containing report names, descriptions, and endpoints so you know what you can fetch.

• wegene-get-report: Read the results of a single report for a chosen profile. You provide the report endpoint, report id, and profile id to obtain the report JSON data.

How to install

Prerequisites: you need a runtime capable of hosting MCP servers (Node.js with npm, and optionally UV-based tooling for local development). Ensure you have an editor and terminal access to run commands.

Install via Smithery (recommended for automatic setup):

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

Install locally and run in development mode:

1. Prepare the project locally by cloning the repository and installing dependencies. 2) Synchronize development extras to set up the MCP server environment. 3) Run the server in development mode.

# 1) Clone the project
git clone https://example.com/xraywu/mcp-wegene-assistant.git
cd mcp-wegene-assistant

# 2) Install dependencies and prepare environment
uv sync --dev --all-extras

# 3) Start the MCP server in development mode (example command, adjust as needed)
uv run wegene-assistant

Additional configuration and notes

Environment considerations: You will need Wegene Open API credentials (key and secret) to enable API access. Copy and rename the environment file from the example, then populate your credentials.

Developer workflow: The following local configuration is used to connect Claude Desktop to the MCP server. This config should be placed in Claude Desktop’s MCP configuration file.

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

Available tools

wegene-oauth

Start a Wegene Open API OAuth process in the browser to authorize access to Wegene data.

wegene-get-profiles

Read the profile list under a user's Wegene account; returns profile names and ids for subsequent requests.

wegene-get-report-info

Return metadata about available Wegene reports, including names, descriptions, endpoints, and other details.

wegene-get-report

Read the results of a single Wegene report for a given profile; requires report_endpoint, report_id, and profile_id and returns the report JSON data.