Resources · Claude connector

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

Overview

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.

Vocabulary

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

Connect Roboflow to Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (42)

42 tools

Forty-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.

When it helps
a colleague planned a pipeline with the agent last week and you want to see what was decided.
Watch out
it reads one conversation at a time.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you want to find the thread where someone discussed the defect-detection Workflow last month.
Watch out
it lists them; opening one takes the other tool.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you uploaded footage from two cameras and want to check what landed in the second batch.
Watch out
one batch per request.

Sourcedocs.roboflow.com · September 30, 2026 ↗

annotation_batches_list

Lists the upload batches in a project, the groups images sit in after upload and before anyone labels them.

When it helps
you want to see which batches are still waiting for your labeling team this week.
Watch out
it covers one project at a time.

Sourcedocs.roboflow.com · September 30, 2026 ↗

async_tasks_get

Polls a background task by its ID, such as a project fork or a split rebalance, to see where it stands.

When it helps
you forked a Universe dataset a minute ago and want to know if it is ready.
Watch out
it reports on a task; it does not start one.

Sourcedocs.roboflow.com · September 30, 2026 ↗

autolabel_job_get

Returns status and progress, sub-job by sub-job, for an auto-labeling run.

When it helps
auto-labeling started on a thousand images and you want to know how far along it is.
Watch out
it follows a run started with the auto-label tool.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_get

Pulls up a single edge device by its ID, the record Roboflow keeps for one unit deployed in the field.

When it helps
a site manager says the loading-dock unit is acting up and you want its record before calling them back.
Watch out
the ID is needed; the listing tool finds it.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_get_config

Shows the runtime configuration a device is running right now, the settings that decide what it does with its camera feeds.

When it helps
you suspect a device runs an older model version than the one you trained last week.
Watch out
it shows the current setup, not its past.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
detections dropped yesterday afternoon and you want to know what the unit ran the day before.
Watch out
history comes newest first.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_get_default_config

Returns the default configuration your workspace applies to devices, the baseline a unit starts from before anyone tailors it.

When it helps
before provisioning a new unit, you want to know what it will start with on day one.
Watch out
it is the workspace default, not one device's actual setup.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_get_events

Lists lifecycle events for a device and its streams, the timeline of starts, stops and state transitions Roboflow records.

When it helps
a stream went down overnight and you want the sequence of events before anyone reboots the unit.
Watch out
events, not full logs; logs have their own tool.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
an edge unit keeps restarting and you want the error lines from the last hours.
Watch out
logs can be long, so ask about a specific window.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you want to know if a device is overheating or short on memory before blaming the model.
Watch out
figures are aggregated, not second by second.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_list

Lists every device registered in the workspace, which gives Claude the inventory it needs before looking at any single unit.

When it helps
you want the full list of units across your three warehouses before a maintenance round.
Watch out
it lists devices, not their streams.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_streams_get

Returns one stream configured on a device, by its ID, with the settings Roboflow holds for that feed.

When it helps
one of four camera feeds on a unit looks wrong and you want its settings side by side with the others.
Watch out
it needs the stream ID.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_streams_list

Lists the streams configured on a device, one entry per camera feed or video source the unit handles.

When it helps
you want to see how many feeds a unit processes before adding another camera to it.
Watch out
one device at a time.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
a large zip went up during lunch and you want to know whether it finished.
Watch out
it follows uploads started with the upload tool.

Sourcedocs.roboflow.com · September 30, 2026 ↗

model_evals_get

Returns the top-level summary of one model evaluation, the headline figures Claude reads before digging into details.

When it helps
you want the key numbers of last night's evaluation before the morning stand-up.
Watch out
details sit in the more specific evaluation tools.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you need to pick a confidence threshold for production and want to see the trade-off first.
Watch out
it covers one evaluation's sweep.

Sourcedocs.roboflow.com · September 30, 2026 ↗

model_evals_get_confusion_matrix

Returns the confusion matrix of an evaluation, showing which classes the model mixes up and how often.

When it helps
the model keeps mistaking forklifts for trucks and you want to know the scale of the problem.
Watch out
it reads one evaluation at a time.

Sourcedocs.roboflow.com · September 30, 2026 ↗

model_evals_get_image_predictions

Returns prediction statistics image by image, in pages, so Claude can point at the pictures behind a weak score.

When it helps
you want the images the model got most wrong, to review them with the labelers.
Watch out
results come in pages.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you want to compare validation and test performance to spot overfitting.
Watch out
mAP only, not the full per-class breakdown.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you want to know which class drags the model down before collecting more data.
Watch out
one split per request.

Sourcedocs.roboflow.com · September 30, 2026 ↗

model_evals_get_recommendations

Returns the recommendations Roboflow generated for an evaluation, when there are any, as a starting point for the next iteration.

When it helps
you want Roboflow's own hints on what to fix before the next training run.
Watch out
not every evaluation has recommendations.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you suspect a cluster of similar images confuses the model and want to see it.
Watch out
it is an analysis view, not a fix.

Sourcedocs.roboflow.com · September 30, 2026 ↗

model_evals_list

Lists the model evaluations in the workspace, the index Claude uses before opening any single evaluation.

When it helps
you want to see which models were evaluated this month and compare them.
Watch out
opening one takes the summary tool.

Sourcedocs.roboflow.com · September 30, 2026 ↗

models_get

Shows the record of a trained model, with the details Roboflow keeps on how and on what it was trained.

When it helps
before deploying, you want to confirm which dataset version a model was trained on.
Watch out
one model per request.

Sourcedocs.roboflow.com · September 30, 2026 ↗

models_infer

Runs hosted inference on an image with a trained model and returns what the model sees.

When it helps
you want to test a model on a new photo from site before rolling it out.
Watch out
it runs one image through one model.

Sourcedocs.roboflow.com · September 30, 2026 ↗

models_list

Lists the trained models in a project, so Claude can compare candidates before you pick one to deploy.

When it helps
you want to compare every model trained on a project so far before a go or no-go meeting.
Watch out
it covers one project.

Sourcedocs.roboflow.com · September 30, 2026 ↗

projects_get

Returns a project's details, including versions, classes, splits and trained models, in one view Claude can summarize.

When it helps
you want the full picture of a project before a quarterly review with stakeholders.
Watch out
one project per request.

Sourcedocs.roboflow.com · September 30, 2026 ↗

projects_health

Returns the dataset health check of a project, the view that exposes imbalanced classes or thin data.

When it helps
you suspect class imbalance and want the numbers before planning a labeling sprint.
Watch out
it checks the dataset, not the models.

Sourcedocs.roboflow.com · September 30, 2026 ↗

projects_list

Lists the projects in the workspace, the entry point Claude uses when you name a project loosely.

When it helps
you want an overview of every computer vision project the team runs right now.
Watch out
it lists the projects your access covers.

Sourcedocs.roboflow.com · September 30, 2026 ↗

versions_get

Returns a version's information, including its splits and the trainings that used it, which ties data to models.

When it helps
you want to know which trainings used a given version before retiring it.
Watch out
one version per request.

Sourcedocs.roboflow.com · September 30, 2026 ↗

workflow_blocks_get_schema

Returns the full schema of one Workflow block, the inputs and outputs Claude must respect when proposing a pipeline.

When it helps
Claude needs the exact inputs of a block before suggesting how to chain it.
Watch out
one block at a time.

Sourcedocs.roboflow.com · September 30, 2026 ↗

workflow_blocks_list

Lists every available Workflow block with a short summary of each, the catalogue of building pieces for a pipeline.

When it helps
you want to see what building blocks exist before designing a pipeline with Claude.
Watch out
summaries are short; the schema tool goes deeper.

Sourcedocs.roboflow.com · September 30, 2026 ↗

workflow_specs_validate

Checks a Workflow JSON definition without running it, which catches mistakes before anything is saved or executed.

When it helps
Claude drafted a pipeline and you want to know it is valid before saving it.
Watch out
validating is not running.

Sourcedocs.roboflow.com · September 30, 2026 ↗

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.

When it helps
you want to see how the inspection pipeline is put together before touching it.
Watch out
one Workflow per request.

Sourcedocs.roboflow.com · September 30, 2026 ↗

workflows_list

Lists the saved Workflows in the workspace, so Claude can see which pipelines already exist before building another.

When it helps
you want to find the pipeline a colleague built last month for the loading dock.
Watch out
it lists saved ones only.

Sourcedocs.roboflow.com · September 30, 2026 ↗

What Claude changes (19)

19 tools

Nineteen 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 rule

Publishes the latest draft of a Workflow that the Roboflow agent edited.

What Claude asks for
Roboflow's page is silent on any prompt before publishing, so the general approval rule decides.
When it helps
the agent reworked your inspection Workflow and you are happy with the draft.
Watch out
it publishes the latest agent-edited draft, not an older one.

Sourcedocs.roboflow.com · September 30, 2026 ↗

annotation_jobs_create

Approval: see the rule

Creates a labeling job and moves images from a batch into it.

What Claude asks for
no source describes a Claude-side prompt before the job is created; the approvals section covers it.
When it helps
a new batch of warehouse photos needs to go to your labeling team.
Watch out
images leave the batch and move into the job.

Sourcedocs.roboflow.com · September 30, 2026 ↗

annotations_save

Approval: see the rule

Saves an annotation on an image that is already in the project.

What Claude asks for
nothing documents a confirmation before an annotation is saved; the default rule applies.
When it helps
Claude spotted a mislabeled box and you want the corrected label kept.
Watch out
it works on existing images only.

Sourcedocs.roboflow.com · September 30, 2026 ↗

autolabel_start

Approval: see the rule

Starts a hosted auto-labeling job over a batch of images.

What Claude asks for
whether Claude pauses before launching it is not documented; see the general rule.
When it helps
you have a fresh batch and want draft labels before your team reviews them.
Watch out
auto-labels still deserve a human pass before training.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_create

Approval: see the rule

Provisions a new edge device in the workspace.

What Claude asks for
a check before provisioning is described nowhere, so fall back on the general rule.
When it helps
a new camera box arrives at a second site and needs to be registered.
Watch out
look at the workspace default configuration first, since that is the baseline Roboflow keeps for devices.

Sourcedocs.roboflow.com · September 30, 2026 ↗

devices_update_config

Approval: see the rule

Updates the runtime configuration of a device.

What Claude asks for
no source describes a confirmation before a live device is reconfigured; the general rule is your safeguard.
When it helps
you want a site unit to run the newly trained model.
Watch out
it acts on hardware in the field, so check the history tool first.

Sourcedocs.roboflow.com · September 30, 2026 ↗

image_upload

Approval: see the rule

Uploads local image files to a project as a zip.

What Claude asks for
nothing published covers a prompt before the upload; the rule further down applies.
When it helps
you have a folder of new defect photos on your laptop.
Watch out
the upload runs as a task; the status tool follows it.

Sourcedocs.roboflow.com · September 30, 2026 ↗

images_batch_update_metadata

Approval: see the rule

Updates metadata and tags on several images in one call.

What Claude asks for
a confirmation for bulk metadata edits is described nowhere; see the approvals section.
When it helps
every image from one site should carry that site's tag.
Watch out
it touches many images at once.

Sourcedocs.roboflow.com · September 30, 2026 ↗

meta_feedback_send

Approval: see the rule

Reports a bug, a missing feature or a documentation issue to the Roboflow team.

What Claude asks for
no source describes a check before feedback goes out; the general rule applies.
When it helps
a tool keeps failing and you want Roboflow to know.
Watch out
it reaches Roboflow's team, not your colleagues.

Sourcedocs.roboflow.com · September 30, 2026 ↗

models_star_nas

Approval: see the rule

Stars or unstars a model found by neural architecture search.

What Claude asks for
nothing documents a Claude-side prompt for starring; see the general rule.
When it helps
one of the search's candidate models deserves to stand out for the team.
Watch out
it marks a model; it does not deploy it.

Sourcedocs.roboflow.com · September 30, 2026 ↗

projects_create

Approval: see the rule

Creates a new computer vision project in the workspace.

What Claude asks for
a prompt before a project is created is described nowhere; the approvals section applies.
When it helps
you are starting a new use case for shelf monitoring.
Watch out
a new project starts empty; images arrive through upload or come from a fork.

Sourcedocs.roboflow.com · September 30, 2026 ↗

projects_fork

Approval: see the rule

Queues an asynchronous fork of a public Universe project into your workspace.

What Claude asks for
no source describes a confirmation before the fork starts; the default rule covers it.
When it helps
a public helmet dataset fits your needs as a starting point.
Watch out
it runs in the background; the async task tool tells you when it is done.

Sourcedocs.roboflow.com · September 30, 2026 ↗

trainings_cancel

Approval: see the rule

Cancels a training run in progress.

What Claude asks for
whether a prompt appears before the cancellation is not documented; see the general rule.
When it helps
you realized the wrong dataset version was used.
Watch out
cancelling ends the run; stopping early is a separate tool.

Sourcedocs.roboflow.com · September 30, 2026 ↗

trainings_stop

Approval: see the rule

Requests an early stop on a training run in progress.

What Claude asks for
no confirmation specific to early stops is published; the general rule applies.
When it helps
the metrics have plateaued and more epochs would waste time.
Watch out
it is a request; the run winds down rather than vanishing.

Sourcedocs.roboflow.com · September 30, 2026 ↗

versions_export

Approval: see the rule

Checks or triggers a dataset export for a version.

What Claude asks for
a check before an export is triggered is described nowhere; the rule further down applies.
When it helps
you want the dataset in a format your own training script reads.
Watch out
it can only check an existing export, or start a new one.

Sourcedocs.roboflow.com · September 30, 2026 ↗

versions_generate

Approval: see the rule

Creates a dataset version with optional preprocessing and augmentation.

What Claude asks for
no source describes a Claude-side prompt before a version is created; see the approvals section.
When it helps
you finished labeling and want a version to train on.
Watch out
preprocessing and augmentation are both optional, so say which ones you want.

Sourcedocs.roboflow.com · September 30, 2026 ↗

workflows_create

Approval: see the rule

Creates and saves a new Workflow.

What Claude asks for
nothing published describes a prompt before a Workflow is saved; the general rule decides.
When it helps
you want a pipeline that detects people and blurs faces.
Watch out
validate the definition first to avoid saving a broken one.

Sourcedocs.roboflow.com · September 30, 2026 ↗

workflows_update

Approval: see the rule

Updates the name and definition of a saved Workflow.

What Claude asks for
no source describes a confirmation before a saved Workflow is rewritten; see the general rule.
When it helps
the pipeline needs an extra filtering step.
Watch out
the saved definition is overwritten, so validate the new one first.

Sourcedocs.roboflow.com · September 30, 2026 ↗

Unclassified (6)

6 tools

Three 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.

Watch out
whatever it ends up doing, the general approval rule covers it.

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.

Watch out
the general approval rule applies to it.

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.

Watch out
it falls under the general approval rule all the same.

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.

Watch out
the general approval rule covers it, like every other tool.

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.

Watch out
the general approval rule covers it either way.

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.

Watch out
whatever it triggers, the general approval rule applies.
Approvals

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.

Plans

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.

Limits

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.

Two official sources disagree

How many tools does the Roboflow connector expose?

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

Need help connecting Roboflow to Claude?

A person reads every message.

FAQ

FAQ on the Claude Roboflow connector

01What can Claude do with the Roboflow connector?
Claude can work across your Roboflow computer vision projects from a conversation. It searches Roboflow Universe and your own images, lists and inspects projects, versions, models and evaluations, runs hosted inference, and reads edge device logs, telemetry and configuration. On the writing side, it uploads images, starts auto-labeling, saves annotations, creates labeling jobs, generates and exports versions, stops or cancels training runs, and creates, updates or publishes Workflows. Six tools stay unclassified.
02Can Claude change, train or reconfigure things in Roboflow?
Yes, nineteen of the sixty-seven tools change your workspace. Claude can create or fork projects, upload images, save annotations, start auto-labeling, generate or export dataset versions, stop or cancel training, provision devices and update their live configuration, and create, update or publish Workflows. Six more tools stay unclassified, because no source says whether running them alters anything. Device configuration changes reach hardware in the field, so read those requests carefully.
03Does Claude ask before it acts in Roboflow?
By default, yes: Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to any Roboflow tool, so that default rule covers every change and every unclassified tool. Roboflow adds its own gate at sign-in, where you approve the permissions your client receives. On Team and Enterprise, owners can also close writing for the whole organization, and members cannot lift that.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule opens remote connectors to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner must enable the connector before members can connect. The Roboflow sheet in the directory, opened from your own account, is the only place that shows the current state.
05Does Claude see our whole Roboflow workspace?
It sees what your Roboflow account and the scopes you approved at sign-in allow, nothing more. Roboflow says each tool declares the permissions it needs and your client only receives those you accept, so a narrower approval means fewer working tools. Claude works with the rights of the person who connected. On a shared workspace, an owner can further restrict what the connector may do, and you can withdraw access from the Roboflow side.
06Why does Roboflow document 141 tools when Claude shows 67?
Because the two sources describe different lists. Roboflow's documentation, read in September 2026, says its server exposes 141 tools, from projects and training to API keys and trash recovery. The Claude directory sheet, read the same day, lists 67, and three of those names do not appear in Roboflow's documentation. This page documents the sheet's 67. What your own account shows after connecting is the list that counts for you.
07Claude or an automation tool for Roboflow?
They do different jobs, so choose by the task. Claude works inside a conversation: you ask, it searches, labels, trains or inspects, and nothing moves once you stop typing. It does not react on its own when a training finishes or a device goes offline. For a job that fires in the background on such an event, an automation tool is the right trade. For hands-on project work you steer, the connector fits.