- Home
- Resources
- Integrations
- Roboflow
Claude Roboflow connectorWhat Claude can do in your Roboflow account.
The Claude Roboflow connector exposes 67 tools. 42 read your projects, models and devices, 19 change something, and 6 stay unclassified. Below: what Claude inspects, what it trains, labels or reconfigures, and why Roboflow documents far more tools than the directory shows.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude works in your Roboflow workspace
A computer vision project in Roboflow spans datasets, labeling, versions, training runs, evaluations and devices in the field. With the connector, you describe what you need, say a model that spots missing hard hats on a site camera, and Claude searches public datasets, sets up the project, uploads images, starts auto-labeling and reads the evaluation back to you. You still judge the results.
A dataset without starting from zero. universe_search finds public datasets and models on Roboflow Universe, and projects_fork copies one into your workspace as a starting point.
Labels and versions, handled in the chat. image_upload brings in a zip of images, autolabel_start runs hosted auto-labeling on a batch, and versions_generate creates a dataset version, with preprocessing if you want it.
Evaluation you can read. model_evals_get_confusion_matrix and model_evals_get_performance_by_class show where a model fails; Claude explains which classes need more data. On the field side, devices_get_telemetry and devices_get_logs tell you how an edge device is doing.
Now the part the sheet does not spell out. Roboflow's documentation says its server exposes 141 tools, while the Claude directory lists 67, and three of those 67 appear nowhere in that documentation. Each tool also depends on the permissions you approve when you sign in. No source describes a Claude-specific confirmation for any Roboflow tool, so the general approval rule is what applies. Nothing runs on its own either: no tool fires when a training finishes or a device raises an alert. For that, an automation tool is the right trade, and our Integrations hub covers it. Other apps get the same breakdown, for instance the Claude asana connector.
Five words before you plug it in
The vocabulary you will meet on the way.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named job the connector opens to Claude. Claude picks the ones it needs mid-answer; the directory sheet lists them by name.
- Authorization
- Roboflow's own sign-in screen, where you hand Claude the access it will use afterwards. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Roboflow.
Connect Roboflow to Claude in three steps
- 01
Find Roboflow in Claude
In Claude's settings, open Customize, then Connectors, and look for Roboflow. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; then each member connects on their own.
- 02
Start the connection
Click Connect on its row. Roboflow asks you to sign in with your Roboflow account in its own window the first time a tool is used. If the link breaks later, hit Disconnect and connect again.
- 03
Read the authorization screen
Before you accept, read what the screen asks for. It belongs to Roboflow, not to Claude, and it decides what the access covers. That access can also be withdrawn later from the Roboflow side.
The 67 tools of the Claude Roboflow connector
Roboflow gives Claude 67 tools: 42 that read your account, 19 that change something in it, and 6 no official source describes.
Three groups: what Claude reads, what it changes, and six tools whose effect no source spells out. Names stay as Claude shows them, in English.
- 42 read
- 19 write
- 6 not documented
Tools index
- agent_conversation_get
- agent_conversations_list
- annotation_batches_get
- annotation_batches_list
- async_tasks_get
- autolabel_job_get
- devices_get
- devices_get_config
- devices_get_config_history
- devices_get_default_config
- devices_get_events
- devices_get_logs
- devices_get_telemetry
- devices_list
- devices_streams_get
- devices_streams_list
- image_upload_status
- images_search
- images_workspace_search
- model_evals_get
- model_evals_get_confidence_sweep
- model_evals_get_confusion_matrix
- model_evals_get_image_predictions
- model_evals_get_map_results
- model_evals_get_performance_by_class
- model_evals_get_recommendations
- model_evals_get_vector_analysis
- model_evals_list
- models_get
- models_infer
- models_list
- projects_get
- projects_health
- projects_list
- universe_dataset_images_search
- universe_search
- versions_get
- workflow_blocks_get_schema
- workflow_blocks_list
- workflow_specs_validate
- workflows_get
- workflows_list
- agent_workflow_publish
- annotation_jobs_create
- annotations_save
- autolabel_start
- devices_create
- devices_update_config
- image_upload
- images_batch_update_metadata
- images_update_metadata
- meta_feedback_send
- models_star_nas
- projects_create
- projects_fork
- trainings_cancel
- trainings_stop
- versions_export
- versions_generate
- workflows_create
- workflows_update
What Claude reads (42)
42 toolsForty-two tools that search, inspect and report on projects, models, evaluations and devices without touching them.
agent_conversation_get
Opens one conversation with the Roboflow agent, with its full message history.
agent_conversations_list
Lists the conversations people in your workspace have held with the Roboflow agent, so Claude can find the right thread without you scrolling through them.
annotation_batches_get
Opens one upload batch in a project and reports what Roboflow knows about it, which is how Claude checks what actually arrived.
annotation_batches_list
Lists the upload batches in a project, the groups images sit in after upload and before anyone labels them.
async_tasks_get
Polls a background task by its ID, such as a project fork or a split rebalance, to see where it stands.
autolabel_job_get
Returns status and progress, sub-job by sub-job, for an auto-labeling run.
devices_get
Pulls up a single edge device by its ID, the record Roboflow keeps for one unit deployed in the field.
devices_get_config
Shows the runtime configuration a device is running right now, the settings that decide what it does with its camera feeds.
devices_get_config_history
Walks back through a device's earlier configuration revisions, newest first, so Claude can tell you what was different before a problem started.
devices_get_default_config
Returns the default configuration your workspace applies to devices, the baseline a unit starts from before anyone tailors it.
devices_get_events
Lists lifecycle events for a device and its streams, the timeline of starts, stops and state transitions Roboflow records.
devices_get_logs
Fetches the logs of a device, the raw lines Claude can scan for errors and patterns you would not spot by eye.
devices_get_telemetry
Returns aggregated hardware metrics and the overall health of a device, the numbers that tell you if the box itself is struggling.
devices_list
Lists every device registered in the workspace, which gives Claude the inventory it needs before looking at any single unit.
devices_streams_get
Returns one stream configured on a device, by its ID, with the settings Roboflow holds for that feed.
devices_streams_list
Lists the streams configured on a device, one entry per camera feed or video source the unit handles.
image_upload_status
Checks where an image zip upload stands, so Claude can tell you whether the images are in the project yet or still on their way.
images_search
Searches for images inside one project, which is how Claude finds the examples you want to look at or relabel.
images_workspace_search
Searches images across the entire workspace with RoboQL, Roboflow's query language, instead of one project at a time.
model_evals_get
Returns the top-level summary of one model evaluation, the headline figures Claude reads before digging into details.
model_evals_get_confidence_sweep
Returns precision, recall and F1 across confidence thresholds, the curve you need to choose where the model should draw the line.
model_evals_get_confusion_matrix
Returns the confusion matrix of an evaluation, showing which classes the model mixes up and how often.
model_evals_get_image_predictions
Returns prediction statistics image by image, in pages, so Claude can point at the pictures behind a weak score.
model_evals_get_map_results
Returns mAP results for each split of the dataset, the standard detection score broken down by training, validation and test.
model_evals_get_performance_by_class
Returns performance metrics class by class for one split, which is where weak classes stop hiding behind a good average.
model_evals_get_recommendations
Returns the recommendations Roboflow generated for an evaluation, when there are any, as a starting point for the next iteration.
model_evals_get_vector_analysis
Returns how the images of an evaluation cluster once turned into embeddings, which helps spot groups of look-alike pictures.
model_evals_list
Lists the model evaluations in the workspace, the index Claude uses before opening any single evaluation.
models_get
Shows the record of a trained model, with the details Roboflow keeps on how and on what it was trained.
models_infer
Runs hosted inference on an image with a trained model and returns what the model sees.
models_list
Lists the trained models in a project, so Claude can compare candidates before you pick one to deploy.
projects_get
Returns a project's details, including versions, classes, splits and trained models, in one view Claude can summarize.
projects_health
Returns the dataset health check of a project, the view that exposes imbalanced classes or thin data.
projects_list
Lists the projects in the workspace, the entry point Claude uses when you name a project loosely.
universe_dataset_images_search
Searches images inside a public Universe dataset from its URL, so you can check what it holds before relying on it.
universe_search
Searches Roboflow Universe, the public catalogue of shared datasets and models, for something close to your use case.
versions_get
Returns a version's information, including its splits and the trainings that used it, which ties data to models.
workflow_blocks_get_schema
Returns the full schema of one Workflow block, the inputs and outputs Claude must respect when proposing a pipeline.
workflow_blocks_list
Lists every available Workflow block with a short summary of each, the catalogue of building pieces for a pipeline.
workflow_specs_validate
Checks a Workflow JSON definition without running it, which catches mistakes before anything is saved or executed.
workflows_get
Opens a saved Workflow and returns the details Roboflow keeps on it, so Claude can walk you through the pipeline in plain words first.
workflows_list
Lists the saved Workflows in the workspace, so Claude can see which pipelines already exist before building another.
What Claude changes (19)
19 toolsNineteen tools that upload, label, train, publish or reconfigure. No source describes a confirmation for them: the general rule below applies.
agent_workflow_publish
Approval: see the rulePublishes the latest draft of a Workflow that the Roboflow agent edited.
annotation_jobs_create
Approval: see the ruleCreates a labeling job and moves images from a batch into it.
annotations_save
Approval: see the ruleSaves an annotation on an image that is already in the project.
autolabel_start
Approval: see the ruleStarts a hosted auto-labeling job over a batch of images.
devices_create
Approval: see the ruleProvisions a new edge device in the workspace.
devices_update_config
Approval: see the ruleUpdates the runtime configuration of a device.
image_upload
Approval: see the ruleUploads local image files to a project as a zip.
images_batch_update_metadata
Approval: see the ruleUpdates metadata and tags on several images in one call.
images_update_metadata
Approval: see the ruleChanges the metadata and tags of a single image.
meta_feedback_send
Approval: see the ruleReports a bug, a missing feature or a documentation issue to the Roboflow team.
models_star_nas
Approval: see the ruleStars or unstars a model found by neural architecture search.
projects_create
Approval: see the ruleCreates a new computer vision project in the workspace.
projects_fork
Approval: see the ruleQueues an asynchronous fork of a public Universe project into your workspace.
trainings_cancel
Approval: see the ruleCancels a training run in progress.
trainings_stop
Approval: see the ruleRequests an early stop on a training run in progress.
versions_export
Approval: see the ruleChecks or triggers a dataset export for a version.
versions_generate
Approval: see the ruleCreates a dataset version with optional preprocessing and augmentation.
workflows_create
Approval: see the ruleCreates and saves a new Workflow.
workflows_update
Approval: see the ruleUpdates the name and definition of a saved Workflow.
Unclassified (6)
6 toolsThree of these have a one-line description that does not say whether they change anything; three appear in no documentation at all. We will not guess either way.
agent_chat
Roboflow's documentation describes this as a chat with its own AI agent for questions, Workflow building and solution planning, but no source says whether that chat alters anything in your workspace. The page leaves it unclassified.
models_get_training_status
The directory lists this name, and Roboflow's documentation does not describe it under that name. No source says what it returns, so the page adds nothing and draws no conclusion from the wording.
models_train
Only the name appears, on the directory sheet. Roboflow's documentation covers training under other names, and no source ties this one to them, so the page stays silent.
trainings_get_results
This name sits in the directory list without a description, and Roboflow's documentation does not use it anywhere. The page will not infer what it reports, even if the name seems clear.
workflow_specs_run
Roboflow describes this as executing a Workflow from an inline JSON definition. No source says whether such a run can alter data in your workspace, so the page leaves it unclassified instead of guessing.
workflows_run
Roboflow's documentation says it executes a saved Workflow on one or more images. No source says whether a run stores results anywhere, so the page does not classify it and makes no promise about side effects.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, owners decide whether a member may let certain actions through without being asked each time. They can also cap what a connector may do across the organization, keeping reading open and closing writing, and nobody bypasses that from their own account. Claude works with your rights, nothing more. Roboflow adds its own layer: each tool declares the permissions it needs, and only those you approve at sign-in are granted.
Which plans include it
Of the 819 sheets in the official directory, none shows availability by plan. The per-connector answer is published nowhere, a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can connect. For the current state, open the Roboflow sheet in the directory from your own account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing starts when a training ends or a device raises an alert.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it. The tool list is an observed floor, not a promise, since an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not decide which tools a publisher exposes. Plug in publishers you know, here Roboflow itself.
How many tools does the Roboflow connector expose?
- Claude directory sheet ↗September 30, 202667 tools listed on the public sheet.
- Roboflow documentation, MCP Server ↗read September 30, 2026Roboflow states that its server exposes 141 tools, grouped by area from projects to API keys.
What this page followsRoboflow's documentation describes a broader server than the list the directory displays, and three of the sheet's 67 names are absent from it. What your account actually shows after connecting is what counts; this page only documents the 67 tools on the sheet.
Need help connecting Roboflow to Claude?
A person reads every message.

