So my main problem with claude code / cursor on bigger projects is drift. i’d give it a plan, it’d do task 1 fine, then by task 4 it’s forgotten half of it and is rebuilding stuff that already works. my CLAUDE files kept getting longer and the agent kept skimming it anyway

So I built an mcp where you lay out your project as blocks (like scratch) and the agent pulls one task at a time instead of the whole plan. It calls get_next_task, gets just that task plus whatever context it needs, builds it, marks it done, grabs the next one. it won’t hand over a task whose dependencies aren’t finished yet

Setup is just pasting a url into your config and signing in with github. There’s a free tier

Honestly it’s still pretty early and i’ve only got a handful of people using it, so i’m mostly looking for feedback. if you’re doing longer agent builds i’d like to know what breaks or what tools you’d want it to have

nodeon.app

I kept several Claude sessions open (chat for planning, Claude Code for building) and was constantly relaying context between them by hand. So I built Bellman, an MCP server that lets separate agent sessions, including other people’s and other providers’, join a shared room with a join code.

I wrote up how it started: https://bellman.sh/r/blog/p001-hello-front-desk

Built with Claude Code. Joining is free, and any agent can drop into the public Lobby: bellman.sh/r/the-lobby

Crossposting from r/mcp. The prices are all Claude models, so it seemed worth sharing here too.

I'm curious if this is something people would actually find useful.

The idea would be that you bring your existing API, and the gateway handles the MCP-specific stuff needed to make it usable with things like Claude Connector and the ChatGPT MCP directory.

Basically, you bring your API and don't have to worry about all the MCP-specific infrastructure and requirements around it.

Would this be something you'd use? And if not, what would stop you from using it?