ckor

Does it work similarly to GrokBots? They really nail intercommunication.

>implementing MCP auth in an MCP server still isn't very streamlined.

That's why services like https://zapier.com/mcp provide still a ton of value, because it helps non technical folks have the MCP server ready to run.

You just run it with: npx evepad

Needs zero config, and it runs in under 2 seconds

https://www.npmjs.com/package/evepad

I shipped evepad, a local browser based IDE and build harness for eve agents.

One place for the whole loop: create an agent → generate and edit its tools by chat (OpenCode via AI Gateway) → watch local and production runs → add channels and integrations with the eve CLI → deploy to Vercel.

Just type:

It comes with:

· GLM 5.2 for free building until Aug 27th

· Local + Prod agent runs

· eve CLI

· Zero config (uses vercel CLI)

· Visual mapping of your agents

· Fastest agent creation

For the last couple of years, I’ve found myself doing more than just my job. My official title was "Senior Engineer, Frontend," but I was actually driving features end-to-end: writing product specs, shipping full-stack code for any system, orchestrating GTM strategies, diving into research and ML, and jumping on customer calls to close the feedback loop.

Fueled by AI and modern tooling, the lines between disciplines started to completely dissolve. I could design and build a prototype, and push it to production in a single afternoon. It felt like a superpower. But this new reality started creating friction and discomfort; my official role felt too narrow, and the existing corporate structure felt like it was holding me back.

While I was driving a huge business impact my engineering review wasn't perfect because I didn't follow the exact metrics that measure the success of a software engineer, at the same time my grow path was unclear, to grow more as a engineer you need to specialize instead of generalize, and by becoming a manager you cannot build. Something have to change.

Then I looked at the indie hackers and solo founders shipping world-class apps and it all clicked. They weren't just "blurring the lines", they were operating in a world where those lines don't even exist. They were building with a velocity and end-to-end ownership that felt revolutionary.

This isn't a temporary trend; it's a paradigm shift in how we create value. I felt an urgent need to give this new archetype a name and a playbook, and explain how this could fit into a larger org, and not just a solo or small startup.

That's why I wrote "The Builder Manifesto", which I've just open-sourced it: https://github.com/andrewckor/builder-manifesto

A Builder is a full-spectrum operator; a senior IC who combines deep engineering excellence with product vision, design sensibility, and a relentless obsession with the customer. They are the innovation engine, capable of taking an idea from a spark of insight to shipped, impactful reality.

For companies, this is a game-changer. It’s how you attract and unleash the most entrepreneurial talent who would otherwise leave to start their own thing. It's about building a culture of speed and ownership.

I'm sharing this to ignite a conversation. Does this tension between old roles and new capabilities resonate with you?

Is this the future of how high-impact individuals will work?

I'd be thrilled to hear your thoughts and get your feedback on the manifesto.

It's time to build

Amazing news! Can't wait to launch.