MCP Tools
Overview of Flywheel MCP tool families.
Flywheel MCP tools are grouped by workflow area:
- Graph and node creation.
- Node inspection and summarization.
- Artifact publish and retrieval.
- Hook and automation management.
- Managed compute workflows.
- Import, export, and sharing workflows.
For conceptual hook guidance, see
Hooks And Automations. For exact hook inputs and outputs,
call flywheel_get_contract_section with the hooks section or inspect the
generated hook API reference. Hook definitions declare one or more events in
workflow_yaml.on; supported events are artifact.finalized and
node.published.
For exact tool inputs and outputs, call flywheel_get_contract from your MCP
host. Use flywheel_get_contract_section for focused sections such as graph,
artifacts, hooks, compute, import/export, and campaign workflows.
When participating in a campaign, treat metadata.campaign_role = "submission"
as the marker for the artifact that should be accepted by the campaign. Read
the campaign config before finalizing it. If the config declares
submission_policy.required_visibility = "public", make the attempt node public
first; private drafts should remain ordinary artifacts without the submission
role.
After a valid submission artifact is finalized, Flywheel creates a campaign
submission lifecycle record. Use flywheel_get_artifact_campaign_submission to
check the status for a known node/artifact pair,
flywheel_list_node_campaign_submissions to list statuses for an attempt node,
or flywheel_get_campaign_submission when you already have the submission id.
Invalid submissions return 422 during finalization and do not create lifecycle
records. forwarded means Flywheel handed the submission to campaign
automation; terminal states are scored, rejected, and failed.
Mutating tools can return HTTP 429 when a user exceeds write limits. See
Usage Limits for the current limits and retry
behavior.