MCP server for WeGene Assistant, using LLM to analyze a user's WeGene genetic testing report.
MCP server for WeGene Assistant, using LLM to analyze a user's WeGene genetic testing report. That is what the mcp wegene assistant mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 9 tools. What each one is for:
wegene-oauth — ** Start a WeGene Open API oAuth process in the browserwegene-get-profiles — ** Read the profile list under a user's WeGene accountwegene-get-report-info — ** Return the report meta info so LLM will know what reports are availablewegene-get-report — ** Read the results of a single report under a profileArguements — report_endpoint: The report's endpoint to be retrieved fromreport_id — The report's id to be retrievedprofile_id — The profile id to retrieve report fromResources — Once a user is authorized, all the reports under his/her account will be exposed as a resource: - Custom wegene:// URI scheme for accessing eachTools — The server implements one tool: - wegene-oauth: Start a WeGene Open API oAuth process in the browser - The user should complete the authorizationPlenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Wegene Assistant's toolset — wegene-oauth, wegene-get-profiles, wegene-get-report-info and 6 more — is a fair guide to whether it matches your workflow. It is maintained by xraywu; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| wegene-oauth | ** Start a WeGene Open API oAuth process in the browser |
| wegene-get-profiles | ** Read the profile list under a user's WeGene account |
| wegene-get-report-info | ** Return the report meta info so LLM will know what reports are available. |
| wegene-get-report | ** Read the results of a single report under a profile |
| Arguements | report_endpoint: The report's endpoint to be retrieved from |
| report_id | The report's id to be retrieved |
| profile_id | The profile id to retrieve report from |
| Resources | Once a user is authorized, all the reports under his/her account will be exposed as a resource: - Custom wegene:// URI scheme for accessing each individual report - A report resource has a name, description and applicati |
| Tools | The server implements one tool: - **wegene-oauth:** Start a WeGene Open API oAuth process in the browser - The user should complete the authorization in 120 seconds so LLM will be able to further access the reports. - ** |
{
"mcpServers": {
"wegene-assistant": {
"command": "npx",
"args": ["-y", "@smithery/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.