llama.cpp Merged stdio MCP Support. Your Local Model Can Spawn Tool Servers Now.

PR #26062, "server: support MCP stdio," by ngxson, merged into ggml-org/llama.cpp on July 25 (r/LocalLLaMA). It landed alongside #26061 (vendored subprocess.h, merged July 24) and pwilkin's #26075 integration-and-tests PR.

Until now, llama-server's web UI could only talk to MCP servers already running over HTTP. That sounds like a small limitation until you go count how MCP servers actually ship: overwhelmingly as stdio subprocesses. Every filesystem server, every git server, every database connector in the ecosystem assumes the client spawns it as a child process and talks over pipes. Running those against a local model meant writing a proxy shim, and most people just didn't bother.

Now llama.cpp spawns the process itself. Your local GGUF reaches the same tool ecosystem Claude Code and Cursor use, with no adapter in between.

This is the operational answer to the token-rationing story. Everybody's cost thesis says "move cheap tasks to local models," but that thesis has been half-real because local models couldn't reach real tools. A model that can reason but can't read a file or query a database isn't going to absorb your cheap-task tier. That gap just closed.

The rest of the open-weight thread from this week reinforces it. Tobi Knaup, Mesosphere co-founder, argues open-weight AI is at the point Kubernetes reached before the community rallied around shared standards. Every lab ships different weight formats, quantization schemes, and inference requirements, so teams building on open models pick ecosystems instead of building applications (tobi.knaup.me). 390 points, 308 comments on HN. He's right about the fragmentation and I think he's right about the window.

Chen Chen's week-long Kimi K3 field report says K3 holds architectural patterns and naming conventions across dozens of files without drifting, matching Opus on instruction adherence and Fable on statistical analysis (chenchen.guru). The failures are operational: overload errors that interrupt long sessions and need retry logic, cases where the model emits only thinking tokens and stops with no content, tool calling that loops burning tokens without progress. Weights drop July 27, tomorrow.

And POCKET-35B-GGUF ships an Apache-2.0 repack of the Qwen3.5-35B-A3B MoE down to IQ1_M at 8.24GB and 1.9 bits per weight (HuggingFace via r/LocalLLaMA). Card-reported GPQA-Diamond of 68.7% at Q4_K_M. But check the numbers before you plan around them: the Reddit post advertises 59 tok/s on CPU while the model card itself cites 27.0 tok/s on a 16-thread Xeon at IQ1_M and 13.8 tok/s on an 8-thread M3 Pro. That's a 4x gap between the headline and the card. Benchmark it yourself.

Go pull llama.cpp and point it at a filesystem MCP server tonight. It's the highest-value 20 minutes available to you this week.