The results are in!
We're thrilled to announce our winners for the Notion MCP Challenge! From dynamic creative journals to meal planning assistant...
For further actions, you may consider blocking this person and/or reporting abuse
No way! This win means so much to me for so many reasons. Huge thanks to the DEV and Notion teams, this really motivates me to keep participating in more and more challenges.
When I first started using Notion as my productivity tool, I was really impressed by the idea behind it, and I never would have imagined that I'd one day be a winner of a challenge related to such an amazing company! I'm incredibly happy!
Congrats to the runner ups as well, you did an amazing job! 🏆️
Just reached and opened mail. Can not believe it finally after 2 years on writing blogs and building projects, finally achieved a major win, very glad that the community loved the idea. Very grateful for the @georgekobaidze for the ultimate win, and congratulations to @caposto for getting reward as runner up as well. Thanks a lot, @thepracticaldev @jess
Congrats. Great job! Keep on writing and building!
Congrats!
Thank you Notion for sponsoring and @thepracticaldev for organizing this challenge! Definitely learned a lot and I am very greatful for the recognition. Congrats to @georgekobaidze and @yashksaini as well!
Great job!!🔥🔥
Congrats!! 🥳
Congrats to all of the winners and to everyone who submitted a project.
Congrats!!👏
Congrats!
By the way @jess how can we get the prize money, and also does the new membership subscription get's add on top of previos one if we won previously
The hybrid pattern NoteRunway uses — direct API for reads, MCP for destructive writes — is one of the best architectural decisions I've seen in MCP projects. I run a production MCP server over a 130k-node Neo4j graph, and we arrived at the same conclusion independently: MCP adds real value as a safety layer for mutations, not as a universal API wrapper.
The temptation is to route everything through MCP for consistency. But read-heavy workloads pay a real latency penalty for the extra round-trip through tool dispatch. NoteRunway's approach gives you speed where it matters (bulk reads) and governance where it matters (writes that change state).
Relay's agent-driven tool selection is interesting too — the distinction between hardcoded tool calls and letting the agent decide which MCP tools to invoke maps to something we've seen in multi-agent systems: agents that discover tools at runtime make fewer errors than agents with a fixed tool manifest, because the discovery step forces them to match the tool to the actual task rather than pattern-matching on tool names.
Congrats to all the winners.
Wow mate, it was indeed a journey for you, 2 years of improvisation and now getting into the top... Bravo!!
Congrats!👏
Congrats!👏
Congrats!!🤩
Congrats!