Building MCP servers that don’t collect dust #68
Description
About You
Your Name:
Tom Johnson
Twitter or Linkedin handle (optional):
Twitter: https://x.com/tomjohnson3
LinkedIn: https://www.linkedin.com/in/tomjohnson3/
The best way to reach out to you:
Email: thomas [dot] johnson [at] multiplayer [dot] app
Your Talk
Title:
Building MCP servers that don’t collect dust
What your talk is about:
This is an interactive session about the best practices when building MCP servers, followed by a practical, hands-on demonstration of how we built the MCP server for Multiplayer.
We’ll go over how it works to feed full stack session recordings into AI IDEs, the architecture we choose, the trade offs we considered, the constraints we implemented and practical use cases we designed for.
As an example of the best practices I’ll discuss see this interview: https://leaddev.com/ai/lessons-learned-launching-mcp-server
How long will your talk be?
- 20-30 minutes
- 30-45 minutes
- 60 minutes or more
15-20 min presentation + 10 min Q&A
Meetup event Copy - Optional
This will show up on your Meetup.com Event page for your talk. Example event page.
Event Title:
Building an MCP server that won’t collect dust
Event Description:
MCP servers are everywhere, but most are collecting dust. This talk will be an interactive session about the key lessons we learned to avoid that, and the best practices we followed when building the Multiplayer MCP server.
We’ll go over how it works to feed full stack session recordings into AI IDEs, the architecture we choose, the trade offs we considered, the constraints we implemented, and practical use cases we designed for.
Speaker Bio:
Tom Johnson is the Co-founder and CTO at Multiplayer, with 30+ years of experience as an engineering leader and backend developer building large-scale distributed software (and robots!)