weather-mcp-server

The LLM passes the HTML back in their response, translated, so it can be rendered to the user as-is. The tool description is self-explanatory: https://github.com/TuanKiri/weather-mcp-server/blob/master/i... You could have it respond with JSON, but then the rendering of the weather widget would have to be defined by the consumer instead of the tool server -- now the 'chat' part of your system needs to be aware of all possible content types, how to detect and render them; it's also doable but a different set of trade-offs.

The same lib is used in this project: https://github.com/TuanKiri/weather-mcp-server/blob/master/g...

I'm relatively new to Go, but recently got interested in how MCP servers work. I started thinking about what the architecture of such a project might look like, and decided to build a minimalist version as an experiment. I based it on my past experience writing regular REST API servers and figured it might be useful or interesting to others as well.