Understand how and why an agent picks your MCP server
- MCP tool descriptions are UX for agents
- How to tell an agent when NOT to use a particular tool
- Why naming tools is the most important thing you can do for your MCP server
Workshop
Build an MCP Product with AI
Your product needs an MCP server for agents to use it. Build it in 4 hours.
See syllabus and enrollWho this is for
Start where this matches your job.
- API and Platform PMs deciding when MCP is the right choice and scoping their first server.
- Engineers and Architects who want to rapidly build an MCP server to start testing tool calls.
- Technical Founders whose product needs to be discoverable by AI agents and must understand the UX and discoverability of MCP.
Syllabus
What you'll learn
Build and deploy MCP servers
- Build an MCP server from an existing API
- Build an MCP server from scratch, with Replit
- Know how to inspect and test MCP servers
Evals: the step most teams skip
- Collect golden prompts
- Set up Evals and scenarios
- Establish a baseline for improvements
Logistics
Prerequisites
- A working understanding of APIs and AI is a bonus. Helpful, not required.
- No coding skills are needed, though it would be an advantage. We'll build servers, but we'll use AI tools, so you don't necessarily need to know how to code.
- If you've used Replit before, you'll have a head start, but it's not necessary. A paid Replit account is good to have but you can build using the free version too.
Reviews
What students say
Very practical - it was nice to have a guided session on how to do this
Fit check
Is this right for me?
- Will I need to know how to code?
No. The exercises use Replit and no-code tools which handle the technical work. You'll prompt, not code.
- Do I need a paid Replit, MCPJam or Zuplo account?
Replit and MCPJam have a free tier that covers what we need. Zuplo's free tier works for the workshop. Paid tiers give you more but aren't required.
- I already use MCP servers. Is this too basic?
If you've installed servers but never built one, this is for you. Building is different from using. And even if you've built one, the Eval section alone is worth the session. As one student put it: "The eval is more important for me than getting the server working."
- This seems organizational, not just technical. Is that covered?
Yes. We cover when to pick MCP vs API vs CLI, how to scope tools, and how to make the case internally: what to build and why, then how to build it.
- I work full-time, what is the expected time commitment?
One 4-hour session. No pre-work required. Optional 30-minute meet-and-greet before and extended Q&A after.
- Can my employer reimburse this?
Many participants use L&D or professional development budgets. Maven provides expense templates to make the case.
Next step