Labsco
MCP SERVER

WeGene Assistant

by xraywu ↗

Pull your WeGene genetic-testing reports into the conversation so a model can read them with you.

Health, Fitness & Wearables
Summary
Your own genetic reports, readable in the place where you can ask questions about them.

The flow is short: authorise once, pick the profile, check what reports exist, then pull the one you want. Results arrive as the raw JSON from WeGene's API, so the model is reading vendor fields rather than a prepared summary — and the browser authorisation has to be finished within 120 seconds or the step starts again.

What it is

A server over the WeGene Open API: authorise in the browser, list the profiles on your account, see which reports exist, then fetch the results of one of them.

What you get
  • A browser OAuth flow started from the conversation, completed within 120 seconds
  • The profiles on your WeGene account, by name and id
  • The report catalogue — names, descriptions and endpoints — so the right report can be picked
  • The result JSON for one report on one profile, as WeGene's API returns it
  • Every authorised report also exposed as a wegene:// resource with its own name and description
Requirements

A WeGene account with reports on it, plus a WeGene Open API key and secret — copy .env.example to .env and fill them in. Runs with uv, or installs for Claude Desktop through Smithery.

Setup effort

One command plus a key — npx -y @smithery/cli install @xraywu/mcp-wegene-assistant --client claude, then supply credentials