antiSMASH MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTISMASH_MCP_SERVER | No | 默认 antiSMASH 服务器类型（bacteria/fungi/plant） | bacteria |
| ANTISMASH_MCP_LOG_LEVEL | No | 日志级别（DEBUG/INFO/WARNING/ERROR） | INFO |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_sequenceB | Submit a nucleotide sequence file to antiSMASH for secondary metabolite biosynthetic gene cluster analysis. The sequence file should be in GenBank, EMBL, or FASTA format. Returns a job ID that can be used to check status and retrieve results. |
| submit_ncbiA | Submit an NCBI accession number to antiSMASH for secondary metabolite biosynthetic gene cluster analysis. antiSMASH will retrieve the sequence from NCBI automatically. Returns a job ID that can be used to check status and retrieve results. |
| check_job_statusB | Check the status of a submitted antiSMASH job. Returns the current status (queued/running/done/error/pending) and a URL to the results page. |
| wait_for_jobA | Wait for an antiSMASH job to complete by polling its status. This is a blocking operation that checks the job status at regular intervals until the job is done or an error occurs. Use with caution as antiSMASH analysis can take 10+ minutes. |
| get_job_resultsB | Get the results of a completed antiSMASH job. Returns a summary of detected biosynthetic gene clusters, regions, and cluster types. The job should be completed before calling this tool. |
| get_job_detailsA | Get detailed information about an antiSMASH job, including detected regions, cluster types, download links, and summary statistics. Works for both running and completed jobs. |
| download_resultsA | Download the antiSMASH results archive (ZIP file) for a completed job and save it to a local path. The ZIP file contains all analysis results including GenBank files, HTML reports, and JSON data. |
| get_server_statusA | Get the current status of the antiSMASH server, including the number of running jobs, queued jobs, and total jobs processed. Useful to check if the server is available before submitting new jobs. |
| list_extra_featuresA | List all available extra features for antiSMASH analysis with their descriptions. These features can be specified when submitting a job. |
| get_example_urlA | Get the URL for the example antiSMASH output, which can be used to explore the format and content of antiSMASH results without submitting a job. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes (submission vs. status vs. download). However, get_job_results and get_job_details overlap noticeably, and check_job_status vs. wait_for_job require reading descriptions to distinguish polling from blocking behavior.
Strong, predictable verb_noun snake_case pattern (submit_*, get_*, check_*, download_*, list_*, wait_*). Minor deviation: submit_ncbi does not mirror submit_sequence (e.g., submit_ncbi_accession), creating slight asymmetry.
10 tools is well-scoped for a job-based analysis server, covering submission, monitoring, retrieval, and server info without redundancy or bloat.
Core lifecycle is covered: two submission paths, status checks, blocking wait, results, details, download, server health, and an example URL. Missing a cancel/delete job or list-jobs operation, but these are minor gaps agents can work around.