That's exactly what zig-mcp does. It gives the LLM tools like search_std_lib, get_std_lib_item, and it decides when and how to use them based on context
LLMs have issues with zig, namely outdated docs. Then I found @jedisct1's project, context7 MCPwhich provides a way to search through zig docs using natural language: https://github.com/jedisct1/zig-for-mcp
But context7 returns semantically processed responses that often summarize or rephrase the information instead of quoting it. And that's why there is now zig-mcp which returns documentation in markdown format for stdlib and builtin functions
> Given that, we have not yet introduced any production applications written in Zig into our codebase (where the toolchain is fully set up), because only a few people in the company know the language at the moment.
Do you have any plans where you can use zig in production applications? Thanks!
No plans yet. In my opinion, it needs a good reason to be picked instead of C (which we have sizable) to overcome the "number of developers" argument.
Introducing a new general purpose language into a large company carries a significant cost, especially into the future. The company is rightly cautious.