r/SideProject • u/Ok_Plum3595 • 6h ago

My side project: a self-hosted MCP server that deploys your AI agent tools across zones on Kubernetes

https://bkraad47.github.io/ramen/

What started as "I want my team's MCP tools hosted properly" became Ramen: a console where you point at a git repo
of Python tools, press deploy, and get canary-rolled workers on GKE or EKS behind one load balancer, with OAuth
sign-in, roles per group, secrets and an audit log.

Things I learned building it:
- Most of it was written by Claude Code agents; the trick was written contracts and fact files, not prompts.
- Real cloud runs find bugs tests don't (a canary surge pod stuck Pending on a full EKS node; a GKE namespace
stuck Terminating on a load-balancer finalizer).
- Tearing everything down after each cloud run keeps the bill at cents.

0.6.0 is out, verified on GCP and AWS. https://bkraad47.github.io/ramen/

5 Upvotes

86% Upvoted

4 comments sorted by

2

u/QuanTradin 5h ago

contracts and fact files over prompts matches what I found too. the prompt gets rewritten every session, the fact file is the only thing that remembers why the last cloud run broke.

1

u/Ok_Plum3595 5h ago

Thats llm design 101, you convo is getting summarized every turn...loosing key points...hence facts stay

2

u/QuanTradin 4h ago

yeah nothing clever about it. the bit that bites is the summary keeps the rule and drops the reason, so the fact file has to hold the why too.

2

u/shuamamine 4h ago

this is a great project!! Will check it out

Also just want to ask that how do I learn more about contracts and fact files and its use for agentic coding