wegene-assistant MCP server

Created By
xraywua year ago
MCP server to analyze your genetic test results from WeGene
Overview

what is WeGene Assistant?

WeGene Assistant is an MCP server designed to analyze genetic test results from WeGene, utilizing a large language model (LLM) to interpret user reports.

how to use WeGene Assistant?

To use WeGene Assistant, users must authorize their WeGene account, after which they can access their genetic reports through a custom URI scheme and various API tools provided by the server.

key features of WeGene Assistant?

  • Integration with WeGene's Open API for seamless report access
  • Custom URI scheme for easy report retrieval
  • Multiple tools for user authorization and report management

use cases of WeGene Assistant?

  1. Analyzing genetic test results for health insights
  2. Accessing and managing multiple genetic profiles
  3. Utilizing LLM for personalized genetic report interpretation

FAQ from WeGene Assistant?

  • What is required to use WeGene Assistant?

You need a WeGene Open API key/secret and to authorize your account to access reports.

  • Can I access multiple reports?

Yes! Once authorized, all reports under your account will be available.

  • Is there a specific installation process?

Yes, you can install via Smithery or set it up locally by cloning the project and configuring the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xraywu
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago