← Back
Theo August 8, 2026 18m

Did Anthropic finally fix MCP?

Read full transcript 14 segments
  1. Time for a 2025 throwback because we Time for a 2025 throwback because we need to talk about MCP. It's a standard need to talk about MCP. It's a standard need to talk about MCP. It's a standard that was really popular at the time. It that was really popular at the time. It that was really popular at the time. It felt like everybody was trying to felt like everybody was trying to felt like everybody was trying to integrate it in their stuff, but it integrate it in their stuff, but it integrate it in their stuff, but it wasn't something I was particularly fond wasn't something I was particularly fond wasn't something I was particularly fond of. In fact, I was notoriously against of. In fact, I was notoriously against of. In fact, I was notoriously against MCP. I felt like it was massively MCP. I felt like it was massively MCP. I felt like it was massively overrated and really bloated spec that overrated and really bloated spec that overrated and really bloated spec that caused as many problems as it solved. caused as many problems as it solved. caused as many problems as it solved. And I just didn't find myself using it a And I just didn't find myself using it a And I just didn't find myself using it a whole lot in my day-to-day workflows. In whole lot in my day-to-day workflows. In whole lot in my day-to-day workflows. In fact, I've actually found it more fact, I've actually found it more fact, I've actually found it more annoying recently because tools like annoying recently because tools like annoying recently because tools like Codeex use it properly. And by using it Codeex use it properly. And by using it Codeex use it properly. And by using it properly, they end up wasting a bunch of properly, they end up wasting a bunch of properly, they end up wasting a bunch of resources because every single MCP resources because every single MCP resources because every single MCP server needs to be a dedicated server server needs to be a dedicated server server needs to be a dedicated server with a dedicated connection to the with a dedicated connection to the with a dedicated connection to the client while it's existing. Even if the client while it's existing. Even if the client while it's existing. Even if the client never ends up calling it, it has client never ends up calling it, it has client never ends up calling it, it has to be bound to a real connection on a to be bound to a real connection on a to be bound to a real connection on a real server. It got so bad that a lot of real server. It got so bad that a lot of real server. It got so bad that a lot of the MCP stuff that we use was just the MCP stuff that we use was just the MCP stuff that we use was just hosted locally because the amount of hosted locally because the amount of hosted locally because the amount of infrastructure it would take to host it infrastructure it would take to host it infrastructure it would take to host it in the cloud just wasn't worth it when in the cloud just wasn't worth it when in the cloud just wasn't worth it when it wasn't being used 99% of the time. it wasn't being used 99% of the time. it wasn't being used 99% of the time. But there's a new MCP spec now. They But there's a new MCP spec now. They But there's a new MCP spec now. They should call this something else like should call this something else like should call this something else like MCP2 or just a new name entirely because MCP2 or just a new name entirely because MCP2 or just a new name entirely because the MCP branding's been destroyed. But the MCP branding's been destroyed. But the MCP branding's been destroyed. But this improvement is massive. Simon this improvement is massive. Simon this improvement is massive. Simon Wilson just posted an article saying Wilson just posted an article saying Wilson just posted an article saying that stateless MCP has recaptured his that stateless MCP has recaptured his that stateless MCP has recaptured his interest. This is kind of the spoiler.

  2. interest. This is kind of the spoiler. interest. This is kind of the spoiler. By the way, MCP can now be stateless. By the way, MCP can now be stateless. By the way, MCP can now be stateless. This is a very, very exciting change This is a very, very exciting change This is a very, very exciting change that makes MCP go from a worse version that makes MCP go from a worse version that makes MCP go from a worse version of a CLI to a potentially actually of a CLI to a potentially actually of a CLI to a potentially actually useful integration to have in our tools. useful integration to have in our tools. useful integration to have in our tools. I'm really excited about what this I'm really excited about what this I'm really excited about what this means, but there's also some concerns means, but there's also some concerns means, but there's also some concerns that I have with the change. And I that I have with the change. And I that I have with the change. And I cannot wait to talk about all of that cannot wait to talk about all of that cannot wait to talk about all of that right after a quick break for today's right after a quick break for today's right after a quick break for today's sponsor. Agents have gotten way, way sponsor. Agents have gotten way, way sponsor. Agents have gotten way, way better at writing code, but they've also better at writing code, but they've also better at writing code, but they've also gotten better at using computers, too. I gotten better at using computers, too. I gotten better at using computers, too. I am blown away when I watch models like am blown away when I watch models like am blown away when I watch models like 56 navigate the web. But there's a 56 navigate the web. But there's a 56 navigate the web. But there's a problem. They need a browser. problem. They need a browser. problem. They need a browser. Thankfully, somebody made the best Thankfully, somebody made the best Thankfully, somebody made the best possible browser for your agents, and possible browser for your agents, and possible browser for your agents, and it's today's sponsor, Browserbase. These it's today's sponsor, Browserbase. These it's today's sponsor, Browserbase. These guys understand browsers and agents guys understand browsers and agents guys understand browsers and agents incredibly well. Just as a quick demo, I incredibly well. Just as a quick demo, I incredibly well. Just as a quick demo, I set up Cloud Code with the Browserbase set up Cloud Code with the Browserbase set up Cloud Code with the Browserbase MCP, and it's so so cool. I put together MCP, and it's so so cool. I put together MCP, and it's so so cool. I put together a lake bed to-do list so you can see the a lake bed to-do list so you can see the a lake bed to-do list so you can see the live updates as they happen because the live updates as they happen because the live updates as they happen because the platform is fully live syncing. I didn't platform is fully live syncing. I didn't platform is fully live syncing. I didn't define an API for my agents to use to define an API for my agents to use to define an API for my agents to use to modify things on this page. All there is modify things on this page. All there is modify things on this page. All there is is a website, which turns out 85% of the is a website, which turns out 85% of the is a website, which turns out 85% of the web doesn't have APIs. It's only web web doesn't have APIs. It's only web web doesn't have APIs. It's only web sites, which means agents need a web sites, which means agents need a web sites, which means agents need a web browser in order to access it. Oh, look browser in order to access it. Oh, look browser in order to access it. Oh, look at that. A live to-do just appeared on at that. A live to-do just appeared on at that. A live to-do just appeared on the fly from Claude, doing it through the fly from Claude, doing it through the fly from Claude, doing it through the browser. Of course, it's making fun the browser. Of course, it's making fun the browser. Of course, it's making fun of me for still demoing to-do apps.

  3. of me for still demoing to-do apps. of me for still demoing to-do apps. What's even cooler is if we go to the What's even cooler is if we go to the What's even cooler is if we go to the dashboard, we can live monitor how the dashboard, we can live monitor how the dashboard, we can live monitor how the agent is using the browser. This is the agent is using the browser. This is the agent is using the browser. This is the actual instance it's using. I could even actual instance it's using. I could even actual instance it's using. I could even hop in here and control it myself if I hop in here and control it myself if I hop in here and control it myself if I want to, clicking on things and saying, want to, clicking on things and saying, want to, clicking on things and saying, "Hey, sup." Because remember, this is a "Hey, sup." Because remember, this is a "Hey, sup." Because remember, this is a real browser. They are hosting in the real browser. They are hosting in the real browser. They are hosting in the cloud. If you don't have use cases for a cloud. If you don't have use cases for a cloud. If you don't have use cases for a tool like this, you're not thinking tool like this, you're not thinking tool like this, you're not thinking creatively enough. If you are, check creatively enough. If you are, check creatively enough. If you are, check them out now at sidyv.link/browserbase. them out now at sidyv.link/browserbase. them out now at sidyv.link/browserbase. Good to have you back. It's time to talk Good to have you back. It's time to talk Good to have you back. It's time to talk about the new MCP standard. I wish they about the new MCP standard. I wish they about the new MCP standard. I wish they gave it a good name, but instead it's gave it a good name, but instead it's gave it a good name, but instead it's MCP 2026728. MCP 2026728. MCP 2026728. Didn't we learn this lesson with model Didn't we learn this lesson with model Didn't we learn this lesson with model names when Anthropic had all the names when Anthropic had all the names when Anthropic had all the different versions of Sonnet 3.5 that different versions of Sonnet 3.5 that different versions of Sonnet 3.5 that were just different dates? Like, they were just different dates? Like, they were just different dates? Like, they know better than to do this. Yet, here know better than to do this. Yet, here know better than to do this. Yet, here we are doing this. I have other we are doing this. I have other we are doing this. I have other complaints about this coming up, don't complaints about this coming up, don't complaints about this coming up, don't worry. The fifth spec release of the worry. The fifth spec release of the worry. The fifth spec release of the model context protocol MCP 202060728 is model context protocol MCP 202060728 is model context protocol MCP 202060728 is live today. The latest spec moves MCP to live today. The latest spec moves MCP to live today. The latest spec moves MCP to a stateless core while hardening a stateless core while hardening a stateless core while hardening authorization and graduating official authorization and graduating official authorization and graduating official extensions. Support is being rolled out extensions. Support is being rolled out extensions. Support is being rolled out across clawed products. This is the big across clawed products. This is the big across clawed products. This is the big part here that MCP has moved to a part here that MCP has moved to a part here that MCP has moved to a stateless core. Very very very exciting.

  4. stateless core. Very very very exciting. stateless core. Very very very exciting. What do we mean by this stateless core? What do we mean by this stateless core? What do we mean by this stateless core? Well, according to Enthropic, MCP has Well, according to Enthropic, MCP has Well, according to Enthropic, MCP has moved from a birectional stateful moved from a birectional stateful moved from a birectional stateful protocol to a request response model. protocol to a request response model. protocol to a request response model. Huh, almost like the exact thing I've Huh, almost like the exact thing I've Huh, almost like the exact thing I've been saying it should do for a long time been saying it should do for a long time been saying it should do for a long time now. Servers can now deploy on now. Servers can now deploy on now. Servers can now deploy on serverless and edge infrastructure. This serverless and edge infrastructure. This serverless and edge infrastructure. This simplifies the experience of building simplifies the experience of building simplifies the experience of building MCP servers for Claude and scaling their MCP servers for Claude and scaling their MCP servers for Claude and scaling their usage as they grow in adoption. Yep, usage as they grow in adoption. Yep, usage as they grow in adoption. Yep, this is the key piece. In as I mentioned this is the key piece. In as I mentioned this is the key piece. In as I mentioned before, in order to set up MCP, you had before, in order to set up MCP, you had before, in order to set up MCP, you had to have a dedicated connection between to have a dedicated connection between to have a dedicated connection between the thing running your agent and the the thing running your agent and the the thing running your agent and the server providing the service. So if you server providing the service. So if you server providing the service. So if you were building an MCP for, I don't know, were building an MCP for, I don't know, were building an MCP for, I don't know, let's say that you had a database let's say that you had a database let's say that you had a database platform and you wanted an MCP that platform and you wanted an MCP that platform and you wanted an MCP that allowed for your customers agents to allowed for your customers agents to allowed for your customers agents to look data up or find things in the DB or look data up or find things in the DB or look data up or find things in the DB or audit, make changes, stuff like that. In audit, make changes, stuff like that. In audit, make changes, stuff like that. In an era where we didn't have a good way an era where we didn't have a good way an era where we didn't have a good way to share all of that context, MCP was to share all of that context, MCP was to share all of that context, MCP was really powerful because it allowed you really powerful because it allowed you really powerful because it allowed you to expose an endpoint on your service, to expose an endpoint on your service, to expose an endpoint on your service, not just enabling it to access that not just enabling it to access that not just enabling it to access that data, but also giving it effectively data, but also giving it effectively data, but also giving it effectively instructions on how it can use those instructions on how it can use those instructions on how it can use those endpoints and what it can do with them, endpoints and what it can do with them, endpoints and what it can do with them, providing examples and whatnot, too. The providing examples and whatnot, too. The providing examples and whatnot, too. The problem with MCP is that that problem with MCP is that that problem with MCP is that that relationship between the client and the relationship between the client and the relationship between the client and the server required them to be connected server required them to be connected server required them to be connected throughout the entire process, even if throughout the entire process, even if throughout the entire process, even if you weren't using it. So if you set up you weren't using it. So if you set up you weren't using it. So if you set up five MCPS in your cloud code and then five MCPS in your cloud code and then five MCPS in your cloud code and then went and did a task that used zero of went and did a task that used zero of went and did a task that used zero of them, that cloud code run still has five them, that cloud code run still has five them, that cloud code run still has five dedicated stateful connections bound dedicated stateful connections bound dedicated stateful connections bound between it and external services. I'm between it and external services. I'm between it and external services. I'm going to show you one of the silliest going to show you one of the silliest going to show you one of the silliest examples of how this affects you in examples of how this affects you in examples of how this affects you in day-to-day. I'm going to spin up codeex.

  5. day-to-day. I'm going to spin up codeex. day-to-day. I'm going to spin up codeex. It's trying to failing to initialize the It's trying to failing to initialize the It's trying to failing to initialize the Xcode build MCP. So I got an error Xcode build MCP. So I got an error Xcode build MCP. So I got an error there. But watch what happens when I say there. But watch what happens when I say there. But watch what happens when I say sup. I'm hitting enter now. sup. I'm hitting enter now. sup. I'm hitting enter now. Oh, did they suppress it finally? They Oh, did they suppress it finally? They Oh, did they suppress it finally? They suppressed it finally. Cool. I gave them suppressed it finally. Cool. I gave them suppressed it finally. Cool. I gave them a shitload of feedback about this. There a shitload of feedback about this. There a shitload of feedback about this. There was a problem where every time you spun was a problem where every time you spun was a problem where every time you spun up a thread in codeex, it would block up a thread in codeex, it would block up a thread in codeex, it would block your first message until it finished your first message until it finished your first message until it finished initializing the MCP servers for initializing the MCP servers for initializing the MCP servers for computer use and whatnot. They recently computer use and whatnot. They recently computer use and whatnot. They recently changed it so that those wouldn't happen changed it so that those wouldn't happen changed it so that those wouldn't happen until after you send, which helped a until after you send, which helped a until after you send, which helped a bit, but they have changed it even bit, but they have changed it even bit, but they have changed it even further where you don't see it as much further where you don't see it as much further where you don't see it as much now, which is good. But previously it now, which is good. But previously it now, which is good. But previously it was obnoxious because every thread and was obnoxious because every thread and was obnoxious because every thread and more importantly every sub aent would more importantly every sub aent would more importantly every sub aent would have to spin up five or more stateful have to spin up five or more stateful have to spin up five or more stateful MCP connections which means that on your MCP connections which means that on your MCP connections which means that on your computer if you have one agent run computer if you have one agent run computer if you have one agent run you're doing in codecs and it spins up you're doing in codecs and it spins up you're doing in codecs and it spins up five sub aents that is now 30 stateful five sub aents that is now 30 stateful five sub aents that is now 30 stateful connections that are bound on your connections that are bound on your connections that are bound on your machine for one prompt and that is for machine for one prompt and that is for machine for one prompt and that is for the server and the client because it has the server and the client because it has the server and the client because it has to spin up the server side for that to spin up the server side for that to spin up the server side for that locally for all the computer use servers locally for all the computer use servers locally for all the computer use servers in case any one of those sub aents wants in case any one of those sub aents wants in case any one of those sub aents wants to do computer use and now you have 30 to do computer use and now you have 30 to do computer use and now you have 30 stateful processes on the server side in stateful processes on the server side in stateful processes on the server side in codecs and then they're bound 30 times codecs and then they're bound 30 times codecs and then they're bound 30 times on the client. It is so much overhead on the client. It is so much overhead on the client. It is so much overhead and if you have seen CIS policyd and if you have seen CIS policyd and if you have seen CIS policyd eviscerating your CPU this is why for us eviscerating your CPU this is why for us eviscerating your CPU this is why for us Mac users because sis policyd is how Mac Mac users because sis policyd is how Mac Mac users because sis policyd is how Mac OS monitors processes to make sure OS monitors processes to make sure OS monitors processes to make sure they're not doing anything sketchy and they're not doing anything sketchy and they're not doing anything sketchy and spinning up 30 servers on your machine spinning up 30 servers on your machine spinning up 30 servers on your machine looks a little sketchy but now that it's looks a little sketchy but now that it's looks a little sketchy but now that it's stateless none of that matters. Each

  6. stateless none of that matters. Each stateless none of that matters. Each agent can just hit a random endpoint and agent can just hit a random endpoint and agent can just hit a random endpoint and get back some JSON and then decide when get back some JSON and then decide when get back some JSON and then decide when it wants to do things from there instead it wants to do things from there instead it wants to do things from there instead of it being a bound connection. It is of it being a bound connection. It is of it being a bound connection. It is just an endpoint that is hit which is to just an endpoint that is hit which is to just an endpoint that is hit which is to be frank the way it always should have be frank the way it always should have be frank the way it always should have worked because all MCP should be doing worked because all MCP should be doing worked because all MCP should be doing is informing the agent of what its is informing the agent of what its is informing the agent of what its capabilities are and then giving the capabilities are and then giving the capabilities are and then giving the agent everything it needs in order to agent everything it needs in order to agent everything it needs in order to call and do things. This also means the call and do things. This also means the call and do things. This also means the infrastructure you host it on and the infrastructure you host it on and the infrastructure you host it on and the ways you provide it on your computer can ways you provide it on your computer can ways you provide it on your computer can be entirely different too. You can have be entirely different too. You can have be entirely different too. You can have a simple local HTTP API or one in the a simple local HTTP API or one in the a simple local HTTP API or one in the cloud that fetches data and has like one cloud that fetches data and has like one cloud that fetches data and has like one little key in it to distinguish between little key in it to distinguish between little key in it to distinguish between things instead of keeping a bound things instead of keeping a bound things instead of keeping a bound connection the whole time. There are connection the whole time. There are connection the whole time. There are other things they added here like they other things they added here like they other things they added here like they standardize extensions through apps and standardize extensions through apps and standardize extensions through apps and tasks. They hardened off which is cool tasks. They hardened off which is cool tasks. They hardened off which is cool as well. And a bunch of companies said as well. And a bunch of companies said as well. And a bunch of companies said awesome things about it. Oh, cool. The awesome things about it. Oh, cool. The awesome things about it. Oh, cool. The official MCP site has a nice visualizer official MCP site has a nice visualizer official MCP site has a nice visualizer for this. Like setting up your MCP for this. Like setting up your MCP for this. Like setting up your MCP before required a intelligent load before required a intelligent load before required a intelligent load balancer to make sure the client balancer to make sure the client balancer to make sure the client connected to the same place always and connected to the same place always and connected to the same place always and that things went back to that one and if that things went back to that one and if that things went back to that one and if somebody else came in, they got routed somebody else came in, they got routed somebody else came in, they got routed to the correct instance as well. In a to the correct instance as well. In a to the correct instance as well. In a world where things are stateless, world where things are stateless, world where things are stateless, everything is significantly simpler. So everything is significantly simpler. So everything is significantly simpler. So you don't have to maintain the you don't have to maintain the you don't have to maintain the connection through the load balancer the connection through the load balancer the connection through the load balancer the whole time. It was one of the most whole time. It was one of the most whole time. It was one of the most highly requested features from highly requested features from highly requested features from developers who were eager to get better developers who were eager to get better developers who were eager to get better reliability and scalability for their reliability and scalability for their reliability and scalability for their MCP servers. [ __ ] yes. Yeah, it was the MCP servers. [ __ ] yes. Yeah, it was the MCP servers. [ __ ] yes. Yeah, it was the lazier on demand stuff. If there is lazier on demand stuff. If there is lazier on demand stuff. If there is something for that, they finally killed something for that, they finally killed something for that, they finally killed the handshake [ __ ] from that awful the handshake [ __ ] from that awful the handshake [ __ ] from that awful old web spec that they shouldn't have old web spec that they shouldn't have old web spec that they shouldn't have implemented. That's a nice change. I

  7. implemented. That's a nice change. I implemented. That's a nice change. I want to share what Simon Willis had to want to share what Simon Willis had to want to share what Simon Willis had to say about this and then I'm going to say about this and then I'm going to say about this and then I'm going to share my personal concerns about this share my personal concerns about this share my personal concerns about this change. As I mentioned at the start, change. As I mentioned at the start, change. As I mentioned at the start, Simon refers to this as stateless MCP, Simon refers to this as stateless MCP, Simon refers to this as stateless MCP, which I think is a really good way to which I think is a really good way to which I think is a really good way to clarify what this release is. Tuesday clarify what this release is. Tuesday clarify what this release is. Tuesday was stateless MCP day, the roll out of was stateless MCP day, the roll out of was stateless MCP day, the roll out of MCP 2.0, or the 2026 0728 model context MCP 2.0, or the 2026 0728 model context MCP 2.0, or the 2026 0728 model context protocol specification to use the more protocol specification to use the more protocol specification to use the more formal but less memorable name. This is formal but less memorable name. This is formal but less memorable name. This is the most significant change to the MCP the most significant change to the MCP the most significant change to the MCP spec since it first launched, and it's spec since it first launched, and it's spec since it first launched, and it's also served to reignite Simon's personal also served to reignite Simon's personal also served to reignite Simon's personal interest in the protocol. For interest in the protocol. For interest in the protocol. For background, MCP is the model context background, MCP is the model context background, MCP is the model context protocol, which describes a standard way protocol, which describes a standard way protocol, which describes a standard way to expose new tools to LM powered agent to expose new tools to LM powered agent to expose new tools to LM powered agent frameworks. It was introduced by frameworks. It was introduced by frameworks. It was introduced by Anthropic in November of 2024 and it had Anthropic in November of 2024 and it had Anthropic in November of 2024 and it had a huge spike of interest throughout much a huge spike of interest throughout much a huge spike of interest throughout much of 2025 and it became eclipsed by skills of 2025 and it became eclipsed by skills of 2025 and it became eclipsed by skills which was another thing anthropic which was another thing anthropic which was another thing anthropic invented. Kind of crazy that this super invented. Kind of crazy that this super invented. Kind of crazy that this super fancy spec and protocol got replaced by fancy spec and protocol got replaced by fancy spec and protocol got replaced by a markdown file as many things do a markdown file as many things do a markdown file as many things do nowadays and the skills took over when nowadays and the skills took over when nowadays and the skills took over when it became apparent that agent harnesses it became apparent that agent harnesses it became apparent that agent harnesses with access to terminals in curl could with access to terminals in curl could with access to terminals in curl could do most of what MCP did in a more do most of what MCP did in a more do most of what MCP did in a more flexible way. Time is coming back around flexible way. Time is coming back around flexible way. Time is coming back around to MCP now. Giving an agent a shell to MCP now. Giving an agent a shell to MCP now. Giving an agent a shell environment with the ability to access environment with the ability to access environment with the ability to access the internet is fraught with risk and it the internet is fraught with risk and it the internet is fraught with risk and it requires a strong model that is capable requires a strong model that is capable requires a strong model that is capable of effectively driving such an of effectively driving such an of effectively driving such an environment. MCB tools in comparison are environment. MCB tools in comparison are environment. MCB tools in comparison are much easier to audit and control and much easier to audit and control and much easier to audit and control and they're simple enough that smaller they're simple enough that smaller they're simple enough that smaller models that run on a laptop can still models that run on a laptop can still models that run on a laptop can still drive them reasonably well. The new drive them reasonably well. The new drive them reasonably well. The new stateless MCP spec greatly decreases the stateless MCP spec greatly decreases the stateless MCP spec greatly decreases the complexity of implementing both the complexity of implementing both the complexity of implementing both the client and the server for the protocol.

  8. client and the server for the protocol. client and the server for the protocol. He built three of them just this week. He built three of them just this week. He built three of them just this week. He linked this blog post that shows the He linked this blog post that shows the He linked this blog post that shows the before and after where before you had to before and after where before you had to before and after where before you had to have a sticky route to one server and have a sticky route to one server and have a sticky route to one server and share sessions and data and manage all share sessions and data and manage all share sessions and data and manage all of this to make sure that when a request of this to make sure that when a request of this to make sure that when a request came in it always stuck with the one came in it always stuck with the one came in it always stuck with the one server that was hit before. Now it server that was hit before. Now it server that was hit before. Now it doesn't matter. The older stateful MCP doesn't matter. The older stateful MCP doesn't matter. The older stateful MCP which he refers to as legacy MCP which he refers to as legacy MCP which he refers to as legacy MCP required two HTTP requests. One to required two HTTP requests. One to required two HTTP requests. One to initialize the session and obtain an ID initialize the session and obtain an ID initialize the session and obtain an ID and the second to actually start calling and the second to actually start calling and the second to actually start calling tools. But when the tool calls come in, tools. But when the tool calls come in, tools. But when the tool calls come in, it has to match this session ID and get it has to match this session ID and get it has to match this session ID and get routed to the right place, which means routed to the right place, which means routed to the right place, which means it has to be maintaining the connection. it has to be maintaining the connection. it has to be maintaining the connection. Obnoxious. And the new stateless version Obnoxious. And the new stateless version Obnoxious. And the new stateless version uses a single HTTP request, which is uses a single HTTP request, which is uses a single HTTP request, which is what it always should have been. It's so what it always should have been. It's so what it always should have been. It's so much cleaner for both client and much cleaner for both client and much cleaner for both client and serverside implementations. It's also a serverside implementations. It's also a serverside implementations. It's also a better fit for building scalable web better fit for building scalable web better fit for building scalable web apps since now you don't need to apps since now you don't need to apps since now you don't need to maintain serverside state to keep track maintain serverside state to keep track maintain serverside state to keep track of those session IDs or worry about of those session IDs or worry about of those session IDs or worry about routing the same session to the same routing the same session to the same routing the same session to the same backend machine. MCP Explorer is a cool backend machine. MCP Explorer is a cool backend machine. MCP Explorer is a cool tool he built with Codeex in order to tool he built with Codeex in order to tool he built with Codeex in order to explore MCPs to see how they're behaving explore MCPs to see how they're behaving explore MCPs to see how they're behaving with these new changes. the stateless with these new changes. the stateless with these new changes. the stateless Python CLI. You don't even need to Python CLI. You don't even need to Python CLI. You don't even need to install it to try it out. You can just install it to try it out. You can just install it to try it out. You can just call it with uvx. It queries the agentic call it with uvx. It queries the agentic call it with uvx. It queries the agentic mermaid.dev demo mcp. The above command mermaid.dev demo mcp. The above command mermaid.dev demo mcp. The above command returns the following list of tools. I returns the following list of tools. I returns the following list of tools. I can even run this in my terminal. Let's can even run this in my terminal. Let's can even run this in my terminal. Let's try it. That's super cool. This simple try it. That's super cool. This simple try it. That's super cool. This simple command can be pointed at an MCP server command can be pointed at an MCP server command can be pointed at an MCP server and then describe all the things that and then describe all the things that and then describe all the things that are available on it. This one has an are available on it. This one has an are available on it. This one has an execute one for executing mermaid SDK execute one for executing mermaid SDK execute one for executing mermaid SDK code. Describe SDK, render SVG, render code. Describe SDK, render SVG, render code. Describe SDK, render SVG, render as render PNG. all these commands that as render PNG. all these commands that as render PNG. all these commands that could be useful if you want to use the could be useful if you want to use the could be useful if you want to use the agentic mermaid site to generate images

  9. agentic mermaid site to generate images agentic mermaid site to generate images and verify like mermaid diagram code. and verify like mermaid diagram code. and verify like mermaid diagram code. Kind of cool that his demo here isn't Kind of cool that his demo here isn't Kind of cool that his demo here isn't even using agents. He's just calling it even using agents. He's just calling it even using agents. He's just calling it by hand to show how the protocol works by hand to show how the protocol works by hand to show how the protocol works because now it's simple enough to just because now it's simple enough to just because now it's simple enough to just fire off a command and get a result. fire off a command and get a result. fire off a command and get a result. Yeah, that's great. That's awesome. He Yeah, that's great. That's awesome. He Yeah, that's great. That's awesome. He also made one for data set which allows also made one for data set which allows also made one for data set which allows MCP endpoints to be added to any data MCP endpoints to be added to any data MCP endpoints to be added to any data set instance. He's tried building this set instance. He's tried building this set instance. He's tried building this four times, but thanks to the new four times, but thanks to the new four times, but thanks to the new stateless MCP specification, he finally stateless MCP specification, he finally stateless MCP specification, he finally has a version that feels good to has a version that feels good to has a version that feels good to release. Huge. Then release. Huge. Then release. Huge. Then you end up with a bloated spec that you end up with a bloated spec that you end up with a bloated spec that requires you to have an expensive requires you to have an expensive requires you to have an expensive infrastructure to put it out, the infrastructure to put it out, the infrastructure to put it out, the likelihood you bother putting the thing likelihood you bother putting the thing likelihood you bother putting the thing out goes down massively. But now that out goes down massively. But now that out goes down massively. But now that these are stateless, it's way easier to these are stateless, it's way easier to these are stateless, it's way easier to get it working, to get it shipped, to get it working, to get it shipped, to get it working, to get it shipped, to get it integrated, and to scale it if it get it integrated, and to scale it if it get it integrated, and to scale it if it does end up being used heavily, and to does end up being used heavily, and to does end up being used heavily, and to spend $0 if it's not used at all. You spend $0 if it's not used at all. You spend $0 if it's not used at all. You can throw this on any Lambda or can throw this on any Lambda or can throw this on any Lambda or Cloudflare worker or anything now Cloudflare worker or anything now Cloudflare worker or anything now trivially and it's so much better. And trivially and it's so much better. And trivially and it's so much better. And in a world where agents are doing more in a world where agents are doing more in a world where agents are doing more and more unsafe things, MCP as a way to and more unsafe things, MCP as a way to and more unsafe things, MCP as a way to be really strict about what agents can be really strict about what agents can be really strict about what agents can do is sensical because again, if you do is sensical because again, if you do is sensical because again, if you give it a CLI, the agent can do pretty give it a CLI, the agent can do pretty give it a CLI, the agent can do pretty much anything. But if you give it a spec much anything. But if you give it a spec much anything. But if you give it a spec out set of endpoints effectively that out set of endpoints effectively that out set of endpoints effectively that are self-describing in a way the agent are self-describing in a way the agent are self-describing in a way the agent can use, then it can only do the things can use, then it can only do the things can use, then it can only do the things that those endpoints provide. Simon's that those endpoints provide. Simon's that those endpoints provide. Simon's conclusion is that he plans to lean into conclusion is that he plans to lean into conclusion is that he plans to lean into MCP much more now when he builds MCP much more now when he builds MCP much more now when he builds sensitive applications on top of LLMs.

  10. sensitive applications on top of LLMs. sensitive applications on top of LLMs. And I agree. It's crazy that I actually And I agree. It's crazy that I actually And I agree. It's crazy that I actually think the spec is interested, good, and think the spec is interested, good, and think the spec is interested, good, and usable now. But there is a catch. As usable now. But there is a catch. As usable now. But there is a catch. As long as you're on the right version. long as you're on the right version. long as you're on the right version. This is the problem that always happens This is the problem that always happens This is the problem that always happens when specs change, when capabilities when specs change, when capabilities when specs change, when capabilities change, when things change. Imagine change, when things change. Imagine change, when things change. Imagine you're looking at a product and they you're looking at a product and they you're looking at a product and they gladly exclaim, "We support agents." and gladly exclaim, "We support agents." and gladly exclaim, "We support agents." and you're like, "Oh, cool. I would love to you're like, "Oh, cool. I would love to you're like, "Oh, cool. I would love to use this with cloud code." So, you go to use this with cloud code." So, you go to use this with cloud code." So, you go to set it up and the instructions are all set it up and the instructions are all set it up and the instructions are all specific for using it in cursor, but all specific for using it in cursor, but all specific for using it in cursor, but all of the screenshots are the version of of the screenshots are the version of of the screenshots are the version of cursor from like 3 years ago. You're cursor from like 3 years ago. You're cursor from like 3 years ago. You're like, "Wait, I thought you support like, "Wait, I thought you support like, "Wait, I thought you support agents." Well, yeah, they technically do agents." Well, yeah, they technically do agents." Well, yeah, they technically do in the same way that a phone cable might in the same way that a phone cable might in the same way that a phone cable might support USBC. I have like eight support USBC. I have like eight support USBC. I have like eight different tiers of USBC cable in this different tiers of USBC cable in this different tiers of USBC cable in this apartment alone. And the problem is that apartment alone. And the problem is that apartment alone. And the problem is that all of them are USBC. So if I ask for all of them are USBC. So if I ask for all of them are USBC. So if I ask for USBC cable, I don't know if the thing I USBC cable, I don't know if the thing I USBC cable, I don't know if the thing I get is actually going to be what I want. get is actually going to be what I want. get is actually going to be what I want. And now that there is so much absolute And now that there is so much absolute And now that there is so much absolute slop MCP servers that were built in an slop MCP servers that were built in an slop MCP servers that were built in an era where MCP was just a way for a era where MCP was just a way for a era where MCP was just a way for a company to justify their AI budgets, company to justify their AI budgets, company to justify their AI budgets, those are all MCP servers. So if I those are all MCP servers. So if I those are all MCP servers. So if I decide I want to try out MCP and I go to decide I want to try out MCP and I go to decide I want to try out MCP and I go to a website and they say they support MCP, a website and they say they support MCP, a website and they say they support MCP, I'm like, "Okay, cool. I'm going to go I'm like, "Okay, cool. I'm going to go I'm like, "Okay, cool. I'm going to go connect that." and then it uses the old connect that." and then it uses the old connect that." and then it uses the old standard. That sucks. Or what I'm more standard. That sucks. Or what I'm more standard. That sucks. Or what I'm more concerned about is the client side where concerned about is the client side where concerned about is the client side where there's a lot of different agentic

  11. there's a lot of different agentic there's a lot of different agentic clients, harnesses, etc. Things like clients, harnesses, etc. Things like clients, harnesses, etc. Things like cloud code and codeex as well as all of cloud code and codeex as well as all of cloud code and codeex as well as all of the others like open code, pi, cursor, the others like open code, pi, cursor, the others like open code, pi, cursor, of course, anti-gravity. of course, anti-gravity. of course, anti-gravity. There's too many. And a lot of those There's too many. And a lot of those There's too many. And a lot of those support MCP, but do they support the new support MCP, but do they support the new support MCP, but do they support the new MCP? Do they support MCP 2026728? MCP? Do they support MCP 2026728? MCP? Do they support MCP 2026728? because that is very different. And if I because that is very different. And if I because that is very different. And if I build an MCP server that is on the new build an MCP server that is on the new build an MCP server that is on the new standard, the new spec, and somebody standard, the new spec, and somebody standard, the new spec, and somebody goes to install it in an older version goes to install it in an older version goes to install it in an older version of Cloud Code or in some other tool that of Cloud Code or in some other tool that of Cloud Code or in some other tool that just hasn't updated their MCP bindings just hasn't updated their MCP bindings just hasn't updated their MCP bindings yet, that sucks. And this is going to be yet, that sucks. And this is going to be yet, that sucks. And this is going to be a real problem for adoption because the a real problem for adoption because the a real problem for adoption because the previous standard was so heavy, weird, previous standard was so heavy, weird, previous standard was so heavy, weird, and annoying, and it still got and annoying, and it still got and annoying, and it still got implemented everywhere. This new, much implemented everywhere. This new, much implemented everywhere. This new, much more elegant, reliable standard won't be more elegant, reliable standard won't be more elegant, reliable standard won't be implemented everywhere. and two things implemented everywhere. and two things implemented everywhere. and two things that both support MCP might be entirely that both support MCP might be entirely that both support MCP might be entirely different and entirely incompatible. And different and entirely incompatible. And different and entirely incompatible. And that's a real concern I have because that's a real concern I have because that's a real concern I have because that's the point of MCP is that it's a that's the point of MCP is that it's a that's the point of MCP is that it's a simple standard that everything supports simple standard that everything supports simple standard that everything supports on both server and client. Now it isn't.

  12. on both server and client. Now it isn't. on both server and client. Now it isn't. By fixing the standard, they ruined the By fixing the standard, they ruined the By fixing the standard, they ruined the nature of the standard. It is a way way nature of the standard. It is a way way nature of the standard. It is a way way better solution. But this new solution better solution. But this new solution better solution. But this new solution is not backwards compatible because the is not backwards compatible because the is not backwards compatible because the previous implementations on the client previous implementations on the client previous implementations on the client side expect a stateful connection to be side expect a stateful connection to be side expect a stateful connection to be bound. And this is the opposite of that. bound. And this is the opposite of that. bound. And this is the opposite of that. You can't just take something that You can't just take something that You can't just take something that expects a dedicated connection and sever expects a dedicated connection and sever expects a dedicated connection and sever it and expect it to work. There is a it and expect it to work. There is a it and expect it to work. There is a catch though. One of the things that catch though. One of the things that catch though. One of the things that makes this less likely to matter. makes this less likely to matter. makes this less likely to matter. There's this cool thing you guys might There's this cool thing you guys might There's this cool thing you guys might have heard of recently. I don't know. I have heard of recently. I don't know. I have heard of recently. I don't know. I I know they're still niche, but but hear I know they're still niche, but but hear I know they're still niche, but but hear me out. There's this thing called LMS, me out. There's this thing called LMS, me out. There's this thing called LMS, and it turns out LM are good at code. and it turns out LM are good at code. and it turns out LM are good at code. What this means, hypothetically, What this means, hypothetically, What this means, hypothetically, is any tool that you're using that is is any tool that you're using that is is any tool that you're using that is only supporting the old MCP standard on only supporting the old MCP standard on only supporting the old MCP standard on the client side really doesn't have much the client side really doesn't have much the client side really doesn't have much of an excuse to not implement the new of an excuse to not implement the new of an excuse to not implement the new standard. Because if you're a company standard. Because if you're a company standard. Because if you're a company building a harness or an agentic tool or building a harness or an agentic tool or building a harness or an agentic tool or something like that, it's your something like that, it's your something like that, it's your responsibility to keep up to date.

  13. responsibility to keep up to date. responsibility to keep up to date. Because if you built a coding tool that Because if you built a coding tool that Because if you built a coding tool that you think is the bees knees, you think you think is the bees knees, you think you think is the bees knees, you think it's super cool, and I go and try your it's super cool, and I go and try your it's super cool, and I go and try your super cool AI code tool and then it super cool AI code tool and then it super cool AI code tool and then it doesn't work with my MCP services, doesn't work with my MCP services, doesn't work with my MCP services, you're on an old version, and I say, you're on an old version, and I say, you're on an old version, and I say, "Hey, you your harness doesn't work with "Hey, you your harness doesn't work with "Hey, you your harness doesn't work with the new MCP. You say you support MCP, the new MCP. You say you support MCP, the new MCP. You say you support MCP, but it's the old version. Can you update but it's the old version. Can you update but it's the old version. Can you update it?" You only really have two answers it?" You only really have two answers it?" You only really have two answers you can give. They are yes, absolutely, you can give. They are yes, absolutely, you can give. They are yes, absolutely, I'll get an agent on it now or eh, I I'll get an agent on it now or eh, I I'll get an agent on it now or eh, I don't really care or I'm too busy or don't really care or I'm too busy or don't really care or I'm too busy or something along those lines. And if something along those lines. And if something along those lines. And if their agentic coding tools are so their agentic coding tools are so their agentic coding tools are so powerful that they can convince you to powerful that they can convince you to powerful that they can convince you to try their thing, but they're not try their thing, but they're not try their thing, but they're not powerful enough to update the standard powerful enough to update the standard powerful enough to update the standard relatively quickly, you should ignore relatively quickly, you should ignore relatively quickly, you should ignore that person in their tools. So hopefully that person in their tools. So hopefully that person in their tools. So hopefully the way this works out, fingers crossed, the way this works out, fingers crossed, the way this works out, fingers crossed, is that it becomes a bit of a self-own is that it becomes a bit of a self-own is that it becomes a bit of a self-own where the companies building tools that where the companies building tools that where the companies building tools that only support the old version of MCP get only support the old version of MCP get only support the old version of MCP get called out for what they are, which is called out for what they are, which is called out for what they are, which is not understanding of how powerful these not understanding of how powerful these not understanding of how powerful these things are and how quickly they can things are and how quickly they can things are and how quickly they can iterate and fix stuff or they do and it iterate and fix stuff or they do and it iterate and fix stuff or they do and it can be a good filter for which companies can be a good filter for which companies can be a good filter for which companies and products do and don't get it and do and products do and don't get it and do and products do and don't get it and do and don't improve over time. I'm at the and don't improve over time. I'm at the and don't improve over time. I'm at the point where if a company is building an point where if a company is building an point where if a company is building an AI tool and they're not giving AI tool and they're not giving AI tool and they're not giving meaningful updates every week that I meaningful updates every week that I meaningful updates every week that I just assume they've deprecated and just assume they've deprecated and just assume they've deprecated and stopped working on it internally because stopped working on it internally because stopped working on it internally because there is no excuse to not be shipping there is no excuse to not be shipping there is no excuse to not be shipping updates regularly at this point in time.

  14. updates regularly at this point in time. updates regularly at this point in time. It's too easy to ship code that is too It's too easy to ship code that is too It's too easy to ship code that is too good. There's no excuse for not good. There's no excuse for not good. There's no excuse for not upgrading. So that's the only reason upgrading. So that's the only reason upgrading. So that's the only reason this is acceptable. In a previous era this is acceptable. In a previous era this is acceptable. In a previous era where you had to manually update where you had to manually update where you had to manually update everything by hand and rebuild this everything by hand and rebuild this everything by hand and rebuild this whole standard into your stuff, this whole standard into your stuff, this whole standard into your stuff, this would be hell. But in a world where you would be hell. But in a world where you would be hell. But in a world where you can point an LM at the new spec and say, can point an LM at the new spec and say, can point an LM at the new spec and say, "Hey, make sure this works. here's three "Hey, make sure this works. here's three "Hey, make sure this works. here's three test MCPS and it tests it and it does test MCPS and it tests it and it does test MCPS and it tests it and it does awesome to take like an hour with Opus awesome to take like an hour with Opus awesome to take like an hour with Opus or Fable. Not a big deal. So, those are or Fable. Not a big deal. So, those are or Fable. Not a big deal. So, those are my thoughts. That's my one big concern my thoughts. That's my one big concern my thoughts. That's my one big concern is a big change like this that is is a big change like this that is is a big change like this that is inherently not backwards compatible is inherently not backwards compatible is inherently not backwards compatible is going to cause some churn. But in a going to cause some churn. But in a going to cause some churn. But in a world where an LLM can go and update world where an LLM can go and update world where an LLM can go and update your tools for you, it's not a big deal. your tools for you, it's not a big deal. your tools for you, it's not a big deal. What is a big deal is how much more What is a big deal is how much more What is a big deal is how much more powerful this standard is now that it is powerful this standard is now that it is powerful this standard is now that it is stateless and can be properly stateless and can be properly stateless and can be properly implemented across scalable solutions implemented across scalable solutions implemented across scalable solutions without having to spend a shitload of without having to spend a shitload of without having to spend a shitload of time and money and complexity to get time and money and complexity to get time and money and complexity to get there. It's a nice change. It feels like there. It's a nice change. It feels like there. It's a nice change. It feels like it actually understands developers and it actually understands developers and it actually understands developers and what their needs are instead of just what their needs are instead of just what their needs are instead of just trying to be this god spec with every trying to be this god spec with every trying to be this god spec with every possible thing included in it. And I'm possible thing included in it. And I'm possible thing included in it. And I'm excited to play with it now. I can't excited to play with it now. I can't excited to play with it now. I can't believe I'm excited to go try out MCP believe I'm excited to go try out MCP believe I'm excited to go try out MCP again, but I really am. And I can't wait again, but I really am. And I can't wait again, but I really am. And I can't wait to see what I'm able to do with it. Let to see what I'm able to do with it. Let to see what I'm able to do with it. Let me know what you guys think. Are you me know what you guys think. Are you me know what you guys think. Are you going to stick with your CLIs or do you going to stick with your CLIs or do you going to stick with your CLIs or do you see real potential with MCP now that we see real potential with MCP now that we see real potential with MCP now that we have these changes?

Summary

The discussion revisits the MCP standard, highlighting its past bloat and resource inefficiency. A new stateless MCP spec is introduced, as mentioned by Simon Wilson, transforming it from a subpar CLI to a potentially useful integration. This evolution offers significant improvements, making MCP a more viable and exciting tool for modern applications.

View original episode ↗