Conference talks, demos, and speaking materials.
| Date | Event | Talk | Speaker |
|---|---|---|---|
| 2026-09 | WeAreDevelopers World Congress NA, San Jose | Making (and Breaking) Agents by Adding 1,000 MCP Tools | Guillaume Lebedel |
| 2026-05 | May 2026 | Context is King: Optimizing Your Agent's Tool Layer | Romain Sestier |
| 2026-04 | AI Demo Day | Building Advanced Agents That Can Act with StackOne and ADK | Romain Sestier |
| 2026-03 | SaaStock Local London | The Agent IS the Product | Romain Sestier |
| 2026-02 | MCPconf @ ContainerDays London | Making (and Breaking) Agents by Adding 1,000 MCP Tools | Guillaume Lebedel |
| 2026 | ARIZE AI | Discode: Stop Wasting Tokens on Tool Schemas and Responses | Will Leeney |
| 2026 | Workshop | Supercharging Research with Agents | Will Leeney |
| — | Conference booth | StackOne Conference Booth loop | — |
| Folder | What |
|---|---|
mcp-app-blog/ |
Blog post + working code: "Build Your First MCP App: An Interactive API Explorer" |
Each talk lives in its own top-level folder, named after the talk (the folder name becomes
the URL path on talks.stackone.space). build.mjs auto-discovers any directory containing
a slides.html or index.html, and reads optional metadata from talk.json.
stackone-talks/
├── making-and-breaking-agents-sanjose-2026/ — Sept 2026 refresh (WeAreDevelopers NA)
│ ├── slides.html — the deck (export to PDF for Sessionize)
│ ├── talk-plan.md — timing and demo runbook
│ ├── speaker-notes.md — cues and audience questions
│ ├── content-review.md — sources and measurement limits
│ └── talk.json — metadata for the index page
├── making-and-breaking-agents-with-1000-tools/ — Feb 2026 original + demo agent
│ ├── slides.html
│ ├── scripts/ — talk outline
│ └── demo-code/agent/ — link to the replacement example
├── examples/sanjose-agent/ — AI SDK, Sonnet/Qwen, MCP and intercepted attack fixtures
├── context-is-king-may-2026/
├── discode-init/ — Discode talk + demo
├── supercharging-research/
├── adk-demo-2026/
├── saastock-local-2026/
├── conference-booth/
├── mcp-app-blog/ — MCP Apps blog post + API Explorer demo
└── README.md
Run npm test and npm run build at the repository root. The build copies presentation assets into public/; local demo code, environment files, notes and symlinks are excluded. The agent has its own install and checks in examples/sanjose-agent.