Skip to content

AI integration (Model Context Protocol)

Note

MCP is optional. You do not need MCP for logging, Runs, Dashboard, or Catalog.

FlowO exposes an HTTP MCP server (mounted at /mcp on your deployment) so assistants (e.g. Cursor) can call the same operation ids the REST /api/v1/mcp-tools/... surface documents.

What is MCP?

MCP is an open standard for tools and resources. With a FlowO API token, a client can:

  • List and summarize runs (Snakemake executions).
  • Inspect failures and timelines.
  • List and search catalog workflows (stored templates).

Setup

  1. Create an API token under Settings → API Tokens (required for MCP clients; this is separate from interactive flowo login on your laptop unless you reuse that token deliberately).
  2. Point your MCP client at https://<your-host>/mcp with Authorization: Bearer <token>.

Example configuration (Cursor)

{
  "mcpServers": {
    "flowo": {
      "url": "https://your-flowo-host/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_FLOWO_API_TOKEN"
      }
    }
  }
}

Example prompts (illustrative)

  • “Summarize the latest failed run and list the first three failed jobs.”
  • Search catalog files for STAR in our RNA-seq template.”
  • Which rule produced results/counts.tsv on run ?”

Exact parameters follow your FlowO version; use Settings → MCP in the app for copy-paste hints.

MCP operation_id reference (runs)

operation_id Role
list_runs Search and list runs with filters (status, name, catalog slug, tag, time window).
get_latest_run Latest run matching optional filters.
summarize_latest_run Human-readable summary of that latest run.
diagnose_latest_failed_run Failure diagnosis for the latest failed run matching filters.
get_run_timeline Timeline payload for a specific workflow_id.
list_run_outputs Outputs recorded for a run.
list_running_runs Lightweight running count / list.
list_recent_failed_runs Recent failures.
summarize_run Summary for one workflow_id.
diagnose_run_failure Failure diagnosis for one workflow_id.
trace_run_output Trace which job/rule produced a path.

MCP operation_id reference (catalog workflows)

operation_id Role
list_catalog_workflows List catalog entries the user can see.
get_catalog_workflow_overview Metadata and overview for one catalog ref.
read_catalog_workflow_file Read one text file from a stored catalog workflow.
search_catalog_workflow_files Search paths / content in one catalog workflow.
summarize_catalog_workflow Structured summary of one catalog workflow.
list_runs_for_catalog_workflow Runs linked to a catalog entry.
materialize_catalog_workflow_workspace Materialize / refresh on-disk workspace for tooling.

Security

Token safety

Your API token grants full access to your FlowO data. Never share your configuration files publicly and always use HTTPS to encrypt the communication between your AI client and the FlowO server.

MCP connection hints on the Settings page