Agentic AI Engineering Lab (Sprint #1) - Build a Production-Ready MCP Server

Agentic AI Engineering Lab (Tech Event, Sprint #1)
- Build a Production-Ready MCP Server

Move from prompting to architecting
The Model Context Protocol (MCP) is an emerging open standard for connecting AI apps/agents to real tools and data sources. This session is not a talk — it’s a hands-on lab where we build MCP servers that can be tested immediately with an MCP-capable client (e.g., Claude Desktop / your preferred agent setup).

The Format
We are planning a series of agentic ai tech meetings for deep building. This event may be attended alone or be seen as part / sprint of the event series with upcoming events building on top of what we build here.
This is a high-density micro-meetup limited to 6 seats. We prioritize builders: bring your laptop, ship code, and be ready to 'build and break' alongside other devs and engineers.

Future Sessions building on top may focus on ...
RAG systems, advanced MCP features, A2A, multi-agent workflows, production deployment Patterns or whatever we feel nice to build next.

(We run our sessions like an anthology series: Every meetup is a standalone sprint. While we often build on previous results, each session provides a complete experience and remains fully accessible to first-time attendees.)

What you'll build
After a quick alignment on the technical scope, the floor is yours: build your solution using the stack and tools that fit your workflow. We provide the framework; you provide the execution.
By the end, you’ll have a working MCP server (Python or TypeScript) with at least one real tool/resource, tested end-to-end.

Ideas: Choose one track (or bring own idea if it fits the scope)
For Beginners (Foundational)

• Personal knowledge server (local files/notes)
• Weather / external API integration
• GitHub issues helper

Intermediate

• SQLite query interface
• Slack/Discord notification tool
• CSV/Excel analyzer

Advanced

• Multi-API aggregator (e.g., calendar + weather + tasks)
• Document processor (PDF/DOCX parsing)
• Lightweight system monitoring/control

Schedule (Saturaday, 10:00 - 15:00 CET)

• 10:00–10:30 — Foundations + Live Demo
  Quick run through general MCP architecture (hosts/clients/servers), core primitives (tools/resources/prompts), basic patterns in order to get everybody on the same page.
• 10:30–11:00 — Environment Sync
  We wanna make sure everyone can run a “Hello World” MCP server (Python or TypeScript).
• 11:00–12:45 — Build Sprint (Lab Time)
  Implement your server + first tool/resource. Pair-debugging encouraged.
• 12:45–13:00 — Break (Pizza/Snacks)
• 13:00–13:30 — Test & Iterate
  Use MCP Inspector / your client to test, fix edge cases, tighten tool contracts.
• 13:30–15:00 — Demos + Technical Teardown
  Quick demos, what broke, what worked, and what we’ll harden in the next sprint.

Prerequisites (Please Read)

• You’re comfortable shipping small things in your preferred dev language and tools (e.g. Python, TypeScript/Node.js).
• Bring your laptop + basic dev setup (Git, package manager).
• Have access to an LLM client / API (Claude/OpenAI/etc.).
• This is a lab for engineers, not a tutorial. We solve architectural problems together, but you are the master of your own dev environment.
• Mindset: Build, Break & Iterate — broken code is welcome, passivity isn’t.

Logistics

• Location: Our private boardroom in the Grunewald area (near Martin-Luther Hospital). The exact address will be shared after RSVP.
• Capacity: 6 seats (first come, first served; deposit required)

Commitment Deposit and No-Show / Late-Show
This meetup is strictly non-profit. To respect everyone’s time and ensure all 6 seats are utilized by committed builders, a €15 deposit is required.

• The Deal: The deposit covers high-quality pizza, snacks, and drinks. Any surplus will be refunded to you via your original payment method after the event.
• Punctuality is Key: We start at 10:00 sharp with the technical foundations (door open from 09:45). To protect the group’s focus, late arrivals or no-shows will not be eligible for a refund. Their deposit will be fully contributed to the community's pizza & snack fund.
• Cancellations: No refunds for cancellations within 24 hours of the start time.