Model Context Protocol and Fireproof Demo: To Do List (opens in new tab)

(github.com)

2 pointsjchanimal1y ago3 comments

3 comments

3 comments · 2 top-level

bfeynman1y ago· 1 in thread

Is this supposed to be impressive? Rebranding function calling and moving that code to a different place?

I’m impressed by how easy it was, for someone new to all parts of the stack.

I agree MCP isn’t a big change, but that is a good thing. It’s more about making the implicit interface into something portable and reusable.

Most posix commands aren’t impressive in their own right, it’s the composability that gives them power. MCP plus data sync is similar.

jchanimalOP1y ago

This is just the first step in a bunch of cool stuff you can do. Now that the data is in a syncing database you can have models across multiple vendors and backends all working with the data locally while collaborating on changes. This means you can use the right model for the job without worrying about tracking where the data needs to go, instead each model can react to the appropriate fields and update types.

This is a super simple codebase so if you fork it and make something real, please share it with us.

j / k navigate · click thread line to collapse