LabscoMCP early access ↗
bio-mcpMCP SERVER

Bio-MCP BLAST

Run BLAST from the conversation against nt, nr or your own databases, and build new databases from your sequences.

by bio-mcp ↗Biomedical: Genomics & Clinical DataCommunity

LABSCO SUMMARY

BLAST from the conversation, against databases you keep.

Point it at a local BLAST+ install and ask in plain language: search a sequence or a FASTA file against nt, nr or a database you built, and get the hits back in the format you need. For searches that take minutes, a queue mode hands back a job ID instead, but it needs a separate queue service.

What it is

A Python MCP server that drives a local NCBI BLAST+ installation. It runs nucleotide and protein searches, builds databases from your own FASTA files, and returns results in JSON, XML, tabular or pairwise form. Job-based searches for long runs need its separate queue mode.

What you get

  • A nucleotide search (blastn) against a named database or a path
  • A protein search (blastp) the same way
  • A BLAST database built from your own FASTA file (makeblastdb)
  • Job-based versions of both searches, with status checks and result pickup, in queue mode only, which needs the separate bio-mcp-queue service running
  • Input given as either a FASTA file path or a raw sequence
  • Output format chosen per search — tabular, XML, JSON or pairwise — with a limit on how many hits return

Requirements

BLAST+ installed on the machine — conda install -c bioconda blast, brew install blast, or apt-get install ncbi-blast+ — plus the server itself: clone the repository and run pip install -e . inside it. The client configuration starts local mode; job-based searches need the separate bio-mcp-queue setup and python -m src.main --mode queue. Databases are local: give a name such as nt or nr, or a path.

Setup effort

Follow the published steps — conda install -c bioconda blast