The short version
There is no standalone MCP certification. Model Context Protocol is Anthropic's open protocol ↗, and competence with it is certified inside two Claude exams: the Claude Certified Architect - Foundations (CCA-F), under Domain 2 (Tool Design + MCP Integration), which is 18% of the exam and the heaviest MCP coverage of the two, and the Claude Certified Developer - Foundations (CCD-F), which has a dedicated Tools & MCPs domain (CCDVF-D8). The CCA-F is 60 questions, 120 minutes, 720/1000 to pass, five weighted domains, a $125 fee, valid for 12 months, launched 2026-03-12, eligibility gated through the Anthropic Partner Network ↗, and delivered via Pearson VUE. Vendor MCP tutorials from Microsoft, AWS and others are courses, not a certification. If you want a credential that proves MCP skill for Claude agents, pick by role: CCA-F for architect-level tool and server-boundary design, CCD-F if you build and ship the MCP servers yourself.
Is there an MCP certification?
No - not as a separate, registerable credential. People search for an "MCP certification" expecting a dedicated exam the way there are dedicated exams for cloud platforms or databases. That exam does not exist. MCP is a protocol, and Anthropic certifies protocol competence in context, as part of the broader job of designing agents on Claude.
That context is mainly the CCA-F, and also the CCD-F. Inside the CCA-F, Domain 2 (Tool Design + MCP Integration, 18%) is where MCP lives, and it is the heaviest MCP coverage of the two exams; inside the CCD-F, a dedicated Tools & MCPs domain (CCDVF-D8) tests the same protocol from the builder's side. So the precise, accurate statement is: you cannot get an MCP certification, but you can get the CCA-F or the CCD-F, and passing either certifies - among other things - that you can design tools and MCP integrations for Claude agents. If a site tells you to buy a standalone "MCP certificate," treat that as a red flag.
What is MCP?
MCP, the Model Context Protocol, is Anthropic's open protocol for connecting language models to external tools, data, and systems through a standard interface. Rather than writing bespoke integration glue for every tool, you expose capabilities through an MCP server the model can discover and call. The protocol standardises the tool-definition shape, the request and response envelope, and how structured errors flow back to the model so it can act on them.
For a deeper treatment of the protocol itself, the MCP concept page and the tool-calling concept page cover the loop end to end. The point for certification purposes is narrower: MCP is the connective tissue between an agent and the world, and the CCA-F tests whether you can design that tissue well.
What the CCA-F tests on MCP
Domain 2 (Tool Design + MCP Integration, 18%) is the domain that owns MCP. It breaks into four clusters, and the exam tends to test each through scenario stems rather than definitions.
- Tool and JSON-schema design. Clear, action-oriented tool names; typed parameters; schemas tight enough that the model cannot pass malformed input. Stems often ask you to pick the better of two tool definitions for a given task.
- MCP server design. When to expose a capability as an MCP server versus an inline tool, how to scope a server, and how to keep tool surfaces small enough that the model can reason about them.
- Error contracts. Structured, retryable-aware error responses that Claude can act on, instead of free-form strings or silent failures. This is the cluster that overlaps with reliability.
- Integration trade-offs. Inline tool vs MCP server vs wrapping a legacy or third-party API behind a thin MCP server. Stems present a constraint and ask for the right boundary.
The recurring test is judgment, not recall. You will rarely be asked to recite the protocol; you will be asked to choose the cleaner tool, the safer server boundary, or the error contract that lets the agent recover. For the error-contract cluster specifically, see MCP error contracts and retry behavior.
Other things people call an "MCP certification"
Several vendors publish MCP material, and search results blur it together with the idea of a certification. To keep the picture accurate, here is what is actually out there, at a safe altitude.
- Vendor MCP tutorials and learning paths. Microsoft and other platform vendors publish MCP integration guides and learning modules as part of their AI developer content (🟡 consensus - vendor catalogs change). These teach MCP; they do not certify it.
- Cloud-platform AI courses that touch MCP. AWS and similar providers cover MCP within broader agent-building material. Again: courses and learning paths, not a standalone MCP credential.
- Community workshops and bootcamps. Useful for hands-on practice. A certificate of completion from a workshop is not a vendor-recognised certification.
None of these is wrong to use - they are good practice. The distinction that matters for your resume is that the recognised certifications covering MCP competence on Claude are the CCA-F and the CCD-F (Domain 2 vs. CCDVF-D8), and the rest are supplements to them.
How to prep for the MCP portion
D2 rewards builders. The fastest path through it is to make the concepts concrete before you sit the exam.
- Learn the loop cold. Read the MCP and tool calling concept pages until you can trace how a tool result and a structured error return to Claude without looking.
- Build one small MCP server. Define two or three tools with clean JSON schemas. Deliberately model both a success response and a structured-error response. Watch how the agent behaves with each.
- Drill the trade-off questions. Run the agentic tool design scenario and the practice questions until tool-boundary and integration-trade-off stems feel routine.
- Connect MCP to reliability. Study how error contracts feed retry behavior, because D2 and D5 share the same ground. The error-contracts knowledge page bridges both.
How this maps to the CCA-F exam
References on this site
- Exam guide - CCA-F format, the five domains and their weightings, scoring, and validity.
- CCD-F exam guide- the Developer cert, whose dedicated Tools & MCPs domain (CCDVF-D8) is the builder-side path for MCP skills. See the CCD-F certification hub to compare.
- Registration - how to register through the Anthropic Partner Network and Skilljar.
- MCP concept page - the protocol, its envelope, and how structured errors flow back to Claude.
- Tool calling concept page - the loop that consumes tool and MCP definitions.
- Agentic tool design scenario - applied D2 practice on tool boundaries and structured errors.