MCP (Model Context Protocol) server for the gget bioinformatics library.
This server implements the Model Context Protocol (MCP) for gget, providing a standardized interface for accessing powerful bioinformatics tools and databases. MCP enables AI assistants and agents to perform complex genomics queries through structured interfaces.
The gget bioinformatics toolkit provides efficient querying of genomic databases and includes functions for:
- Gene and sequence information retrieval
- BLAST and sequence alignment
- Protein structure prediction
- Gene expression analysis
- Functional enrichment analysis
- And much more!
See how the gget MCP server works in practice with AI assistants
π€ User: "Analyze the TP53 gene - find its details and protein sequence, then check for cancer mutations"
π€ AI Assistant: I'll help you analyze TP53 step by step:
[Uses gget_search] β Found TP53 (ENSG00000141510) on chromosome 17
[Uses gget_info] β TP53 is a protein-coding tumor suppressor gene
[Uses gget_seq with translate=True] β Retrieved 393 amino acid protein sequence
[Uses gget_cosmic] β Found hotspot mutations R175H, R248Q, R273H in multiple cancers
π€ User: "Now predict the 3D structure of this protein sequence: MSKGEELFTGVVPILVEL..."
π€ AI Assistant: Let me analyze this sequence:
[Uses gget_blast] β Identified as Green Fluorescent Protein (GFP)
[Uses gget_alphafold] β Predicted classic beta-barrel structure with 90%+ confidence
π€ User: "Perform pathway enrichment for DNA repair genes: TP53, BRCA1, BRCA2, ATM"
π€ AI Assistant: [Uses gget_enrichr] β Top pathways: DNA Damage Response, Homologous Recombination, Cell Cycle Checkpoints, p53 Signaling
See how powerful this is? You can now ask natural language questions about genes, sequences, mutations, and pathways - the AI does the complex bioinformatics work for you!
Learn more about the Model Context Protocol
MCP is a protocol that bridges the gap between AI systems and specialized domain tools. It enables:
- Structured Access: Direct connection to powerful bioinformatics tools and databases
- Natural Language Queries: Simplified interaction with complex genomics workflows
- Type Safety: Strong typing and validation through FastMCP
- AI Integration: Seamless integration with AI assistants and agents
If you want to understand more about what the Model Context Protocol is and how to use it more efficiently, you can take the DeepLearning AI Course or search for MCP videos on YouTube.
Comprehensive bioinformatics functionality through gget
gget_search: Find Ensembl IDs associated with search termsgget_info: Fetch detailed information for Ensembl IDsgget_seq: Retrieve nucleotide or amino acid sequencesgget_ref: Get reference genome information from Ensembl
gget_blast: BLAST nucleotide or amino acid sequencesgget_blat: Find genomic locations of sequencesgget_muscle: Align multiple sequences
gget_archs4: Get gene expression data from ARCHS4gget_enrichr: Perform gene set enrichment analysis
gget_pdb: Fetch protein structure data from PDBgget_alphafold: Predict protein structure using AlphaFold
gget_cosmic: Search COSMIC database for cancer mutations
gget_cellxgene: Query single-cell RNA-seq data from CellxGene
Installing uv (optional - uvx can auto-install)
# Download and install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# Verify installation
uv --version
uvx --versionuvx is a very nice tool that can run a python package installing it if needed.
You can run the gget-mcp server directly using uvx without cloning the repository:
# Run the server in HTTP mode (default)
uvx gget-mcp httpOther uvx modes (STDIO, HTTP, SSE)
# Run the server in stdio mode
uvx gget-mcp stdio# Run the server in streamable HTTP mode on default (3002) port
uvx gget-mcp http
# Run on a specific port
uvx gget-mcp http --port 8000# Run the server in SSE mode
uvx gget-mcp sseIn cases when there are problems with uvx often they can be caused by cleaning uv cache:
uv cache clean
The HTTP mode will start a web server that you can access at http://localhost:3002/mcp (with documentation at http://localhost:3002/docs). The STDIO mode is designed for MCP clients that communicate via standard input/output, while SSE mode uses Server-Sent Events for real-time communication.
Note: Currently, we do not have a Swagger/OpenAPI interface, so accessing the server directly in your browser will not show much useful information. To explore the available tools and capabilities, you should either use the MCP Inspector (see below) or connect through an MCP client to see the available tools.
We provide preconfigured JSON files for different use cases. Here are the actual configuration examples:
Use this configuration for most AI clients. Use this mode when you want to save large output files (sequences, structures, alignments) to disk instead of returning them as text. Create or update your MCP configuration file:
{
"mcpServers": {
"gget-mcp": {
"command": "uvx",
"args": ["--from", "gget-mcp@latest", "stdio"]
}
}
}For HTTP mode:
{
"mcpServers": {
"gget-mcp": {
"command": "uvx",
"args": ["--from", "gget-mcp@latest", "server"]
}
}
}For a visual guide on how to configure MCP servers with AI clients, check out our configuration tutorial video for our sister MCP server (biothings-mcp). The configuration principles are exactly the same for the gget MCP server - just use the appropriate JSON configuration files provided above.
Using MCP Inspector to explore server capabilities
If you want to inspect the methods provided by the MCP server, use npx (you may need to install nodejs and npm):
For STDIO mode with uvx:
npx @modelcontextprotocol/inspector --config mcp-config.json --server gget-mcpYou can also run the inspector manually and configure it through the interface:
npx @modelcontextprotocol/inspectorAfter that you can explore the tools and resources with MCP Inspector at which is usually at 6274 port (note, if you run inspector several times it can change port)
Simply point your AI client (like Cursor, Windsurf, ClaudeDesktop, VS Code with Copilot, or others) to use the appropriate configuration file from the repository.
Comprehensive Windows setup guide with Google Drive integration
This guide will walk you through setting up Claude Desktop with the gget_mcp extension and Google Drive integration on Windows. By the end, you'll be able to use Claude to fetch biological data (like gene sequences) and save them directly to your Google Drive folder with offline access.
- Windows PC with administrator access
- Google account
- Stable internet connection
-
Download and install Google Drive for Desktop
-
Launch the application and sign in with your user account
-
Connect your project's shared Google account (if applicable)
-
Configure offline access for your working folder:
- Navigate to the folder you want to work with in Google Drive
- Right-click on the folder (e.g., "work" or your project folder)
- Select "Available offline" from the context menu
- This makes the folder accessible at a path like
C:\GDrive\holy-bio-mcp\My Disk\work
Important: This is different from just syncing - offline access ensures the files are locally available while still being part of your Google Drive structure.
- Download Claude Desktop for Windows
- Run the installer and follow the setup wizard
- Sign in with your Anthropic/Claude account
- Complete the initial setup
-
Install
uvusing one of these methods:Option A: Using winstall
- Visit https://winstall.app/apps/astral-sh.uv
- Follow installation instructions
Option B: Using PowerShell
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
-
Restart your terminal after installation
You can install Node.js using either method:
Option A: Native Installer
- Visit https://nodejs.org/en/download
- Download the Windows installer (LTS version recommended)
- Run the installer with default settings
Option B: Using Chocolatey
choco install nodejsBoth methods work equally well - choose whichever you prefer.
Open Command Prompt or PowerShell and run:
uvx --from gget-mcp@latest stdioExpected behavior:
- The command should start without errors
- Packages will be downloaded and cached
- If it runs successfully, everything is configured correctly
- You can press
Ctrl+Cto stop it
- Open Claude Desktop
- Go to Settings (gear icon)
- Navigate to the "Extensions" tab in the left sidebar
- Enable the Filesystem Extension
- Add your Google Drive offline folder to the allowed directories (e.g.,
C:\GDrive\holy-bio-mcp\My Disk\work)
Note: The Filesystem extension is built into Claude Desktop and uses MCP under the hood, but it's managed directly by the application. You don't need to configure it in the JSON file.
- In the same manner, go to Settings, navigate to the "Developer" tab in the left sidebar
- In Developer settings tab, click "Edit Config" button
- This will open the
claude_desktop_config.jsonfile - Edit it and add the gget_mcp server configuration:
{
"mcpServers": {
"gget": {
"command": "uvx",
"args": [
"--from",
"gget-mcp@latest",
"stdio"
]
}
}
}- Save the configuration file
- Completely close Claude Desktop (check system tray)
- Restart the application
- Note: On first launch, you might experience a timeout - this is normal
- If needed, restart Claude Desktop a second time
- Open Claude Desktop Settings
- Go to the Developer tab
- Confirm that both components are enabled:
- β Filesystem Extension - should show your configured Google Drive path and show "Running" status
- β gget MCP Server - should show "Running" status
Now let's verify everything works! In Claude Desktop, create a new chat. Click "Search and tools" icon, select and enable both gget_mcp and filesystem
Try this prompt:
Please search for the COL1A1 gene, retrieve its protein sequence,
and save it to C:\GDrive\holy-bio-mcp\My Disk\work\test_sequences\ as a FASTA file.
Expected result:
- Claude will use gget_mcp to search for the gene
- It will fetch the sequence data
- It will save the file to your specified folder
- The file will sync to Google Drive automatically
- Claude will be able to read it using Filesystem Extension.
- Ensure
uvandnodeare in your system PATH - Try running the verification command again from Step 5
- Restart Claude Desktop completely
- Check that the Filesystem Extension has access to your Google Drive folder
- Verify the folder has offline access enabled in Google Drive
- Try running Claude Desktop as administrator
- Ensure the path is correct (use the exact path shown in File Explorer)
- This is normal - simply restart Claude Desktop
- Wait 10-15 seconds before making requests
- Ensure internet connection is stable (gget fetches from online databases)
- Check that the gget_mcp server shows as "Active" in settings
- Try the verification command from Step 5 again
- Confirm the folder shows a green checkmark in Google Drive for Desktop
- If files aren't syncing, right-click the folder and re-enable "Available offline"
- Check that you have enough local disk space for offline files
If everything works correctly, you now have:
- β Claude Desktop with MCP capabilities
- β Access to biological databases via gget_mcp
- β Direct file operations in your Google Drive offline folder
- β Automatic cloud synchronization of all results
You can now ask Claude to fetch gene sequences, protein data, perform BLAST searches, and save everything directly to your Google Drive folder with offline access!
- Fetch gene sequences: "Get the DNA sequence for BRCA1 and save it to my Drive"
- Protein analysis: "Find the protein sequence for TP53 and create a markdown report"
- Bulk operations: "Search for all genes related to apoptosis and create a summary table"
- Cross-referencing: "Get information about COL1A1 from Ensembl and UniProt"
Guide updated: October 13, 2025
For developers: cloning and running locally
# Clone the repository
git clone https://github.com/longevity-genie/gget-mcp.git
cd gget-mcp
uv syncIf you already cloned the repo you can run the server with uv:
# Start the MCP server locally (HTTP mode)
uv run server
# Or start in STDIO mode
uv run stdio
# Or start in SSE mode
uv run sse- Input validation: Comprehensive parameter validation for all gget functions
- Error handling: Robust error handling with informative messages
- Rate limiting: Respectful usage of external APIs and databases
- Data validation: Type checking and data format validation
Developer information: Testing and CI/CD workflows
The MCP server is provided with comprehensive tests including both unit tests and integration tests for network-dependent operations.
Run tests for the MCP server:
# Run all tests (excluding expensive judge tests)
uv run pytest -vvv -m "not judge"
# Run only fast tests (skip slow, integration, and judge tests)
uv run pytest -vvv -m "not slow and not integration and not judge"
# Run only integration tests
uv run pytest -vvv -m integration
# Run judge tests (expensive LLM tests - requires API keys and may cost money)
uv run pytest test/test_judge.py -vvv
# Run tests with coverage (excluding judge tests)
uv run pytest -vvv --cov=src/gget_mcp --cov-report=term-missing -m "not judge"Note on Judge Tests: The judge tests (test_judge.py) use large language models to evaluate the AI agent's performance with gget tools. These tests:
- Are automatically excluded from CI/CD to avoid costs
- Require API keys (GEMINI_API_KEY or similar)
- May incur charges from LLM API providers
- Are designed for local development and manual evaluation
- Provide valuable insights into how well the tools work with AI agents
This project includes several GitHub Actions workflows:
- CI (
.github/workflows/ci.yml): Runs on every push/PR with basic linting and fast tests - Tests (
.github/workflows/test.yml): Comprehensive testing across multiple OS and Python versions- Fast tests on all platforms
- Integration tests (may require network access)
- Slow tests (like BLAST operations) - runs only on Ubuntu with Python 3.11
- Code coverage reporting
- Security checks with bandit and safety
- Publish (
.github/workflows/publish.yml): Publishes to PyPI when tags are pushed
You can use MCP inspector with locally built MCP server same way as with uvx.
Note: Using the MCP Inspector is optional. Most MCP clients (like Cursor, Windsurf, etc.) will automatically display the available tools from this server once configured. However, the Inspector can be useful for detailed testing and exploration.
If you choose to use the Inspector via npx, ensure you have Node.js and npm installed. Using nvm (Node Version Manager) is recommended for managing Node.js versions.
Here are validated example questions that you can ask the AI assistant when using this MCP server:
- "Find information about the human TP53 gene and get its protein sequence."
- "What are the orthologs of BRCA1 gene across different species?"
- "Perform enrichment analysis for a set of cancer-related genes: TP53, BRCA1, BRCA2, ATM, CHEK2."
- "Get the 3D structure information for the protein encoded by the EGFR gene."
- "Find mutations in the COSMIC database for the PIK3CA gene."
- "Analyze gene expression patterns for insulin (INS) gene across different tissues."
- "Perform BLAST search with a DNA sequence to identify its origin: ATGGCGCCCGAACAGGGAC."
- "Find diseases associated with the APOE gene using OpenTargets."
- "Get reference genome information for mouse (Mus musculus)."
- "Align multiple protein sequences and identify conserved regions."
These questions are taken directly from our automated test suite and are validated to work correctly with the available gget tools.
We welcome contributions from the community! π Whether you're a researcher, developer, or enthusiast interested in bioinformatics and genomics research, there are many ways to get involved:
We especially encourage you to try our MCP server and share your feedback with us! Your experience using the server, any issues you encounter, and suggestions for improvement are incredibly valuable for making this tool better for the entire research community.
- π Bug Reports: Found an issue? Please open a GitHub issue with detailed information
- π‘ Feature Requests: Have ideas for new functionality? We'd love to hear them!
- π Documentation: Help improve our documentation, examples, or tutorials
- π§ͺ Testing: Add test cases, especially for edge cases or new query patterns
- π Data Quality: Help identify and report data inconsistencies or suggest improvements
- π Performance: Optimize queries, improve caching, or enhance server performance
- π Integration: Create examples for new MCP clients or AI systems
- π₯ Tutorials & Videos: Create tutorials, video guides, or educational content showing how to use MCP servers
- π User Stories: Share your research workflows and success stories using our MCP servers
- π€ Community Outreach: Help us evangelize MCP adoption in the bioinformatics community
Tutorials, videos, and user stories are especially valuable to us! We're working to push the bioinformatics community toward AI adoption, and real-world examples of how researchers use our MCP servers help demonstrate the practical benefits and encourage wider adoption.
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes and add tests
- Run the test suite (
uv run pytest) - Commit your changes (
git commit -m 'Add amazing feature') - Push to your branch (
git push origin feature/amazing-feature) - Open a Pull Request
- Follow the existing code style (we use
rufffor formatting and linting) - Add tests for new functionality
- Update documentation as needed
- Keep commits focused and write clear commit messages
Don't hesitate to open an issue for discussion! We're friendly and always happy to help newcomers get started. Your contributions help advance open science and bioinformatics research for everyone. π§¬β¨
Technical limitations and considerations
Some gget functions depend on external web services and databases that may occasionally be unavailable or rate-limited. The server implements proper error handling and retries where appropriate.
While we provide comprehensive tests including integration tests for network-dependent operations, some test cases may be sensitive to external service availability. Some automated test results may need manual validation.
This project is licensed under the MIT License.
- gget - The amazing bioinformatics toolkit this server wraps
- FastMCP - The MCP server framework used
- Model Context Protocol - The protocol specification
We also develop other specialized MCP servers for biomedical research:
- biothings-mcp - MCP server for BioThings.io APIs, providing access to gene annotation (mygene.info), variant annotation (myvariant.info), and chemical compound data (mychem.info)
- opengenes-mcp - MCP server for OpenGenes database, providing access to aging and longevity research data
- synergy-age-mcp - MCP server for SynergyAge database, providing access to synergistic and antagonistic longevity gene interactions
We are supported by:
HEALES - Healthy Life Extension Society
and
IBIMA - Institute for Biostatistics and Informatics in Medicine and Ageing Research


