How I'm monitoring my MCP server logs

twitter.com

3 points·alrocar··5 comments

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.

Built something generic to monitor MCP servers (https://github.com/tinybirdco/mcp-tinybird/tree/main/mcp-ser...) using events + tinybird + prometheus + grafana, but I'm wondering what others are using for that purpose?

Are you finding building MCP integrations to be worth it? We've been using agents (e.g. langchain), which are pretty good at bringing in context and taking actions. Tool results become part of the context --it just works.

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).

i’ve been looking at your implementation as a reference, thank you

have you run into this weird bug which causes python MCP servers to crash when the MCP client times out? https://github.com/modelcontextprotocol/python-sdk/issues/88

also generally do you have any advice for how to notify Claude Desktop when a long running tool call is done? there are resource notifications but those must be selected by the user in the subsequent message

thanks!

mmm didn't know about that, but my server may have big latency so it could happen. I see there's a reproducer in the issue, I'll take a look.

Reply on news.ycombinator.com