We made the exercise to building a "wrapped" kind of feature for our users.
Being an analytics data platform on top of CLickHouse made it "simpler" because we are used to develop and support that kind of uses cases, but still that's the full story for those interested on the internals of those kind of features.
Good thing to me (besides being an open spec) is their simplicity, with libraries such as FastMCP you can just bring stuff you already have implemented into Claude (or any MCP client).
We recently built an MCP server (https://github.com/tinybirdco/mcp-tinybird/tree/main) so our users could ask questions to their workspace. We released fast and since MCP servers run locally we lacked observability on product metrics, error monitoring and all that stuff you usually want when you are in production.
Thanks for this comment. I guess there's sometimes we (developers) take things for granted when they are not, and that puts a lot of pressure on us instead of celebrating our wins.
I would change now "pretty standard" by "we don't invented the wheel" xD :pray:, in the end I wanted to mean we use existing tools and "just" put them together
Yep, it's part of our culture, we do many releases per day to constantly iterate things. Also as in other projects there are maintenance and bug fixing we want to bring to production as soon as possible.
Our context is the one of a startup that is constantly validating things, also in our context a release does not necessarily mean releasing to the users, sometimes stuff is behind feature flags or for beta testing.
Being an analytics data platform on top of CLickHouse made it "simpler" because we are used to develop and support that kind of uses cases, but still that's the full story for those interested on the internals of those kind of features.