Roboflow (Official)
Server Details
Roboflow computer vision for AI agents: datasets, annotation, versioning, workflows, inference.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Added
images_batch_update_metadata - Added
images_update_metadata
1 tool update
- Changed
autolabel_start6 fields changed- removed
Input schema / properties / ontology / additionalPropertiesRemoved value: -{ - "type": "string" -} - added
Input schema / properties / ontology / anyOfAdded value: +[ + { + "additionalProperties": { + "type": "string" + }, + "type": "object" + }, + { + "type": "null" + } +] - added
Input schema / properties / ontology / defaultAdded value: +null - changed
Input schema / properties / ontology / descriptionPrevious value: -"Mapping of class name -> text prompt used to label, e.g. {'cat': 'a cat', 'dog': 'a dog'}. Required. For sam3, max 50 classes."New value: +"Mapping of class name -> text prompt used to label, e.g. {'cat': 'a cat', 'dog': 'a dog'}. Required for foundational models (sam3: bare nouns, max 50 classes). Optional for model_type='roboflow' — when omitted, the trained model's own classes are used." - removed
Input schema / properties / ontology / typeRemoved value: -"object" - changed
Input schema / requiredPrevious value: -[ - "project_id", - "batch_id", - "model", - "model_type", - "ontology" -]New value: +[ + "project_id", + "batch_id", + "model", + "model_type" +]
1 tool update
- Changed
models_train4 fields changed- changed
Input schema / properties / checkpoint / descriptionPrevious value: -"Checkpoint to initialize from"New value: +"Checkpoint to initialize from (COCO, a Universe model, or a previous version)" - changed
Input schema / properties / epochs / descriptionPrevious value: -"Number of training epochs"New value: +"Number of training epochs (max 300)" - changed
Input schema / properties / model_type / descriptionPrevious value: -"Model architecture. Recommended: RF-DETR ('rfdetr-base', 'rfdetr-nano', 'rfdetr-large', etc). Also: 'yolov11n', 'yolov8n', 'yolo26n', etc. For NAS sweeps (one Training produces many child Models): 'rfdetr-nas-parent', 'rfdetr-nas-base-parent', 'rfdetr-nas-seg-parent'. NAS requires the version's validation split to have ≥15 images. Read the training-and-evaluation skill for the complete list of valid model IDs — wrong IDs cause failures."New value: +"Model architecture ID. Examples: 'rfdetr-medium' (object detection, recommended), 'yolov11n' (fast YOLO), 'rfdetr-seg-medium' (instance segmentation), 'yolo26n-pose' (keypoint), 'vit-base-patch16-224-in21k' (classification), 'qwen3_5-2b-peft' (multimodal/VLM). For NAS sweeps: 'rfdetr-nas-parent' (requires ≥15 validation images). If an invalid ID is passed, the API returns the full list of valid model types for the project's task. Read the training-and-evaluation skill for the complete list and model selection guidance." - changed
Input schema / properties / speed / descriptionPrevious value: -"Training speed"New value: +"Training speed (deprecated — model_type is usually sufficient)"
3 tool updates
- Added
create_project_app - Added
universe_dataset_images_search - Added
universe_search_app
5 tool updates
- Added
agent_chat - Added
agent_conversation_get - Added
agent_conversations_list - Added
agent_workflow_publish - Changed
models_train4 fields changed- changed
Input schema / properties / checkpoint / descriptionPrevious value: -"Checkpoint to initialize from (COCO, a Universe model, or a previous version)"New value: +"Checkpoint to initialize from" - changed
Input schema / properties / epochs / descriptionPrevious value: -"Number of training epochs (max 300)"New value: +"Number of training epochs" - changed
Input schema / properties / model_type / descriptionPrevious value: -"Model architecture ID. Examples: 'rfdetr-medium' (object detection, recommended), 'yolov11n' (fast YOLO), 'rfdetr-seg-medium' (instance segmentation), 'yolo26n-pose' (keypoint), 'vit-base-patch16-224-in21k' (classification), 'qwen3_5-2b-peft' (multimodal/VLM). For NAS sweeps: 'rfdetr-nas-parent' (requires ≥15 validation images). If an invalid ID is passed, the API returns the full list of valid model types for the project's task. Read the training-and-evaluation skill for the complete list and model selection guidance."New value: +"Model architecture. Recommended: RF-DETR ('rfdetr-base', 'rfdetr-nano', 'rfdetr-large', etc). Also: 'yolov11n', 'yolov8n', 'yolo26n', etc. For NAS sweeps (one Training produces many child Models): 'rfdetr-nas-parent', 'rfdetr-nas-base-parent', 'rfdetr-nas-seg-parent'. NAS requires the version's validation split to have ≥15 images. Read the training-and-evaluation skill for the complete list of valid model IDs — wrong IDs cause failures." - changed
Input schema / properties / speed / descriptionPrevious value: -"Training speed (deprecated — model_type is usually sufficient)"New value: +"Training speed"
1 tool update
- Changed
models_train1 field changed- changed
Input schema / properties / model_type / descriptionPrevious value: -"Model architecture ID. Use EXACT IDs below — wrong IDs cause failures.\n\nObject Detection (recommended → RF-DETR):\n rfdetr-pico, rfdetr-nano, rfdetr-small, rfdetr-base, rfdetr-medium, rfdetr-large, rfdetr-xlarge, rfdetr-2xlarge\n yolo26n/s/m/l/x, yolov12n/s/m/l/x, yolov11n/s/m/l/x, yolov8n/s/m/l/x\n yolo_nas_s/m/l, yololite-n/s/m/l/xl, yololite-edge-n/s/m/l/xl\n\nInstance Segmentation:\n rfdetr-seg-nano/small/medium/large/xlarge/2xlarge\n yolo26n-seg .. yolo26x-seg, yolov11n-seg .. yolov11x-seg, yolov8n-seg .. yolov8x-seg\n sam3-large\n\nKeypoint / Pose:\n yolo26n-pose .. yolo26x-pose, yolov11n-pose .. yolov11x-pose, yolov8n-pose .. yolov8x-pose\n\nClassification:\n vit-base-patch16-224-in21k, resnet18/34/50/101\n vit_base_patch16_dinov3.lvd1689m, vit_small_patch16_dinov3.lvd1689m\n\nSemantic Segmentation: deeplabv3plus\n\nMultimodal / VLM:\n qwen3_5-2b-peft, qwen3_5-0.8b-peft, qwen3vl-2b-instruct, qwen3vl-2b-instruct-peft\n smolvlm2-peft, smolvlm-256m-peft\n florence-2-base, florence-2-large, florence-2-base-peft, florence-2-large-peft\n paligemma2-3b-pt-224/448/896, paligemma2-3b-pt-224-peft\n qwen25-vl-7b, qwen25-vl-7b-peft\n\nNAS sweeps (produces many child models):\n rfdetr-nas-parent, rfdetr-nas-base-parent, rfdetr-nas-seg-parent\n NAS requires ≥15 validation images.\n\nRead the training-and-evaluation skill for model selection guidance, checkpoint options, and training best practices."New value: +"Model architecture ID. Examples: 'rfdetr-medium' (object detection, recommended), 'yolov11n' (fast YOLO), 'rfdetr-seg-medium' (instance segmentation), 'yolo26n-pose' (keypoint), 'vit-base-patch16-224-in21k' (classification), 'qwen3_5-2b-peft' (multimodal/VLM). For NAS sweeps: 'rfdetr-nas-parent' (requires ≥15 validation images). If an invalid ID is passed, the API returns the full list of valid model types for the project's task. Read the training-and-evaluation skill for the complete list and model selection guidance."
1 tool update
- Changed
models_train4 fields changed- changed
Input schema / properties / checkpoint / descriptionPrevious value: -"Checkpoint to initialize from"New value: +"Checkpoint to initialize from (COCO, a Universe model, or a previous version)" - changed
Input schema / properties / epochs / descriptionPrevious value: -"Number of training epochs"New value: +"Number of training epochs (max 300)" - changed
Input schema / properties / model_type / descriptionPrevious value: -"Model architecture. Recommended: RF-DETR ('rfdetr-base', 'rfdetr-nano', 'rfdetr-large', etc). Also: 'yolov11n', 'yolov8n', 'yolo26n', etc. For NAS sweeps (one Training produces many child Models): 'rfdetr-nas-parent', 'rfdetr-nas-base-parent', 'rfdetr-nas-seg-parent'. NAS requires the version's validation split to have ≥15 images. Read the training-and-evaluation skill for the complete list of valid model IDs — wrong IDs cause failures."New value: +"Model architecture ID. Use EXACT IDs below — wrong IDs cause failures.\n\nObject Detection (recommended → RF-DETR):\n rfdetr-pico, rfdetr-nano, rfdetr-small, rfdetr-base, rfdetr-medium, rfdetr-large, rfdetr-xlarge, rfdetr-2xlarge\n yolo26n/s/m/l/x, yolov12n/s/m/l/x, yolov11n/s/m/l/x, yolov8n/s/m/l/x\n yolo_nas_s/m/l, yololite-n/s/m/l/xl, yololite-edge-n/s/m/l/xl\n\nInstance Segmentation:\n rfdetr-seg-nano/small/medium/large/xlarge/2xlarge\n yolo26n-seg .. yolo26x-seg, yolov11n-seg .. yolov11x-seg, yolov8n-seg .. yolov8x-seg\n sam3-large\n\nKeypoint / Pose:\n yolo26n-pose .. yolo26x-pose, yolov11n-pose .. yolov11x-pose, yolov8n-pose .. yolov8x-pose\n\nClassification:\n vit-base-patch16-224-in21k, resnet18/34/50/101\n vit_base_patch16_dinov3.lvd1689m, vit_small_patch16_dinov3.lvd1689m\n\nSemantic Segmentation: deeplabv3plus\n\nMultimodal / VLM:\n qwen3_5-2b-peft, qwen3_5-0.8b-peft, qwen3vl-2b-instruct, qwen3vl-2b-instruct-peft\n smolvlm2-peft, smolvlm-256m-peft\n florence-2-base, florence-2-large, florence-2-base-peft, florence-2-large-peft\n paligemma2-3b-pt-224/448/896, paligemma2-3b-pt-224-peft\n qwen25-vl-7b, qwen25-vl-7b-peft\n\nNAS sweeps (produces many child models):\n rfdetr-nas-parent, rfdetr-nas-base-parent, rfdetr-nas-seg-parent\n NAS requires ≥15 validation images.\n\nRead the training-and-evaluation skill for model selection guidance, checkpoint options, and training best practices." - changed
Input schema / properties / speed / descriptionPrevious value: -"Training speed"New value: +"Training speed (deprecated — model_type is usually sufficient)"
2 tool updates
- Added
devices_get_default_config - Added
devices_update_config
11 tool updates
- Added
autolabel_job_get - Added
autolabel_start - Added
model_evals_get - Added
model_evals_get_confidence_sweep - Added
model_evals_get_confusion_matrix - Added
model_evals_get_image_predictions - Added
model_evals_get_map_results - Added
model_evals_get_performance_by_class - Added
model_evals_get_recommendations - Added
model_evals_get_vector_analysis - Added
model_evals_list
2 tool updates
- Changed
models_star_nas1 field changed- changed
Input schema / properties / model_id / descriptionPrevious value: -"NAS-trained model id (Firestore document id, from models_list[].id or trainings_get_results[].models[].modelId)."New value: +"Public model id (the `url` field from models_list[] or models[].modelId from trainings_get_results), e.g. 'beer-can-hackathon-410-nas-gpu-b'. Just the bare id — workspace prefix added automatically."
- Added
projects_health
18 tool updates
- Added
async_tasks_get - Added
devices_create - Added
devices_get - Added
devices_get_config - Added
devices_get_config_history - Added
devices_get_events - Added
devices_get_logs - Added
devices_get_telemetry - Added
devices_list - Added
devices_streams_get - Added
devices_streams_list - Changed
models_list1 field changed- added
Input schema / properties / groupAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional NAS modelGroup to scope the list to a single NAS run. Get this value from trainings_get_results." +}
- Added
models_star_nas - Changed
models_train1 field changed- changed
Input schema / properties / model_type / descriptionPrevious value: -"Model architecture. Recommended: RF-DETR ('rfdetr-base', 'rfdetr-nano', 'rfdetr-large', etc). Also: 'yolov11n', 'yolov8n', 'yolo26n', etc. Read the training-and-evaluation skill for the complete list of valid model IDs — wrong IDs cause failures."New value: +"Model architecture. Recommended: RF-DETR ('rfdetr-base', 'rfdetr-nano', 'rfdetr-large', etc). Also: 'yolov11n', 'yolov8n', 'yolo26n', etc. For NAS sweeps (one Training produces many child Models): 'rfdetr-nas-parent', 'rfdetr-nas-base-parent', 'rfdetr-nas-seg-parent'. NAS requires the version's validation split to have ≥15 images. Read the training-and-evaluation skill for the complete list of valid model IDs — wrong IDs cause failures."
- Added
projects_fork - Added
trainings_cancel - Added
trainings_get_results - Added
trainings_stop
1 tool update
- Changed
models_train1 field changed- changed
Input schema / properties / model_type / descriptionPrevious value: -"Model architecture (e.g. 'yolov8n', 'rf-detr-base', 'paligemma2-3b')"New value: +"Model architecture. Recommended: RF-DETR ('rfdetr-base', 'rfdetr-nano', 'rfdetr-large', etc). Also: 'yolov11n', 'yolov8n', 'yolo26n', etc. Read the training-and-evaluation skill for the complete list of valid model IDs — wrong IDs cause failures."
30 tool updates
- First observed
annotation_batches_get - First observed
annotation_batches_list - First observed
annotation_jobs_create - First observed
annotations_save - First observed
images_prepare_upload - First observed
images_prepare_upload_zip - First observed
images_search - First observed
images_upload_zip_status - First observed
meta_feedback_send - First observed
models_get - First observed
models_get_training_status - First observed
models_infer - First observed
models_list - First observed
models_train - First observed
projects_create - First observed
projects_get - First observed
projects_list - First observed
universe_search - First observed
versions_export - First observed
versions_generate - First observed
versions_get - First observed
workflow_blocks_get_schema - First observed
workflow_blocks_list - First observed
workflow_specs_run - First observed
workflow_specs_validate - First observed
workflows_create - First observed
workflows_get - First observed
workflows_list - First observed
workflows_run - First observed
workflows_update
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Machine-readable utilities and datasets for AI agents.
Build, validate, and deploy multi-agent AI solutions from any AI environment.
Video, audio, and image processing for AI agents: convert, transcribe, upscale - 150+ operations.
- mcp-serverOAuthcom.make
Give your AI agents the tools to build, manage, and run automation workflows.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to analyze images, extract text, compare images, and analyze video through any OpenAI-compatible vision model.411920MIT
- FlicenseNot gradedqualityAmaintenanceProvides AI assistants with a comprehensive computer-vision dataset toolkit for analyzing, curating, augmenting, and exporting datasets, including label error detection and automatic publishing.-

monday MCP Serverofficial
AlicenseAqualityCmaintenanceEnable AI agents to work reliably - giving them secure access to structured data, tools to take action, and the context needed to make smart decisions.852,433422MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read images with metadata, OCR text, regions, and citeable evidence without relying on generative LLMs.282MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Most tools have distinct purposes, but there are a few potentially confusing pairs like trainings_cancel vs. trainings_stop and workflow_specs_run vs. workflows_run, which could cause misselection by an agent.
Names follow a general verb_noun pattern but with inconsistent ordering: some are domain_first (annotation_batches_get) and others action_first (versions_export). This mix may reduce predictability.
With 46 tools, the set is large but covers many subdomains of a computer vision platform. It's on the heavy side but not excessive given the scope.
The toolset covers CRUD operations for projects, models, devices, and workflows, plus additional features like training and inference. Minor gaps exist (e.g., annotation deletion) but core workflows are well-supported.