Eyal Ben Ezra

323 posts

Eyal Ben Ezra banner
Eyal Ben Ezra

Eyal Ben Ezra

@eyalbe

Family man, builder, tinkerer, wannabe french chef. Now: 🤖 Building https://t.co/ZNzsC5I9Jn Then: 🐻 https://t.co/pawxtsiUQF (sold to https://t.co/D2cDMYiT9Y)

Tel Aviv Katılım Şubat 2011
598 Takip Edilen262 Takipçiler
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@urieli17 שירות ברמה הכי גבוהה שפגשתי באמירים
עברית
0
0
1
311
Uri Eliabayev
Uri Eliabayev@urieli17·
אני עושה את המחקר שלי על איפה לקנות מחשב מאק ואני רואה שזה עולם ומלאו. יש את idigital ו-iStore שהייתי בטוח שזה אותו הדבר, יש את KSP שהם זולים כמו תמיד וגם לא הבנתי מי זה אמירים ולמה כולם מתים עליו..
עברית
100
0
133
36.9K
Eyal Ben Ezra retweetledi
Randy Olson
Randy Olson@randal_olson·
Summary of the MCP vs. CLI debate on X this week.
Randy Olson tweet media
English
39
70
775
44.3K
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@anvisha 100%. engineers obsess over the last mile. People just need things that work. MCPs aren't perfect but they just work. Plug and play. That was the concept. We're seeing it firsthand with both technical and non-technical teams - incredible results
English
0
0
1
33
Eyal Ben Ezra retweetledi
Rhys
Rhys@RhysSullivan·
MCP sucking is a harness problem, not an MCP problem MCP unlocks behavior that is fundamentally impossible to get via CLI or APIs Bad auth, too much context usage, all get solved with an execution layer - your agent writes code to progressively discover and call tools
Garry Tan@garrytan

MCP sucks honestly It eats too much context window and you have to toggle it on and off and the auth sucks I got sick of Claude in Chrome via MCP and vibe coded a CLI wrapper for Playwright tonight in 30 minutes only for my team to tell me Vercel already did it lmao But it worked 100x better and was like 100LOC as a CLI

English
165
92
1.4K
373.4K
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@ItakGol it's incredible how @AnthropicAI keeps pumping out visuals that grab everyone's attention. Something new every week. I had 2 sales calls yesterday where this spider graph came up. How much $$$ do I need to pay to get some of their marketing talent 🤣?
English
0
0
1
39
Itamar Golan 🤓
Itamar Golan 🤓@ItakGol·
Funny how the “safe” jobs changed. Computer science was the dream. Now construction might be.
Itamar Golan 🤓 tweet media
English
3
0
10
855
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@amsalemadir 100% seeing this too. Now imagine every dev on your team gets auto-synced skills, plugins, and tools inside Claude Code - no setup, no config drift. That's what we're building. Happy to show you if you're curious.
English
2
0
2
53
Adir Amsalem
Adir Amsalem@amsalemadir·
In the past two weeks, every person on my team shipped solo what we likely couldn’t ship together just a few months ago. Not hype or bragging - just a genuine observation. If you haven't changed your AI-coding workflow recently, you're shipping at least 2x less than you could.
English
4
0
7
220
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
Valid take — context bloat is a real problem. But I think this is less "MCP is dead" and more "the tooling layer is growing up." The bloat thing though — that's an implementation problem, not a protocol problem. A well-designed MCP server is 5-8 tools, not 50. If you're loading 50 tool definitions at once, that's not MCP's fault, you built it wrong :) The ecosystem is already moving toward dynamic tool loading — surface what's relevant to the task, not everything at once. It's something we're actively building at webrix.ai. The 50-tool problem is a v1 growing pain, not a death sentence. Where I really disagree is the CLI-for-everything take. CLI + exec is great when a CLI already exists. But what about SaaS apps that want to expose a specific agent experience? When Figma builds their MCP server, they're not wrapping 200 endpoints — they're designing an intentional agent interface: "get frame by name, export as PNG, list comments." That curation — the service provider deciding how an agent should interact with them — is what makes the agent actually useful. "Here's a shell, figure it out" doesn't get you there. And the deeper reason MCP sticks? Standardization. Everyone's tired of the USB-C analogy but here we go 😛 — before USB-C every phone had its own charger. Before MCP every service had its own integration pattern, auth flow, schema format. One standard way for agents to discover and call services. Will MCP look the same in 2 years? Probably not. But we're not going back to proprietary connectors.
English
0
0
0
96
Chrys Bader
Chrys Bader@chrysb·
unpopular (maybe?) opinion: MCP is dead in the water @openclaw has shown me that api & cli will win. every MCP server you connect loads its tool definitions into your context window. name, description, parameter schema, all of it. connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. context bloat will never be a good thing - performance-wise or economically. i assume this is why @steipete left it out of @openclaw. the "exec" tool paired with on-demand skills is all you need. it can run any command invented since the beginning of computers. a resurgence of glory for ancient, but powerful tools like curl, sed, awk, grep. command line tools once mastered by the greats, but long forgotten and buried underneath abstractions developed for us lesser mortals. now available to us all, piloted by the smartest models on earth. every founder gets their own mass army of greybeards. the inertia required for MCP adoption, imo, is too great to overcome the momentum @openclaw has breathed into api + cli + skills. the common defenses people bring up: • "MCP gives you typed schemas and validation" — so does a well-documented CLI • "MCP gives you explicit permissions" — so does a sandbox with an allowlist • "MCP is a standard" — a standard that scales poorly is still a standard that scales poorly lastly, i've heard many MCP servers are just wrapping existing APIs - that kind of redundancy and unnecessary indirection should be a red flag. so, let's drop it and redirect our efforts into cli tools & apis with accompanying skills.
Chrys Bader tweet media
English
285
89
1.6K
331.3K
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@AnthropicAI Claude runs my whole biz (@webrix_ai) - love it. Using Webrix to route Claude to all my tools & skills. Voice got amazing but please stop kicking me to text for tool calls & structured outputs. @ChatGPTapp keeps you in voice for everything. Copy that! 🙏
English
0
0
3
53
Elie Steinbock — oss/acc
LFG. We're 1st on Product Hunt!!!! Thank you to everyone that helped get us here! Now lots of hard work ahead to stay for the rest of the day!
Elie Steinbock — oss/acc tweet media
English
9
1
22
967
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
Masters of the Air on Apple TV. The bravery of these men is beyond comprehension. Beyond being glued to the screen for the entire series, it left me with a deep sense of humility and inspiration - a true understanding of what humans are capable of when everything is on the line. Makes you rethink what "hard" actually means. tv.apple.com/us/show/master…
English
0
0
0
184
Harley Finkelstein
Harley Finkelstein@harleyf·
Best thing you read, heard or watched this year? I’m looking for ones that made you stop and rethink how you’re approaching your business or your life.
English
72
10
175
39.4K
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@tdinh_me I built this for Shopify stores based on @browserbase. Was hard af to monazite based on small shops. Eventually gave up 🤓. Looks like you got great validation in this post.
English
0
0
0
25
Tony Dinh
Tony Dinh@tdinh_me·
Examples: “Alert: discount code stopped working in your checkout flow” “Alert: App crash when clicking on sidebar expand menu button in the admin dashboard.” “Alert: New UI in the onboarding screen is missing style for dark mode”
English
17
0
40
18K
Tony Dinh
Tony Dinh@tdinh_me·
Anyone building this?
Tony Dinh tweet media
English
73
1
318
86.2K
Elie Steinbock — oss/acc
Sponsoring the wedding paid for itself by getting a 90 DR do-follow backlink from people com.
Elie Steinbock — oss/acc tweet media
English
11
0
66
8.6K
Eyal Ben Ezra
Eyal Ben Ezra@eyalbe·
@hipreetam93 1st rule of business: never build it on facebook. 2nd rule of business: never build it on facebook. ... Hope tobi will come through
English
1
0
1
357
Preetam Nath
Preetam Nath@hipreetam93·
Requesting the folks at Shopify to please step in and help figure things out. We too have received the trademark notice. And the deadline to fix it is 6 days away. Otherwise, our app will be delisted from the Shopify app store. Just like that. After 5 years of being on the app store and complying with every request or warning or mildly threatening email about fixing something "or else". Quite a violent way to communicate, I feel. Like this is the best a multi billion corporation can do? It does not make any sense @harleyf @ShopifyDevs since the app store is full of apps with "Facebook" and "Instagram" in their app titles and descriptions. Meta is forcing "WhatsApp" named apps to remove the word because they have launched their own WhatsApp app for Shopify. When a big guy flexes, we small people don't have any way out. Except if another big guy ( looking at you @Shopify @tobi ) is there to stand-up and meditate and come up with a more peaceful and decent way to go about it.
sivaram💻@sivaram636

We have been building WhatsApp integration for Shopify for the last 5 years due to a Trademark notice from Meta or its representative, Shopify requires us not use “WhatsApp” even as a description of our app.The whole Shopify App is built for WhatsApp. @tobi @ShopifyDevs @harleyf

English
16
37
79
35.1K
Elie Steinbock — oss/acc
You can upgrade to Next.js 16 using their dedicated MCP 🤯 Install the MCP and type "upgrade to nextjs 16" and you're good
Elie Steinbock — oss/acc tweet media
English
5
2
23
1.9K