That’ll work; thanks for clarifying that you prefer this to be implemented on the user side.
I’ve used julia-mcp more regularly now, just wanted to say thanks again for this @aplavin !
Agreed! Thanks for making this. For my workflow, the design choices are excellent.
julia-mcp works very nicely out of the box, many thanks!
This question is perhaps more related to Claude: when working on code that produces PNG, it insists encoding everything to base64 which is very slow.: “Now let’s pull that PNG out of the Julia session (separate filesystem) by base64-encoding it through julia_eval..”. Is there a way to make it do a direct copy instead?
As often is, it was enough just to ask, like “Use julia-mcp for julia related invocations, not one in your own container. Do not use base64 encoding, but copy files directly and use SVG format.”
Hmmm, I wonder what is the scenario when it does base64? Is it for plots? I find that it just saves plots natively with like save() in julia.
Yeah, I think it wrote a heredoc and escaping did not work and after that it is trying to use base64 if anything fails (just to be sure, you know :-D). I am using now vscode where a different agent is behaving much better and julia-mcp works so well that you do not even notice it ;-)!