MCP ServerTool Reference

Tool reference

The remote BioNodulo server at https://bionodulo.com/api/mcp exposes the cloud tools below. Each request is authorized for the connected account and selected team. A team override is accepted only when that user belongs to the team. The server requires one of three OAuth scopes for each tool:

  • bionodulo:read allows the listed account, catalog, workflow, run, billing, and file reads.
  • bionodulo:write allows changes to saved workflows and cloud files.
  • bionodulo:run allows starting and cancelling cloud runs.

An AI client may request these scopes during sign-in or ask you to reconnect when a tool needs an additional scope. A default login may grant read access only. A tool call also checks your account and team permissions. Run operations can consume credits; submit_run requires confirmation of the team, workflow, and credit use.

Read tools (bionodulo:read)

ToolWhat it does
open_bionoduloOpen the authorized cloud workbench in a host that supports MCP Apps. In a client without embedded UI, use the regular tools; get_workflow can provide an editor link. It does not access the local desktop app.
get_account_infoShow the connected account and team.
get_credit_balanceShow plan, credit balance, and AI quota.
list_workflowsList saved workflows accessible to the team.
get_workflowRead one saved workflow definition and an editor link.
list_runsList the team’s recent cloud runs.
get_run_statusRead a cloud run’s current status. Queued or running does not mean completed.
get_run_eventsRead paginated durable events for a run.
get_run_outputsRead verified output artifacts and temporary download links.
estimate_run_costGet the compute credit rate for a resource profile; this does not predict total runtime.
list_filesList cloud uploads and run outputs accessible to the team.
search_node_typesSearch the live built-in node catalog.
get_node_infoRead a node’s actual input, output, and parameter schema.
validate_workflowCheck a graph against the shared editor’s validation rules. This does not run it or prove local tools are installed.
import_workflowTranslate supported Nextflow, Snakemake, CWL, or Galaxy text into a BioNodulo draft. It does not execute or save the source; review portability warnings and validate the result.
export_workflowExport a graph as Nextflow, Snakemake, CWL, Galaxy, JSON, RIS, BibTeX, or CSV. Review the portability report; export does not prove another engine can run it.

Write tools (bionodulo:write)

ToolWhat it does
create_workflowSave a new workflow draft; it does not start compute. Requires a client request ID to prevent duplicate drafts after retries.
update_workflowChange selected fields of a saved workflow.
delete_workflowPermanently delete a saved workflow.
get_upload_urlRequest a temporary storage URL for a declared file. This does not upload the bytes.
complete_uploadVerify bytes sent to an upload URL and mark the file available.
delete_filePermanently delete a selected cloud file.

Run tools (bionodulo:run)

ToolWhat it does
submit_runSubmit a saved workflow for cloud execution. Requires explicit authorization of credit use; the result is a submitted run, not a completed one.
cancel_runRequest cancellation of a queued or running run. It cannot undo charges already incurred.

Local desktop tools

These belong to the separate local bionodulo-mcp connector, which runs on the same computer as the BioNodulo desktop app. They are not exposed by the remote /api/mcp endpoint: desktop_status, desktop_list_node_types, desktop_get_node_info, desktop_list_templates, desktop_validate_workflow, desktop_submit_run, desktop_get_run, desktop_get_run_logs, desktop_get_queue, desktop_get_history, and desktop_get_system_stats.

The repository’s older Python MCP package also has additional cloud tools, resources, and prompts. Its capabilities and operator configuration are separate from this remote server’s OAuth tool list. See the source README for developer details.

Next