The MCP Practitioner Course · Lesson 7 of 7

Capstone — Ship a Real MCP Integration

> Two-week build. The portfolio artifact you walk into your first sales meeting holding.

The course ends here, but the work doesn't. The capstone is a two-week build that turns the methodology in this course into a real artifact you can hand to a paying client, a hiring manager, or your boss as proof you can ship MCP work end-to-end.

Pick one client (real or fictional). Pick one of the three patterns (helpdesk, CRM, finance) or a custom pattern grounded in a real workflow. Build it for real. Deploy it for real. Write the security review checklist for real. Hand it to a real human and watch them use it.

---

The brief

You have two weeks. Build a remote MCP server, OAuth-protected, deployed to a real hosting platform, integrated with a real or sandbox SaaS backend, exposing 4–8 tools and 1–2 prompts. Connect it to Claude Desktop or Cursor and demonstrate at least three different conversational scenarios where the agent uses it productively.

Your capstone deliverable is a single packet (folder, GitHub repo, Notion page — your choice) containing:

  • The MCP server source code with structured logging, tests, and a CI workflow that runs the tests.
  • A README that walks a stranger through running it locally and deploying it. Include the auth setup steps.
  • The 21-item security review checklist filled in for your specific deployment.
  • The one-page runbook from Module 6.
  • A 5-minute Loom or similar video of the agent using your server in real time, with you narrating what's happening.
  • A two-page client deliverable: the server's purpose in plain English, the workflows it agentizes, the time-saved-per-week claim, the price you'd quote for an equivalent client engagement.

---

The grading rubric (use it on yourself before showing it to anyone)
  • Does it work end-to-end? Boots, authenticates, executes tool calls successfully, returns useful content. Pass/fail.
  • Are the tool descriptions good? Read them aloud. If they sound like API docs, they're not good. If they sound like prompts that tell the model when to use the tool and when not to, they're good.
  • Is the auth real? Real OAuth provider, real scopes, real validation, no hardcoded secrets. The Module 4 lab is the floor, not the ceiling.
  • Does the security checklist pass? Walk the 21 items. Anything checked "no" is a known limitation; anything ambiguous is a problem to fix before you'd ship to a client.
  • Is the runbook actionable? Could someone other than you operate the server using only the runbook? If not, fix it.
  • Is the client deliverable believable? Read it as if you were a CFO. Does the time-saved claim hold up? Does the price feel calibrated? If not, recalibrate.

---

What you do with it

Three options, in order of impact:

  • Take it to a real client. If you have a current relationship with an SMB, this is what you walk into a strategic review with. "Here's something I built. Want me to do this for your environment?"
  • Use it as a portfolio piece. Put it on your firm's site, in your LinkedIn, in your sales emails. The Loom video is the highest-leverage 5 minutes of marketing material you can produce.
  • Open-source it (if appropriate). If the integration is generic, ship it on GitHub. The repo becomes a credibility marker that feeds inbound interest. Watch your maintenance load — open-source MCP servers attract issues fast.

---

The line you cross

Most people who read about MCP never ship anything. The ones who do the capstone are the ones who become the people their IT partner/firm/department turns to when an MCP question comes up.

The line between "I read about MCP" and "I am the MCP person here" is one capstone. Two weeks. Pick the client, ship the work, write the deliverable. After that, every module in this course becomes a tool in your kit instead of a thing you read once.

---

What's next

If you finished the capstone, you have everything you need to run a real MCP engagement. Three suggestions for where to take it:

  • Read [Book 7 — The MCP Practitioner Playbook](/books/mcp-practitioner) for the deeper version of every chapter in this course. Same voice, ~218 pages, includes appendices with the spec quick reference, the tooling cheat sheet, and the dozen most common errors.
  • Pair it with [Book 6 — The Process Capture Playbook](/books/process-capture) for the audit methodology you'll use during discovery on every MCP engagement. The two together form the complete commercial system.
  • Use the [Process Capture Audit tool](/tools/process-audit) during the discovery phase of every engagement. The workflow inventory it produces drives which MCP server to build first.

Pick the first client. Send the first email. Ship the work.

— John E. Martines, Applied AI Technology

Previous: Productizing MCP as a Service · Back to the course