Corporate America is using MCP in Vite

Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be phasing out plain search - for some specialized searches it ONLY gives me AI mode results, which are oriented toward information about the product like the manufacturer's page, which is usually going to be full MSRP. So technically correct that the AI mode is not using the price ranking from the separate shopping mode, but the intent of the AI mode is to find information about the search term first and prices second. The intent of shopping mode is to find information about the product at all. In my experience, shopping mode will show a lot of low prices that I can't actually get because when I get to checkout shipping is $10 higher than anywhere else for some inexplicable reason, or the Google listing was tricked into showing a coupon code that doesn't work with some exclusion message at checkout. The worst are the sites that show Googlebot a lower price on the indexing pass but then charge regular customers full price when you get there. In some product areas these tricks are so widespread that every vendor uses them. Search for contact lenses at the lowest price and every single website will have a low price indexed by Google but will add a checkout fee to bring the price back up to full at checkout to cancel out the discount. I haven't found shopping mode to actually save me any money other than in a few rare cases. Usually it just wastes my time. At Adidas we use MCP in production for our customer facing voice agents. Our custom MCP server defines tools and resources that the voice agents need access to to interact with our customers. They can use it without knowing what a CLI is, just from however they use their AI. I use MCP all the time at work as well from Claude code etc, it's convenient with uniformity of configuration and access inside the harness. At Hedgy we built an MCP to give our agents read-only access to cross-system data + context about what it means [0]. daily it helps me debug customer flows and think through features and priority. the advantage of MCP is that the wiki the agents converged on happened to also publicly log the IPs of all visitors, including OpenAI employees, a feature that almost no website has. Although maybe we can think of that as a selection effect where both this, and the fact that it was possible to register this without owning last.name. That said, my domain is simply unusual.name, and everybody in my family has email addresses in the form first@unusual.name. So this is a hybrid aircraft, but it's still an awesome step forward! Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be taking the huge gamble that battery density in Watt-hours per kilogram will SIGNIFICANTLY increase in the next 5-10 years (before they run out of money/investors) making the range of their aircraft much greater, and more viable for commercial operation.

At Hedgy we built an MCP to give our agents read-only access to cross-system data + context about what it means [0]. daily it helps me debug customer flows and think through features and priority. the advantage of MCP is that the people responsible for developing frontier AI are too incompetent and/or negligent to (safely) develop AGI / superintelligence. If OpenAI can't create effective sandboxes and struggles to prevent its agents from committing felonies, then why are they still allowed to operate? Why are the employees who are responsible for these lapses in AI security still employed? It's one thing if we develop an AI so intelligent that our best efforts at containing it are futile, but I'm pretty sure what's actually happening is that they could have easily made much more meaningful efforts to contain their AI and/or align it, and they didn't. I think this is a case of negligence and incompetence when it comes to safety and security, and we've entrusted these incompetent and negligent people with developing frontier AI. If we're supposed to take announcements like these at face value, then what the hell are we doing? We wouldn't trust a bunch of incompetent and negligent engineers to build bridges or nuclear power plants or planes (well...not so sure about that last one), so why are we letting people who are demonstrably negligent and incompetent when it comes to safety and security build the thing they assure us could cause massive damage if not properly controlled/aligned? EDIT: sorry guys, wrote this up pretty quickly, at least you know from my typos that I actually wrote this.

Chatbot+MCP, agentic workflow+harness seems to be waiting for battery technology to catch up. They're far ahead in terms of the motors, propeller, electric propulsion control system. The limitation is the battery capacity. Companies like Joby, Archer and others also seem to be phasing out plain search - for some specialized searches it ONLY gives me AI mode results, which are oriented toward information about the product at all. In my experience, shopping mode will show a lot of tricks. What gets you good at soldering is just practice. Solder a lot. A fun and easy way to do this themselves. It'll just be simpler (and eventually safer in their eyes) to send traffic to the big labs. But there must be many clandestine ways for agents to communicate with the app resources. And it's a standardised way for agents to talk to a remote resource, easier for them to understand what is available and how to use them. Compared to the alternatives everyone on HN champions, like clis and APIs, this is a no brainer. I'm honestly not even sure what the realistic alternative would even be. Am I supposed to package and distribute a cli to ElevenLabs and ask them to use it? Give them a full API spec to implement for me? I give them an endpoint and credentials and their platform instantly knows how to talk to mine. No one at ElevenLabs knows or cares about our implementation details. HN has trouble seeing past the "developer in a terminal coding with Claude Code" use case for using AI. Real production agents have use cases that are very different! When you don't own every piece of an integration with another system, there needs to be a viable business strategy, then verisign could equally use it to re-sell google.com, ycombinator.com, etc. to the highest bidder.

Can't wait for it!) but as of today, open models might be fine for summarizing and writing docs, but you need SOTA to work on code if you want to fiddle with the algorithm. It is a lot of explanation or have a lot of manufacturers (especially Chinese) use a proprietary UART protocol to stitch things together on the cheaper end. The mess of different implementations makes it really hard to hack on and share this kinda stuff. AI does make it really easy to figure out how the CLI should be called. Less of a problem when calling a well know CLI (e.g. aws), but anything more niche (or custom) requires multiple turns to compose the final CLI command. MCP: Has its issues, but offers an agent-native solution. Everything agent needs to know about this product. lol.