Roboflow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBOFLOW_API_KEY | Yes | Your Roboflow private API key | |
| ROBOFLOW_API_URL | No | Override the API base (default https://api.roboflow.com) | |
| ROBOFLOW_WORKSPACE | No | Default workspace slug, so tools can omit it | |
| ROBOFLOW_MCP_LOG_LEVEL | No | DEBUG, INFO, WARNING, ERROR (default INFO) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roboflow_get_workspace | Get a Roboflow workspace's metadata and its projects. Pass |
| roboflow_list_projects | List all projects in a Roboflow workspace. Lighter than |
| roboflow_search_images | Search images in a Roboflow project. Filter by |
| roboflow_add_image_tagsC | Add one or more tags to an image. Additive; not destructive. |
| roboflow_remove_image_tagsA | Remove tags from an image. Destructive: requires |
| roboflow_set_image_tags | Replace an image's tags with the given list. Destructive: requires |
| roboflow_upload_imageA | Upload a single image to a Roboflow project.
Every mode runs through URL / path / image safety guards
before the upload. |
| roboflow_upload_images_batchA | Upload many images concurrently.
|
| roboflow_delete_image | Delete an image. Destructive: requires confirm='yes' and ROBOFLOW_MCP_MODE=curate or full. |
| roboflow_get_image | Get the metadata of a single image. |
| roboflow_list_image_batchesC | List upload batches for a project. |
| roboflow_upload_annotationC | Attach an annotation to an image. Supported formats (
Pass |
| roboflow_get_project | Read project metadata (classes, image count, splits). |
| roboflow_list_annotation_jobsA | List a project's annotation jobs (Annotate-tab batches). Each job reports labeling / review progress; |
| roboflow_add_reviewed_to_datasetA | Add every fully-reviewed annotation job to the dataset. Moves images from jobs in review with all images approved into
the dataset, split randomly at the given global ratios
(default 70/20/10). Restrict to specific jobs via Destructive: requires |
| roboflow_list_versions | List dataset versions under a project. |
| roboflow_get_version | Read one version's full metadata. |
| roboflow_create_versionB | Kick off an async version generation (quota-heavy). Destructive-of-quota: requires confirm='yes' and
ROBOFLOW_MCP_MODE=curate or full. After this returns,
poll |
| roboflow_get_version_generation_status | Poll the async generation state of a version. |
| roboflow_export_versionA | Request an export for a trained/generated version. Returns a signed download URL when ready. Does NOT stream
bytes — pair with |
| roboflow_delete_versionA | Delete a dataset version. Destructive: confirm='yes' required. |
| roboflow_download_export | Stream an exported dataset zip to disk. Writes under ROBOFLOW_MCP_EXPORT_CACHE_DIR (default
Destructive-to-fs: requires confirm='yes' and ROBOFLOW_MCP_MODE=curate or full. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct action or resource: image tagging (add/remove), upload (single/batch), annotation, version management (create/delete/export), listing jobs/batches, and dataset addition. Even similar operations like single vs batch upload are clearly differentiated.
All tools follow a consistent 'roboflow_verb_noun' pattern in snake_case (e.g., roboflow_add_image_tags, roboflow_upload_image). The naming is predictable and easy to parse.
With 11 tools, the set covers the primary operations of a Roboflow MCP server without being bloated. Each tool serves a clear purpose, and the count feels appropriate for the domain.
The tools cover image upload, annotation, tagging, version CRUD (except list/get versions), and dataset addition. However, missing operations include retrieving version details, listing versions, deleting images, and polling version generation status (despite being referenced in create_version). These gaps may hinder full workflow automation.