17 August 2026 · 7 min read
Claude Skills vs Projects vs MCP: What's the Difference?
A clear breakdown of Claude's Projects, Skills, Connectors and MCP servers — what each one is for, and when to reach for which.
Projects — grouping context, not automating anything
A Project groups related chats and uploaded files under one set of standing instructions and context. One Project per client, per case, per course — Claude stops needing to be re-briefed every time. It's the simplest of the four, and the right starting point for anyone doing recurring work with the same context.
Skills — reusable, named workflows
A Skill is a reusable, named workflow Claude loads on demand — you teach it your firm's exact way of doing something, once, and Claude reaches for that instruction set automatically when a relevant task comes up. The anatomy is simple: a SKILL.md file with a frontmatter (name + description — the trigger Claude reads first) and a body (the actual Markdown instructions, loaded only once the skill activates). Claude only reads the frontmatter at startup — a cheap 'table of contents' — so having many Skills doesn't cost tokens until one actually fires.
Connectors — built-in integrations
A Connector is a native, built-in integration — Gmail, Calendar, Drive — the same idea as installing a Chrome extension. Claude reaches into a connected app directly, following whatever permission scopes you grant.
MCP — the general, extensible version
MCP (Model Context Protocol) is the more general mechanism behind Connectors — and it extends further, to servers you or your organization build yourselves. A local MCP server runs on your own machine through Claude Desktop (for example, a local Python GST-reconciliation script that shares only the limited output Claude actually needs — nothing else leaves the machine). An online MCP server is a custom connector you host yourself as a web service that accepts MCP requests.
Which one do you actually need?
Start with a Project the first time you have recurring context for the same client or task. Move to a Skill once you notice yourself typing the same instructions across multiple chats. Reach for a Connector when the work genuinely requires touching another app (email, calendar). Only build a custom MCP server when you have a specific tool or data source that nothing built-in already covers — it's real engineering work, not a first step.
Want to go deeper, live, with direct Q&A?
Level 2 builds all four, hands-on, in 3 days →