BioNext-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_PATH | Yes | Path to your analysis directory where results are saved. Set in the env of the MCP server configuration. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_bioinformatics_taskB | Analyze user intent and create a bioinformatics workflow plan. This tool helps understand your analysis goals and prepares the workflow structure. After this, ask Claude to generate Python scripts (≤100 lines each), then use execute_claude_script to run them. |
| debug_workflowC | Analyze workflow execution results and provide debugging insights |
| execute_claude_scriptA | 🚀 MAIN TOOL: Automatically detect and execute Python scripts generated by Claude LLM for bioinformatics tasks. Features: ✅ Auto-detects Python installation ✅ Provides detailed installation guide if Python missing ✅ Auto-installs required packages (pandas, numpy, biopython, etc.) ✅ Full execution logging and error handling ✅ Script length monitoring (recommends ≤100 lines) ✅ HTML report generation with auto-browser opening |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cherine0205/BioNext-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server