Chang Feng 🦦 Building OtterShipper

Paused ottershipper for 20 days to ship lovediary.io for the hackathon by ETHGlobal

My first web3 app. Got the opportunity to understand modern ETH ecosystem and what people are building in web3.

I will share more thoughts when the hackathon wraps.

#buildinpublic #web3 #ETHGlobal #Hackathon

Ended up throwing Multipass VMs at it with 8 cores. Not elegant, not clever caching, just brute force compute. But it works now and I can actually test things locally before pushing.

Sometimes the solution is just "use more CPU" and that's fine.

Day 9: Finally got the local tests working. Spent 2 days going in circles with Docker-in-Docker nonsense. Bind mounts? Nope. Named volumes? Also nope. AI kept suggesting stuff but all the assumptions about how this should work were just WRONG.

#buildinpublic

From the mcp community on Reddit Explore this post and more from the mcp community

Yeah, I asked the question on Reddit and got something useful www.reddit.com/r/mcp/commen...

The outcome: I know exactly which AIs can successfully use my MCP server and which ones can't. If none of them can, I know my tool descriptions or schema need work before any real user hits this wall.

I really want this to exist.

Then it checks: Does each model understand what the user actually wants? Does it understand my MCP's capabilities? Does it prepare the data correctly? Does it call my tools in the right sequence with the right parameters?

Here's what I want:

I give it real user input ("find me all TypeScript files modified this week") and my MCP implementation. The test runs this through multiple AI models—Claude, GPT, Gemini, whatever I want to support.

Testing MCP servers is backwards right now. I can verify my tools connect and return data, but I have no idea if an AI agent will actually understand how to use them.

I need a way to test MCP servers through an AI's eyes—not just mine.

#buildinpublic #mcp #claudecode #vibecoding

Today's tip for AI coding:

Even with a roadmap in .claude/, you still gotta remind Claude about the big picture context when starting new features. Saves you from refactoring later 👍

#BuildInPublic #VibeCoding

GitHub - ottershipper/ottershipper: AI-first deployment platform for Docker applications. Deploy via conversation with Claude Code using the Model Context Protocol (MCP). AI-first deployment platform for Docker applications. Deploy via conversation with Claude Code using the Model Context Protocol (MCP). - ottershipper/ottershipper

Ex-Amazon SDE here. I love building side projects, but managing deployments manually is a headache.

With AI writing more code faster, I needed a better solution. If Claude can build my service, why can't it deploy it too?

⭐ github.com/ottershipper...
Follow for updates →

Day 1 building OtterShipper 🦦

An AI-native deployment tool for vibe coders who want to ship fast and try new ideas.

Deploy by talking to Claude Code (via MCP). No kubectl, no YAML, just conversation.

Open source, built for side project builders.

#buildinpublic #vibecoding