Anthropic created MCP and open-sourced it in late 2024, but it is an open, model-agnostic spec now adopted across the industry, not an Anthropic-only technology.
Think about USB. One group helped design it, but USB is not owned by that group. Any laptop, phone, or charger maker can build a USB port, and they all interoperate. MCP is like that for AI tools. Anthropic published the design in late 2024 and gave it away as an open specification. By 2026 many tools, IDEs, and platforms implement it across model vendors, and the spec is developed in the open on GitHub by a multi-contributor working group. So when someone says MCP is 'an Anthropic thing', they are confusing who invented it with who can use or build to it. Inventing an open standard does not mean locking it down.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
This question is a misconception check, and it catches more candidates than you would expect. The Model Context Protocol came out of Anthropic, so a lot of people file it mentally as 'an Anthropic thing', the same way they might think of a proprietary SDK. That instinct is wrong, and being wrong about it signals you have not actually tracked how the agent-tooling landscape evolved through 2025 and into 2026.
The correct answer hinges on a single distinction: who creates a standard versus who owns and controls it. Anthropic created MCP and open-sourced it in November 2024. From that moment the specification was public, freely implementable, and explicitly model-agnostic. Creating an open standard is the opposite of locking it down.
This deep dive unpacks that distinction, walks through why MCP had to be open to do its job, lays out the 2026 adoption and governance picture, and gives you crisp language to defuse the misconception in an interview without overclaiming.
Created by is not the same as owned by
The root of the misconception is a category error. People hear 'Anthropic made MCP' and conclude 'MCP belongs to Anthropic', as if it were a closed product. Those are different claims, and collapsing them is where candidates go wrong.
Plenty of foundational standards were created by a single organization and then released for everyone. One group designs the spec, publishes it openly, and invites the world to implement it. The creator gets credit for the design and early momentum, but no exclusive control over who may build to it. The web itself started at one research lab and became something nobody owns. HTTP, JSON, and JSON-RPC all have origins in particular companies or individuals, yet none of them is anyone's property today.
MCP follows exactly this pattern. Anthropic authored the protocol and open-sourced it at launch in November 2024. The specification, the reference implementations, and the schemas were public from the start. Anyone could read the spec, build a server, build a host, or wire MCP into a model stack without asking Anthropic for permission or a license.
That is the defining property of an open standard, and it is the single fact that settles the question. Ownership in the proprietary sense, the power to charge for access, restrict who implements it, or close the spec, simply never existed for MCP. The right verb is 'created', and the right follow-on is 'and then gave away'.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
| Claim | Misconception | Reality (2026) |
|---|---|---|
| Ownership | Anthropic-only, proprietary | Open spec, freely implementable by anyone |
| Model support | Claude models only | Model-agnostic, any provider |
| Adoption | Used mainly by Anthropic | Broad cross-host: Cursor, Zed, Cline, Continue, Goose, and hundreds of community servers |
| Governance | Closed Anthropic process | Open RFC process on the modelcontextprotocol GitHub org; Anthropic as primary editor |
Real products, models, and research that use this idea.
- Cursor, Zed, Cline, Continue, and Goose all embed MCP clients, letting a single filesystem or Postgres server plug into many different IDEs.
- The official modelcontextprotocol GitHub organization hosts the spec and reference servers (filesystem, Git, Postgres, Slack, etc.); anyone can submit RFCs and contributions.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy did Anthropic open-source MCP instead of keeping it as a proprietary advantage?
Network effects: a protocol's value scales with adoption. Open governance recruits competitors as implementers, which is the only way to win the integration-standard fight.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Calling MCP 'Anthropic's proprietary protocol'. Anthropic created and open-sourced it, but it is a vendor-neutral spec any provider can implement.
60 second bullets to scan on the way to the call.
When Anthropic introduced and open-sourced MCP
The difference between creating a standard and owning it
Primary sources. Browse if you want the original framing.
Same topic, related formats. Practice these next.