Tuist supports now analyzing bundles, allowing developers to push the analysis to the server for a visually-rich presentation, and over-time analysis. They can also export it as a JSON:
tuist inspect bundle --json --path MyApp.ipa
Developers can use this feature to get the bundle’s JSON representation and paste it in an LLM chat interface to ask questions about it. But wouldn’t it be better if we got rid of that indirection and developers could easily load that context into the chat application without having to run commands and copy the output?
We have all the foundational pieces to enable that workflow: the business logic to generate the reports, and an MCP server to expose them as resources. Tuist could look up bundles in the derived data directory, and expose them as resources of the MCP server; that way, developers could select an app from Derived data (e.g. MyApp.app (Debug)
) and the resource would get loaded right away.
Thoughts? If anyone is interested in taking this on, we can give you the pointers to push this to the finish line. Since most of the foundational pieces are in place, connecting them to shape a new feature is a matter of connecting them.