Sloppypasta culprits, unpacking MCP’s spotlight, and Anthropic wants your agents to work the graveyard shift

**Ben Lloyd-Pearson** (0:05)
Andrew, are you taking advantage of Claude's recommendation to start working nights and weekends now?

**Andrew Ziegler** (0:11)
What do you mean, Ben?

**Ben Lloyd-Pearson** (0:13)
You haven't gotten the notification yet? And when you sign in, it's like, hey, we'll give you more tokens if you work late at night, because it's cheaper for us.

**Andrew Ziegler** (0:22)
Oh, yes, if you distribute your workloads, the time is when not everyone is rushing to slam GitHub with their pull requests. Definitely getting people off of the morning shake up on Mondays, for sure. I don't know about you, but like every Monday morning, it's just like, oh, is this going to fall over today? It's like every week now, I'm like betting on my repositories.

**Ben Lloyd-Pearson** (0:42)
Monday mornings, I feel like almost every AI tool is barely surviving, just scraping by, suffering through the first few hours of the work week before things sort of flatline.

**Andrew Ziegler** (0:54)
It makes me think of a very apocalyptic future where there's rolling token blackouts, where you're in a token blackout because the consumptions are too high in your area. And imagine what that would turn off, because it has electricity when it shuts off, you can't turn on a bunch of things. Maybe when the tokens stop flowing in your area, a lot of things don't work anymore either.

**Ben Lloyd-Pearson** (1:15)
Well, you know, people get batteries for their house when they have solar panels to collect energy and then use that battery energy when electricity prices are high. I wonder if there's a way for me to just collect tokens, so that I can leverage my bank of tokens when token costs are high.

**Andrew Ziegler** (1:34)
Okay, well, somebody get Ben a solar farm and let him get cooking, because that sounds fascinating. But it would be just to get more tokens in general. So I love Claude's idea of distributing folks around. I just wonder who will do it. Obviously, if you can orchestrate your agents and they're running for you all the time anyways, what's the matter? It's like they're probably always running slash you could just have them run later.

**Ben Lloyd-Pearson** (1:56)
So what you're saying is all the more pressure to just have our agents constantly working for us when we're not working, I guess. Yeah. Well, and on that note, welcome to the Friday Deploy. I'm your host, Ben Lloyd-Pearson.

**Andrew Ziegler** (2:09)
And I'm your host, Andrew Ziegler.

**Ben Lloyd-Pearson** (2:11)
And this week we've got MCP, Is It Dead? How to Anchor Context to Prevent Model Compaction, The Resurgence of the Small Web, and An AI-Edequate Guide. So let's just start at the top with MCP. Andrew, is MCP dead?

**Andrew Ziegler** (2:27)
Okay, well this spicy article is about how MCP is gone and no, MCP is back and MCP is somewhere in the middle. Yes, I think AI's darling child MCP has certainly ran its course of popularity. I love how this article calls out the fault of AI hype influencers for making MCP more popular than it needed to be. I don't know if this was directed at me, I'm just kidding. But if you have been listening to Dev Interrupted, especially around this time, about a year ago, you'll know we were talking about MCP on this show a lot.

**Ben Lloyd-Pearson** (2:59)
The timeline in this article actually almost perfectly lines up when we were hyping MCP. So I feel like he probably is calling us out directly on this one. Yes.

**Andrew Ziegler** (3:08)
Clearly a Dev Interrupted reader, clearly disgruntled by our effusive coverage of MCP. You know what? I don't blame them because reflecting on it, it was a different problem, a different solution for a different time. Because around this time a year ago, let's not forget, the models were a lot dumber.
Their ability to use tools was not as great as it was today. And MCP was a fundamental day and night change in the ability to get consistent tool usage from LLMs. It really paved the way for more token optimized and simpler solutions. We all kind of ended up going back to CLIs in some form or another, instead of carrying around massive MCP servers. And the benefits of this are numerous and lots of folks talk about them. But what this article calls out is, why was MCP in the spotlight in the first place? I think it's a great reminder that we're in a growing pain. We're going to be embracing and using technology that maybe it's not going to stick around forever. So you should always be working in a way that expects your tools to be temporary and moving with you, not standing still.