Portfolio Projects and Capstone Roadmap
Project A — Developer Assistant
Capabilities: Repository metadata, documentation search, and issue lookup.
Architecture: Read-only tools + documentation resources + reusable review prompt.
Tests: Invalid paths, missing repository, pagination, and untrusted document injection.
Interview story: Explain why source reads are resources while searches with filters are tools.
Project B — Business Data Assistant
Capabilities: Customer/order lookup, validated filters, and role-based access.
Architecture: MCP adapter → service → authorization policy → repository.
Tests: Cross-customer denial, parameterized queries, timeouts, empty results, and pagination.
Project C — Support Assistant
Capabilities: Ticket lookup, draft creation, approved submission, and an audit log.
Safety: Separate read/write tools; writes require a preview, confirmation, and an idempotency key.
Final capstone
Build two servers and one custom host: a documentation server + a business server + a TypeScript client. Add tracing, an approval UI, failure recovery, deployment, a threat model, architecture decision records (ADRs), tests, a README, and a short demo.
Resume bullet template
“Built a TypeScript MCP system exposing validated tools and resources over stdio/Streamable HTTP, with role-based authorization, approval-gated writes, structured outputs, integration tests, and operational tracing.”
Use only the features you have actually completed and measured.
Can you explain it without the notes?
Portfolio Projects and Capstone Roadmap
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
Project A — Developer Assistant
Turn this concept into a clear answer.
Practice this conceptAdapted from 20_MCP_SERVER.md · “17. Portfolio Projects and Capstone Roadmap”. Examples are study fragments; framework behavior can depend on your version.