Ultralytics Platform MCP
MCP server for Ultralytics Platform workflows: projects, datasets, models, training, prediction, exports, and dataset uploads.
[!IMPORTANT] Independent community project. Not affiliated with or endorsed by Ultralytics.
Install · Tools · Safety · Troubleshooting
Try Asking
- "Show me my Ultralytics projects and which datasets are ready to train on."
- "Create a private project called traffic-cams and upload ./clips/junction.mp4 as a dataset."
- "Fine-tune yolo11n on traffic-cams for 50 epochs."
- "Fine-tune traffic-cams/detector across day-shots, then night-shots, in one run."
- "How is that training going? Show me the last 10 epochs of metrics."
- "Run the trained model on https://example.com/frame.jpg, then download the weights to ./weights."
- "Move my scratch project to trash." (restorable for 30 days)
https://github.com/user-attachments/assets/449d051b-d162-4539-93c5-94be478303f0
Installation
You need:
- Node.js =20
- An Ultralytics Platform API key
- ffmpeg and ffprobe on PATH, to upload a dataset from a local video file
- Claude Code, Codex, or another MCP client that can launch stdio servers
Get an API key
Sign in at Ultralytics Platform, open Settings - API Keys, and create or copy a key. The official API key docs cover creation, usage, and revocation.
Environment variables
| Variable | Required | Description | | --- | --- | --- | | ULTRALYTICSAPIKEY | ✅ | Ultralytics API key. Expected format: ul followed by 40 hex characters | | ULTRALYTICSAPIBASE | ❌ | Advanced: override API base URL. Default: https://platform.ultralytics.com/api |
Treat ULTRALYTICSAPIKEY as a bearer token. Pass it through your MCP client's environment configuration only. Never paste real keys into prompts, scripts, or committed config files. Project-scoped .mcp.json files are ignored by this repo to reduce accidental key commits; if a key is exposed, revoke it in Ultralytics Platform and create a replacement.
Standard config
Works in MCP clients that accept JSON stdio server definitions.