Roboflow MCP integration for AI agents.

Connect AI agents to Roboflow through 12 structured actions, including describe workflow interface, run saved workflow, and detect objects. Review authentica…

ACTION CONTRACTS
12
AUTHENTICATION
API key
SOURCE STATUS
Provider-backed

CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE

CAPABILITY PROFILE

What the Roboflow integration exposes

The Roboflow Agent App exposes 12 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent describe workflow inputs, outputs, typing hints, and kind schemas for a specification or saved roboflow workflow, run a workflow saved in roboflow using workspace and workflow identifiers with runtime inputs, and run roboflow hosted object detection for one project version using a public image url or base64 image content. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.

A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.

For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Roboflow account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real Roboflow capabilities.

Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

describe_workflow_interfaceREAD

Describe workflow inputs, outputs, typing hints, and kind schemas for a specification or saved Roboflow workflow.

INPUTS: specification / workspace / workflowId / workflowVersionId / useCache

run_saved_workflowWRITE

Run a workflow saved in Roboflow using workspace and workflow identifiers with runtime inputs.

INPUTS: workspace / workflowId / inputs / workflowVersionId / useCache

detect_objectsREVIEW

Run Roboflow hosted object detection for one project version using a public image URL or Base64 image content.

INPUTS: project / version / imageUrl / imageBase64 / confidence

get_execution_engine_versionsREAD

List available Roboflow workflow execution engine versions.

get_project_versionsREAD

Get one Roboflow project and list its available versions.

INPUTS: workspace / project

get_server_infoREAD

Read Roboflow inference server name, version, and UUID.

get_server_metricsREAD

Read Prometheus metrics exposed by the Roboflow inference server.

get_versionREAD

Read one Roboflow project version and return training/export metadata.

INPUTS: workspace / project / version

get_workflow_schemaREAD

Fetch the Roboflow workflow block JSON schema.

list_projectsREAD

List Roboflow projects visible to the API key workspace.

run_workflowWRITE

Run a Roboflow workflow specification with runtime inputs and return serialized workflow outputs.

INPUTS: specification / inputs / workflowId / excludedFields / enableProfiling

validate_workflowREVIEW

Validate a Roboflow workflow specification before running it.

INPUTS: specification

INPUT CONTRACTS

Know what the action needs before it runs.

describe_workflow_interface

specificationOPTIONAL
Roboflow workflow specification object defining version, inputs, steps, and outputs.
workspaceOPTIONAL
The Roboflow workspace slug.
workflowIdOPTIONAL
The Roboflow workflow identifier.
workflowVersionIdOPTIONAL
Specific saved workflow version identifier to use instead of the latest version.
useCacheOPTIONAL
Whether Roboflow should use cached saved workflow definitions when describing a saved workflow.

run_saved_workflow

workspaceREQUIRED
The Roboflow workspace slug.
workflowIdREQUIRED
The Roboflow workflow identifier.
inputsREQUIRED
Runtime values keyed by Roboflow workflow input name.
workflowVersionIdOPTIONAL
Specific saved workflow version identifier to use instead of the latest version.
useCacheOPTIONAL
Whether Roboflow should use cached saved workflow definitions.

detect_objects

projectREQUIRED
The Roboflow project slug.
versionREQUIRED
The Roboflow project version number.
imageUrlOPTIONAL
A public image URL to send to Roboflow for inference.
imageBase64OPTIONAL
Base64-encoded image bytes to send to Roboflow for inference.
confidenceOPTIONAL
Minimum confidence threshold percentage for returned predictions.

get_project_versions

workspaceOPTIONAL
The Roboflow workspace slug.
projectOPTIONAL
The Roboflow project slug.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Describe Workflow Interface

Describe workflow inputs, outputs, typing hints, and kind schemas for a specification or saved Roboflow workflow. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

describe_workflow_interface

Control Run Saved Workflow

Run a workflow saved in Roboflow using workspace and workflow identifiers with runtime inputs. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.

run_saved_workflow

Verify with Get Execution Engine Versions

List available Roboflow workflow execution engine versions. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

get_execution_engine_versions

SAFETY BOUNDARY

Operate Roboflow with explicit limits

  • Authorize Roboflow with API key and grant only the provider access required by the selected actions.
  • 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
  • Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
  • No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Roboflow rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the Roboflow task completed successfully.

CONNECTION MODEL

API key

Roboflow API key sent as the api_key query parameter. Get it from Roboflow Settings under API Keys.

Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.

READ SIGNALS
8
WRITE SIGNALS
2
HIGH IMPACT
0
REVIEW SIGNALS
2

EVIDENCE AND AVAILABILITY

Provider reference

Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Roboflow.

Official Roboflow website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS