YOUR_ROBOFLOW_API_KEY with your actual key):claude_desktop_config.json:~/.codex/config.toml:~/.cursor/mcp.json):The Roboflow MCP Server is a hosted Model Context Protocol (MCP) server at mcp.roboflow.com that gives AI coding agents direct access to a Roboflow workspace. It exposes 30 tools across projects, datasets, training, Workflows, and Universe, so any MCP-compatible client (Claude, Claude Code, Cursor, Codex, Windsurf, Continue) can manage computer vision projects through natural-language prompts. The one-command installer wires up the server connection along with Skills, expert markdown playbooks the agent reads as MCP resources.
MCP gives your agent the tools (verbs). Skills give it the expert knowledge (when, why, and how). Tools are live primitives like 'create a project' or 'run a Workflow.' Skills are durable markdown playbooks: api-reference, data-management, inference, plans-and-pricing, product-navigation, training-and-evaluation, and universe.
The REST API is for code. MCP is for agents. The server speaks streamable HTTP at /mcp and presents 30 tools your AI agent can discover and call directly. It is tuned for natural language to tool call workflows rather than hand-written integrations.
The plugin manifest ships for Claude Code and Codex. The Skills CLI installs standalone Skills into Claude Code, Cursor, OpenCode, and any agent that reads SKILL.md files. The MCP server itself works with anything that speaks MCP over streamable HTTP.
The MCP server is hosted at mcp.roboflow.com, so it runs in the cloud. The plugin install pulls the Skills bundle and writes the MCP config locally so your agent knows about the server. If you only want the live tools, paste the .mcp.json snippet from this page into your client config by hand instead.
Set ROBOFLOW_API_KEY in the shell that launches your agent (run export ROBOFLOW_API_KEY=your_key, or add it to ~/.zshrc or a project .env). The plugin reads the value from your environment; direct MCP clients pass it in the x-api-key header. Grab a key from app.roboflow.com/settings/api.
Yes. claude plugin install roboflow --scope local writes the plugin into the current project only and reads the API key from that project environment. Useful when different projects need different ROBOFLOW_API_KEY values for different workspaces.
The MCP server, Skills, and plugin are free and open source under Apache-2.0. You only pay for the underlying Roboflow usage on the same plans you already have.
Open an issue or PR on roboflow/computer-vision-skills. Skills are markdown; contributions are mostly editing or adding files under skills/, each with a SKILL.md frontmatter block.