
This article is part of The MCP Guide, our plain-English reference on the Model Context Protocol.
0 entries
The best MCP portfolio projects prove three things: you can build a working server, you can make it safe, and you can ship it so other people can use it. Ten small, finished projects with clear READMEs beat one sprawling demo. Each project below is tied to a documented MCP feature or vendor tool, so a reviewer can check your work against the official docs.
They are grouped by level. Start with a beginner project, then add one from each later group. Documentation for the tools mentioned was checked on 2 November 2026.
Key Takeaways
- Employers look for working code, security judgment and clear writing, not just "built an MCP server."
- Start read-only; a safe server is more impressive than a powerful, risky one.
- Show both transports: a local stdio server and a remote Streamable HTTP server with OAuth.
- Packaging and publishing (desktop extensions, the MCP Registry) prove you can ship.
- Every project needs a README with setup steps, a tool list, limits and a short demo.
- Never put real customer data or live secrets in a public repo.
What makes a project portfolio-worthy
Reviewers skim. Make each repo easy to judge:
- A one-line purpose at the top of the README.
- Setup in under five steps, tested on a clean machine.
- A tool table: name, what it does, read or write.
- Safety notes: scopes needed, what it cannot do, how errors look.
- A short recording or screenshots of a client using it.
- Tests, even a few, and a note on how you checked it with the MCP Inspector.
UK job ads that mention MCP most often also mention Python, LLMs and retrieval-augmented generation (RAG), according to ITJobsWatch data for the six months to 2 November 2026. Projects that combine those skills match what employers ask for.
Beginner projects
1. A read-only server for a public dataset
Wrap a public API, such as weather or open government data, as two or three read-only tools. Write precise descriptions and input schemas.
What it proves: you understand tools, schemas and the stdio transport. Follow our lesson on your first tool in Python.
2. A local SQLite explorer
Expose a sample SQLite database with tools to list tables, describe a table and run read-only queries with a row limit.
What it proves: you think about limits. Google's BigQuery MCP server, for comparison, caps results at 3,000 rows, per its docs. Mention a similar cap in your README.
3. A docs search server with resources
Index a small documentation set and expose it as searchable resources plus a "summarize section" prompt.
What it proves: you know tools, resources and prompts are different. See tools vs resources vs prompts.
Intermediate projects
4. A remote server with OAuth sign-in
Deploy a Streamable HTTP server that acts for a signed-in user, for example on a personal task list. Use OAuth, not a shared API key.
What it proves: production basics. Our lesson on adding OAuth covers the flow.
5. Split read and write tools with annotations
Take an existing API and design separate read, create, update and delete tools, each with a title and readOnlyHint or destructiveHint. Anthropic's connector review criteria reject a single catch-all tool that accepts both safe and unsafe HTTP methods, and require these annotations.
What it proves: you design for safety and for directory review.
6. A Claude desktop extension
Package project 1 or 2 as a .mcpb file with a user_config block for any API key, then sign it. The MCPB CLI provides init, pack, sign and verify.
What it proves: you can ship to non-developers. Follow our guide to build a Claude desktop extension.
7. A tool-search-friendly server
Build a server with 20 or more tools using consistent prefixes (such as crm_ and billing_), short descriptions with key words first, and server instructions. Explain in your README how it behaves when a client defers tools.
What it proves: you understand context cost. Claude Code's MCP docs say server instructions "become more useful with tool search enabled." Background: tool search and code mode.
Advanced projects
8. A paid tool on a test network
Add a pay-per-call tool using x402 on a test network. Cloudflare's x402 docs say to use base-sepolia with free test USDC for testing. Add spend limits on the client side.
What it proves: you can handle payments responsibly. Never use real funds in a demo. See MCP payments with x402 and Stripe.
9. A security review of your own server
Write a short threat model for one of your servers: assets, attackers, risky tools, and fixes you made. Include a prompt-injection test and how the server responds.
What it proves: senior-level judgment. Our MCP server security review guide gives a structure.
10. A custom Docker catalog for a fictional team
Package two of your servers as images and build a private Docker MCP catalog with an approval README. Docker's CLI docs cover docker mcp catalog create, server add and push.
What it proves: you think about teams, not just code. See custom Docker MCP catalogs.
Bonus: publish to the MCP Registry
Any project with a public package or public URL can be listed in the official MCP Registry. The registry verifies namespaces through GitHub or DNS, so a listing under your GitHub name shows you completed a real publishing flow. Validate your server.json with our server.json validator.
How to present the portfolio
| Item | Where |
|---|---|
| Three to five best repos | Pinned on GitHub |
| One-paragraph summary per project | Your CV or personal site |
| Short demo videos | Linked from each README |
| A write-up of one hard problem | Blog post or README section |
| Certificate, if you have one | CV, with the issuing body named |
Keep projects current. MCP changes quickly: the 2026-07-28 spec removed protocol-level sessions, for example. A note like "updated for spec 2026-07-28" tells reviewers you keep up. See what changed in 2026-07-28.
Mistakes that hurt a portfolio
- Public repos with API keys in the history.
- Servers that only work on your laptop.
- Write tools with no confirmation or limits.
- Copy-pasted tutorials with no changes.
- Old SSE-only examples presented as current.
Next step
Pick one beginner and one intermediate project and finish both before starting more. For a structured path, follow the MCP developer skills roadmap, and for more server ideas see our list of MCP server project ideas. Our MCP capstone lesson helps you plan a larger build.
More in the MCP Guide
Latest research: State of MCP: October 2026
Frequently asked questions
How many projects should an MCP portfolio have?
Three to five finished projects are usually enough if they show different skills: a local server, a remote server with OAuth, and one that is packaged or published.
Should I build on real company APIs?
Use public APIs, sample data or your own accounts. Do not use an employer's or client's data or credentials in public projects.
Do I need to deploy the remote server permanently?
No. A deployment guide and a short recording are enough for most reviewers. If you keep a live demo, add rate limits and keep it read-only.
Is a certificate better than projects?
They do different jobs. A certificate such as MCPA shows you studied the protocol. Projects show you can build and ship. Most hiring managers look at projects first.
Think your company belongs on this list? Ask us to review it. If it meets our quality standard, we will add it.
How companies are reviewed: we also write independent, fact-checked reviews of companies, with strengths and weaknesses, in Company Spotlight.











