Talk Python To Me · Hands-On Engineering Podcasts · November 2026
Michael Kennedy asked for her view on the MCP versus command-line debate. She describes a colleague's test where an agent fixed a real bug using the GitHub CLI, the GitHub MCP server or neither. Her advice is to offer all of them and test each with agents.
Yes, we have to have the required MCP versus CLI debate. We do. It wouldn't be
complete if we didn't do it.
I'm actually obliged. So yeah, it's very interesting, actually. Like my colleague has a project that's now called Scope. And in this project, they actually will set up scenarios to see how well an agent succeeds at a particular task in a particular environment. And the example that he gave in a talk the other day was using the GitHub CLI GH command and the GitHub MCP server and then just nothing at all compared to see like how long would it take? How successful would it be? Like would it, so in this case, it was actually fixing a bug on one of my repos, which I didn't know he was going to do. So I was surprised to see this PR the morning of his talk. But yeah, so he's, you know, so it's comparing to see, you know, token efficiency success, number of tool calls, all that stuff, right? Now, the results from that particular experiment was that the GitHub CLI was the best, right? And I think a lot of people would actually predict that. Like it was, you know, it was, you required less tokens overall and was successful more of the time. But why is that? Part of that is because the agents, like…
My agent runs rough a lot. I don't know about yours, but I told the standing rule for all of my agents, if they're doing coding, that is, is whenever you're done, you're not done until rough format, rough check, and TY check. All of those run without warnings, without errors. You know what I mean?…
Right. So that, I mean, you can put that in your agents.md. I oftentimes have that in my agents.md. You can even formalize like a lot of these coding agents have what's called like a hook, at least VS Code, we call it a hook. So you can have a hook that runs every single time and make sure that it…
If you want to be super old school, I mean, we're talking like 2024 old school, you could put it in a Git pre-commit hook, really. Oh, yeah, of course.