Wegene Assistant MCP Server
# wegene-assistant MCP server
[](https://smithery.ai/server/@xraywu/mcp-wegene-assistant)
MCP server for WeGene Assistant, using LLM to analyze a user's WeGene genetic testing report.
## Components
### 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 application/json mimetype
### 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.
- **wegene-get-profiles:** Read the profile list under a user's WeGene account
- Profiles' name and id will be returned for LLM to use.
- **wegene-get-report-info:** Return the report meta info so LLM will know what reports are available.
- A list of report names, descriptions, endpoints, etc. will be returned
- **wegene-get-report:** Read the results of a single report under a profile
- Returns the result JSON specified in [WeGene's Open API platform](https://api.wegene.com)
- 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
## Configuration
- You will need WeGene Open API key/secret to use this project.
- Copy `.env.example` as `.env` and update the key and secret in the file.
## Quickstart
### Install
#### Installing via Smithery
To install WeGene Assistant for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@xraywu/mcp-wegene-assistant):
```bash
npx -y @smithery/cli install @xraywu/mcp-wegene-assistant --client claude
```
#### Insall Locally
##### Prepare MCP Server
1. Clone this project
2. Run `uv sync --dev --all-extras` under the project's root folder
##### Claude Desktop Configuration
- On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
- On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
Add below contents in the configuration file:
```
{
"mcpServers": {
"wegene-assistant": {
"command": "uv",
"args": [
"--directory",
"/path/to/wegene-assistant",
"run",
"wegene-assistant"
]
}
}
}
```
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get-profiles retrieves account profiles, get-report fetches a specific genetic report, get-report-info lists available reports, and oauth handles authentication. There is no overlap in functionality, making tool selection unambiguous.
All tools follow a consistent 'wegene-verb-noun' pattern with hyphens, using clear verbs like 'get' and 'oauth'. This uniformity makes the tool set predictable and easy to understand.
Four tools are reasonable for a genetic data server, covering authentication, profile retrieval, and report access. It might benefit from additional operations like updating profiles or deleting data, but the core scope is well-defined.
The tools cover authentication and read operations (profiles and reports) adequately, but there are notable gaps in write operations such as creating, updating, or deleting profiles or reports. This limits the server to read-only workflows.