Show HN: I built an MCP server using Cloudflare's code mode pattern

Show HN: I built an MCP server using Cloudflare's code mode pattern(github.com)

87 points by jmcodes 277 days ago | 29 comments

Read this article by Cloudflare this morning https://blog.cloudflare.com/code-mode/ the main argument being that LLMs are much better at writing typescript code than tool calls because they've seen typescript code many more times.

HN Discussion: https://news.ycombinator.com/item?id=45399204 https://news.ycombinator.com/item?id=45386248

Deno provides a great sandbox environment for Typescript code execution because of its permissions system which made it easy to spin up code that only has access to fetch and network calls.

Stick an MCP proxy on top of that and you've got "CodeMode" (code intermixed with MCP tool calls) for more advanced workflow orchestration.

https://github.com/jx-codes/codemode-mcp

There's a lot of things that can be improved here. Like a virtual file system for the agent to actually build up its solution instead of being forced to one shot the solution but the bones are there.

WilcoKruijer 277 days ago |

I find it interesting how this project uses all three major JavaScript runtimes in a single project. Bun for the code itself, Deno for sandboxing and Node for running the MCP server. Says something about the ecosystem.

jmcodes 277 days ago | |

Says something about my coding haha.

Yeah since it's using Deno it'd be cool just use Deno throughout. Definitely gotta clean up the code quite a bit.

gvkhna 277 days ago | | |

Nice my project also uses Deno for sandbox and bun runtime because it just works.

http://github.com/gvkhna/vibescraper

I told Jared if bun had a sandbox i’m pretty sure everyone would use it.

malnourish 277 days ago | | |

Why Deno over Bun? Forgive my naivety, I was a backend dev for years and am only now familiarizing myself with the JS/TS ecosystem

cpard 277 days ago |

The valuable lesson from what Cloudflare claims is that if you want to make an LLM perform as you expect you have to build considering their strengths and weaknesses.

You can see the same behavior if you try to ask an LLM to code in an API that is not commonly used.

When it comes to MCP tooling I followed a different path but with similar assumptions.

There are tools that LLMs have been Rled to death to use. So I’m modeling my tools after them.

Specifically, I try to have a “glob” tool, used to let the LLM figure out structure. A search and a read tool and use regexp as much as possible for passing parameters.

You can see an early version of this pattern here: https://github.com/typedef-ai/fenic/blob/main/examples/mcp/d...

It has been working well, at least in terms of the model knowing how to invoke and use the tools.

I have to say though that each model is different. I see differences between Claude code and Codex when I use the MCP for development, at least on how good they are in retrieving the information they need.

Maybe I should try to run some benchmarking and compare more formally

Palmik 269 days ago |

Many [1] models expect (MCP) tool calls to be formatted as a JSON. So if you expose code execition as an MCP tool to such model, it will have to generate the code escaped as a JSON string. I would exepct this to tank code generation quality.

[1] Not all, some use different formats, e.g. GLM uses plain text with special tokens to denote param names and values.

gavmor 277 days ago |

> LLMs are much better at writing code than at tool calling.

Wait, really? This is harder to get right:

``` { "jsonrpc": "2.0", "id": 102, "method": "tools/call", "params": { "name": "book_flight", "arguments": { "origin": "SFO", "destination": "JFK", "departureDate": "2025-10-15", "returnDate": "2025-10-18", "passengers": 2, "cabinClass": "business" } } } ```

Than the equivalent... but with `method: "POST"` boilerplate, etc? Or is it literally the chaining of tools that's missing from—and fundamentally faulty in—MCP client implementations?

jmcodes 277 days ago | |

So this is a first pass to capture the workflow part (mix code and MCP calls).

The fetch code isn't any better than the tool code I agree, but typescript code is more common so I'd guess this would be too?

But anyway I think the real power comes with the type-safety part that I left out this morning (working on it now). From what I understand Cloudflare is essentially generating an SDK for the LLM to write code against.

Instead of writing that fetch call. The LLM would generate

``` const redditResults = await redditMCP_getTopPosts(subreddit); const insertMutation = await duckdb_Insert("SQL STUFF", redditResults.map(...)); const results = await duckDb_Query(args: duckDb_QueryArgs); return resultsInSomeNiceFormat; ```

Where the method names come from the MCP server tools, and the argument types are autogenerated from the MCP schemas themselves.

No idea if this is a valuable workflow or not personally. I just thought it was cool and wanted to tinker with it.

danielser 277 days ago | | |

Correct, this is like giving the LLM full specs on your GraphQL endpoint, and telling it have fun, get only what you need.

Except it can use Typescript to manipulate the data mid stream.

So in reality this is MCP Middleware + MCP Orchestration + Tool Call Efficiency.

It will save tokens as well due to only returning what it needs, but more so just think of going from 10 consecutive tool calls, to 1 call that gives you everything you need and nothing you don't, with 1/10th the time taken to accomplish.

jmcodes 276 days ago |

https://github.com/jx-codes/mcp-rpc

For those of you interested, I wrote out and built an more RPC typescript centric approach to avoid using other MCP servers at all. Would appreciate some thoughts!

https://news.ycombinator.com/item?id=45420133

fabmilo 277 days ago |

I was just reflecting on this blog post after reading it this morning. What do you think on code mode after implementing it? At this point would not be better to just have a sandboxed api environment with customizable api/tools endpoints? basically an RL environment :)

evertedsphere 277 days ago |

also seen in

https://lucumr.pocoo.org/2025/8/18/code-mcps/

kordlessagain 277 days ago |

This is a terrible idea masquerading as innovation. Cloudflare wants you to believe LLMs write TypeScript better than they make tool calls, but they're really just creating another dependency on their infrastructure.

1. Tool calls are intentionally simple; adding a code generation layer introduces needless complexity and failure points.

2. Cloudflare already acts as a man-in-the-middle for ~20% of the Internet with limited transparency about government data requests

3. This is clearly designed to drive adoption of their Worker platform and create lock-in for AI agent developers

Similar to their x402 payment scheme that reinvents HTTP 402 under their control, the community has already built alternatives (see the Aperture implementation from Lightning) that don't require surrendering more of your stack to Cloudflare.

Remember what's happening here: a company with unprecedented visibility into web traffic wants even more control over how AI agents interact with the internet. Even if you don't believe that AI will eventually self govern itself, this is a horrible idea to limit individual's ability to automate portions of their access to the web.

No thanks.

dennisy 277 days ago | |

Whilst I agree that Cloudflare have a vested interest here, there have been other proposers of this concept such as huggingface.

https://huggingface.co/blog/smolagents

danielser 277 days ago | |

Is this not just GraphQL for MCP/Tools?

In which case your likely wrong, people do want it, and AI will be very good at orchestrating simple patterns.

CF definitely has a vested interest.. The problem for them now that I see is that THEY DIDN"T ACTUALLY LAUNCH IT... but did describe what it is/does in complete detail.

Now there are gonna be dozens of non CF locked clones, just like the one OP linked.

luckydata 277 days ago |

does this approach actually work? is it more reliable than plain mcp calls?

danielser 277 days ago | |

Think of GraphQL, this gives the AI all the structure via Typescript of the MCP / API / Tools, lets it orchestrate its own response.

So once it has the API shape in memory, it could make dozens of tool calls in a single call.

It isn't about token saving, its about time/efficiency of tool usage/response time accumulation.

Instead of 20 separate tool calls one after the other, you get one larger, orchestrated one that only returns exactly what it needed.

lucis 277 days ago |

MCP is the best SDK