전사 🔗
WEBVTT
00:00:00.240 --> 00:00:03.980
Should your agent call an MCP server or just run a CLI?
00:00:04.540 --> 00:00:09.320
Pamela Fox joins us to share how she thinks about connecting AIs and her data.
00:00:09.960 --> 00:00:13.100
She's taught MCP workshops from PyCon to VR developers,
00:00:13.480 --> 00:00:15.940
and every week an agent combs her Gmail,
00:00:16.880 --> 00:00:19.480
Outlook, and X history to build her news roundup.
00:00:20.000 --> 00:00:21.220
She uses MCP all day,
00:00:21.760 --> 00:00:23.760
yet there are still times when you should skip it.
00:00:24.240 --> 00:00:27.140
You'll hear how her colleague pitted the GitHub CLI
00:00:27.180 --> 00:00:30.000
against the GitHub MCP server on a real bug.
00:00:30.400 --> 00:00:31.660
The CLI used fewer tokens.
00:00:32.140 --> 00:00:33.180
It succeeded more often.
00:00:33.940 --> 00:00:35.720
So do we choose CLIs,
00:00:36.020 --> 00:00:36.580
MCPs,
00:00:36.780 --> 00:00:37.740
or even just APIs
00:00:38.000 --> 00:00:40.520
for connecting our agents to our data and services?
00:00:41.200 --> 00:00:41.800
Let's find out.
00:00:42.180 --> 00:00:44.440
This is Talk Python To Me, episode 569,
00:00:44.540 --> 00:00:47.160
recorded October 15th, 2026.
00:01:04.320 --> 00:01:09.000
Welcome to Talk Python To Me, the number one Python podcast for developers and data scientists.
00:01:09.520 --> 00:01:10.920
This is your host, Michael Kennedy.
00:01:11.120 --> 00:01:14.840
I'm a PSF fellow who's been coding for over 25 years.
00:01:15.260 --> 00:01:16.540
Let's connect on social media.
00:01:16.980 --> 00:01:19.180
You'll find me and Talk Python on Mastodon, Bluesky,
00:01:19.560 --> 00:01:20.000
and X.
00:01:20.250 --> 00:01:22.180
The social links are all in your show notes.
00:01:22.600 --> 00:01:25.540
You can find over 10 years of past episodes at
00:01:25.660 --> 00:01:26.460
Talk Python.fm.
00:01:26.740 --> 00:01:29.840
And if you want to be part of the show, you can join our recording live streams.
00:01:30.260 --> 00:01:34.120
That's right. We live stream the raw uncut version of each episode on YouTube.
00:01:34.780 --> 00:01:35.160
Just visit
00:01:35.300 --> 00:01:39.140
Talk Python.fm slash YouTube to see the schedule of upcoming events.
00:01:39.330 --> 00:01:40.480
Be sure to subscribe there and
00:01:40.490 --> 00:01:43.020
press the bell so you'll get notified anytime we're recording.
00:01:43.620 --> 00:01:45.020
Before we dive into the show,
00:01:45.200 --> 00:01:49.220
I want to tell you about an upcoming members meetup here at Talk Python.
00:01:49.960 --> 00:01:50.420
The title,
00:01:50.700 --> 00:01:54.140
SQLite Might Actually Be All You Need.
00:01:54.840 --> 00:01:56.780
This talk dives into running SQLite in production
00:01:56.900 --> 00:01:57.980
and why, surprisingly,
00:01:58.340 --> 00:02:02.260
it might be one of the best production databases you can choose.
00:02:03.120 --> 00:02:04.960
Here's something I haven't really talked about yet.
00:02:05.460 --> 00:02:07.500
Talk Python doesn't run on MongoDB anymore.
00:02:08.039 --> 00:02:09.080
After years on Mongo,
00:02:09.300 --> 00:02:12.260
I've moved almost all of our sites to SQLite,
00:02:12.580 --> 00:02:14.220
the database that you might file under.
00:02:14.680 --> 00:02:16.040
Fine for prototypes and phone apps.
00:02:16.680 --> 00:02:19.760
I knew an in-process database would have some speed advantages,
00:02:20.100 --> 00:02:25.200
but what I didn't expect is that it's 40 to 300 times faster on our data.
00:02:26.020 --> 00:02:26.240
Now,
00:02:26.400 --> 00:02:28.920
looking up a guest takes 1.5 microseconds.
00:02:29.180 --> 00:02:31.560
That's 1 1,000th of a millisecond,
00:02:31.760 --> 00:02:35.320
or over 600,000 calls a second from plain Python.
00:02:36.120 --> 00:02:36.640
And a write?
00:02:37.220 --> 00:02:39.540
Well, that's 1 1 100th of a millisecond.
00:02:40.260 --> 00:02:42.620
But then there's that question that scares people off.
00:02:42.700 --> 00:02:43.920
What happens when the server dies?
00:02:44.580 --> 00:02:46.240
This is where the surprises live.
00:02:47.000 --> 00:02:49.740
So I hope you join me for the members tech meetup.
00:02:49.940 --> 00:02:51.740
It's on December 2nd at 10 a.m.
00:02:52.000 --> 00:02:53.020
U.S. Pacific time.
00:02:53.740 --> 00:02:55.700
Find all the details at Talk Python.
00:02:55.850 --> 00:02:58.160
Just click membership and go to the tech talks.
00:02:58.820 --> 00:02:59.920
Add it to your calendar right there.
00:03:00.050 --> 00:03:03.260
I hope to see you at the meetup and share some SQLite surprises with you.
00:03:04.020 --> 00:03:04.380
Pamela,
00:03:04.540 --> 00:03:06.080
welcome to Talk Python To Me.
00:03:06.280 --> 00:03:08.580
It is long past time I had you on the show.
00:03:08.790 --> 00:03:09.440
Really glad you're here.
00:03:10.000 --> 00:03:10.360
Awesome.
00:03:10.860 --> 00:03:11.560
It's so fun to be here.
00:03:11.800 --> 00:03:17.220
We're going to talk about some of the craziness of 2026 and choices.
00:03:18.010 --> 00:03:20.980
Should we MCP to MCP or not?
00:03:21.140 --> 00:03:23.440
Was that the Shakespeare question? I think that was it.
00:03:23.500 --> 00:03:23.940
Yeah, exactly.
00:03:24.170 --> 00:03:25.960
Or the CLI or APIs,
00:03:26.310 --> 00:03:32.320
or basically I've got some data and services and I want to connect them to my code, to my agents.
00:03:32.580 --> 00:03:33.520
How do we do that, right?
00:03:33.580 --> 00:03:39.780
I know you've written a whole lot about this and people should absolutely check out your blog, but especially conference talks.
00:03:40.320 --> 00:03:43.160
You're an awesome technologist and I really loved all of your presentations,
00:03:43.560 --> 00:03:45.700
you know, including the one just at PyBay where we were.
00:03:45.820 --> 00:03:47.580
How was PyBay? What do you think?
00:03:48.780 --> 00:03:50.780
I thought PyBay was really fun.
00:03:51.120 --> 00:03:53.220
I love the Python conferences,
Load full transcript
00:03:53.780 --> 00:03:57.880
getting to meet the local community and you had a great talk at it as well.
00:03:58.140 --> 00:03:58.480
Oh, yeah.
00:03:58.700 --> 00:04:00.840
Thanks. That was really fun about Talk Python in production.
00:04:00.880 --> 00:04:02.000
that will come out eventually.
00:04:02.280 --> 00:04:04.480
I'm sure the videos of those will come out. They were recorded,
00:04:04.700 --> 00:04:06.100
so they wouldn't record them for no reason.
00:04:07.280 --> 00:04:07.680
Yes.
00:04:08.360 --> 00:04:10.120
So really, really cool. Now, before we dive in,
00:04:10.460 --> 00:04:11.060
as per usual,
00:04:11.260 --> 00:04:12.920
just give people a quick background on you.
00:04:13.200 --> 00:04:13.300
Yeah,
00:04:13.760 --> 00:04:13.900
sure.
00:04:14.100 --> 00:04:15.940
So I am Pamela Fox. I am
00:04:16.260 --> 00:04:19.400
currently at Microsoft and or GitHub,
00:04:20.120 --> 00:04:24.000
whichever company you prefer more.
00:04:24.420 --> 00:04:25.580
And I am a principal
00:04:25.840 --> 00:04:26.420
cloud advocate.
00:04:26.900 --> 00:04:28.380
So that means that generally,
00:04:28.540 --> 00:04:30.279
like I'm using all of our developer tools
00:04:30.300 --> 00:04:32.620
and showing developers how to use them.
00:04:33.520 --> 00:04:35.180
I tend to focus on Python.
00:04:35.720 --> 00:04:39.860
We had like an official Python advocacy team for four years
00:04:40.280 --> 00:04:41.860
and we don't anymore,
00:04:42.790 --> 00:04:43.380
which is sad.
00:04:43.380 --> 00:04:46.540
And that's kind of part of the change due to coding agents
00:04:46.880 --> 00:04:49.760
where like languages are not as much of a thing anymore
00:04:50.360 --> 00:04:52.880
because the coding agents can just code and whatever
00:04:53.500 --> 00:04:54.920
and all that matters is the output.
00:04:55.640 --> 00:04:56.060
So now,
00:04:56.500 --> 00:04:56.760
you know,
00:04:57.120 --> 00:04:58.739
I guess there's just this big question
00:04:58.760 --> 00:05:01.880
as to how much does your language even matter anymore.
00:05:02.010 --> 00:05:04.480
So I'm glad on that note with PyBay,
00:05:04.880 --> 00:05:06.320
I currently think it's great
00:05:06.520 --> 00:05:08.520
that we still have these Python-specific conferences.
00:05:09.060 --> 00:05:12.000
It will be interesting to see how long language
00:05:12.600 --> 00:05:14.920
is the theme that holds together a community.
00:05:15.240 --> 00:05:16.420
What an interesting idea.
00:05:16.520 --> 00:05:18.740
I've been thinking about this a lot too, and I fright.
00:05:19.320 --> 00:05:21.400
I was, before we go down this AI thing,
00:05:22.440 --> 00:05:23.580
when you were talking about
00:05:24.060 --> 00:05:26.400
not specifically having a Python team,
00:05:26.900 --> 00:05:27.580
one of the thoughts I had,
00:05:27.700 --> 00:05:29.080
well, like Python is just so popular,
00:05:29.240 --> 00:05:30.080
just it's expected.
00:05:30.540 --> 00:05:32.620
It's not this niche thing where we brought in a few people
00:05:32.780 --> 00:05:34.980
that know this weird no curly braces language.
00:05:35.580 --> 00:05:36.020
You know what I mean?
00:05:36.160 --> 00:05:38.940
But like just the advocates know about Python.
00:05:39.420 --> 00:05:41.080
And so maybe you don't need a specific Python team.
00:05:41.360 --> 00:05:44.880
Yeah, I guess two things happen is one is that more and more
00:05:45.200 --> 00:05:46.980
the advocates from the other language teams
00:05:47.440 --> 00:05:50.460
found themselves using Python because you almost have to now
00:05:50.600 --> 00:05:54.400
because that's like it became the default language for new SDKs, right?
00:05:54.480 --> 00:05:56.400
When I first joined Marksoft, it was the opposite, right?
00:05:56.500 --> 00:05:58.220
where we had to like kind of beg for a Python SDK.
00:05:59.140 --> 00:06:02.740
And then people had to beg for like SDKs in C#,
00:06:02.950 --> 00:06:04.140
which is a crazy thing for Microsoft
00:06:04.460 --> 00:06:05.720
because Microsoft is like a huge,
00:06:05.940 --> 00:06:06.800
you know, C# user.
00:06:07.260 --> 00:06:08.780
Like they may have created the language.
00:06:09.700 --> 00:06:09.900
Right,
00:06:10.200 --> 00:06:10.820
that thing.
00:06:10.980 --> 00:06:11.340
Yes, yes,
00:06:11.580 --> 00:06:11.860
that's true.
00:06:12.840 --> 00:06:14.360
So yeah, so I think part of it
00:06:14.460 --> 00:06:16.180
is that just basically all advocates,
00:06:16.700 --> 00:06:16.900
you know,
00:06:17.080 --> 00:06:18.020
they're, you know, we're all there.
00:06:18.120 --> 00:06:19.500
Everyone's using Python now,
00:06:19.900 --> 00:06:20.860
all using JavaScript now.
00:06:21.040 --> 00:06:21.720
Everyone's using every,
00:06:21.880 --> 00:06:21.980
you know,
00:06:22.040 --> 00:06:24.020
because it's just so easy to add on,
00:06:24.260 --> 00:06:25.240
you know, a React front end.
00:06:25.440 --> 00:06:27.180
I saw a talk from my dad the other day.
00:06:27.340 --> 00:06:28.380
He's a computer scientist.
00:06:29.300 --> 00:06:31.940
And on his slide, he had like React front end.
00:06:31.950 --> 00:06:32.420
I was like, what?
00:06:32.960 --> 00:06:33.100
Dad,
00:06:33.560 --> 00:06:34.220
you're doing React?
00:06:34.480 --> 00:06:35.300
Like what has happened,
00:06:35.560 --> 00:06:35.620
right?
00:06:35.720 --> 00:06:38.560
That's only due to coding agents.
00:06:38.670 --> 00:06:39.360
I guarantee it.
00:06:39.430 --> 00:06:44.420
Because there's no way that my dad would be just like suddenly like, well, I'm like seven
00:06:44.480 --> 00:06:44.800
years old.
00:06:44.850 --> 00:06:46.500
I think it's time that I learned React,
00:06:46.860 --> 00:06:46.960
right?
00:06:47.240 --> 00:06:47.580
Exactly.
00:06:47.700 --> 00:06:47.940
It's like,
00:06:48.340 --> 00:06:49.860
Pamela, what are you using Node for?
00:06:49.980 --> 00:06:50.980
We all use Bun now.
00:06:51.140 --> 00:06:51.460
Come on.
00:06:52.500 --> 00:06:52.740
What?
00:06:53.000 -->
00:06:53.640
Who are you?
00:06:54.180 --> 00:06:54.340
Yeah.
00:06:54.640 --> 00:06:57.000
I need to call him up so we can talk JavaScript now.
00:06:57.180 --> 00:06:57.360
Funny.
00:06:57.540 --> 00:06:57.640
Yeah,
00:06:57.820 --> 00:06:58.140
you're right.
00:06:58.360 --> 00:07:03.040
And I honestly don't even know if I want to talk about it because it makes me a little bit sad.
00:07:03.140 --> 00:07:07.060
But I do think that there is also something to the second half of the reason that you gave.
00:07:07.480 --> 00:07:10.480
And that's we don't necessarily have to read the code.
00:07:10.880 --> 00:07:11.440
Should we read the code?
00:07:11.480 --> 00:07:12.260
I don't know.
00:07:12.380 --> 00:07:13.400
I'm very conflicted.
00:07:13.400 --> 00:07:17.880
I actually was thinking today about building a little GUI application,
00:07:18.460 --> 00:07:19.340
plug into an LLM,
00:07:19.720 --> 00:07:20.640
maybe an MCP, who knows,
00:07:20.920 --> 00:07:26.920
that would basically go to a code base and go from this git commit to that one i need i need a tour
00:07:27.060 --> 00:07:32.600
of what has happened will you explain this to me because git history is not there's a thousand
00:07:32.840 --> 00:07:35.900
change files what is significant what do i you know what i mean something like that would be cool
00:07:36.260 --> 00:07:40.560
yeah yeah we care more about the high level changes and also just how they're being verified
00:07:41.020 --> 00:07:47.999
so i think like in terms of python you know what i am most interested in is you know the verifiability
00:07:48.020 --> 00:07:49.880
We do have great testing frameworks in Python.
00:07:50.120 --> 00:07:51.200
So I think we can continue,
00:07:51.780 --> 00:07:52.080
you know,
00:07:52.580 --> 00:07:54.260
talking about those testing frameworks,
00:07:54.600 --> 00:07:55.020
like how you
00:07:55.180 --> 00:08:00.080
could encourage your agents to use PlayWrite and use pytest and use hypothesis and schema
00:08:00.260 --> 00:08:01.860
thesis and all of that stuff.
00:08:02.100 --> 00:08:02.380
And,
00:08:02.640 --> 00:08:06.560
you know, at least guide it to using like an async FastAPI,
00:08:07.140 --> 00:08:08.140
you know, versus a
00:08:08.340 --> 00:08:08.840
sync framework.
00:08:10.420 --> 00:08:12.340
But the specifics of Python,
00:08:13.080 --> 00:08:13.340
you know,
00:08:13.580 --> 00:08:15.060
not as useful.
00:08:15.300 --> 00:08:19.100
I was reading the Python 315 release notes and I was like, oh, all of this is great.
00:08:19.300 --> 00:08:19.640
I'm glad.
00:08:19.840 --> 00:08:20.140
I know.
00:08:20.140 --> 00:08:21.240
I'm glad they added this.
00:08:21.660 --> 00:08:26.320
But none of this matters until the LLMs know it.
00:08:26.920 --> 00:08:27.200
I see.
00:08:27.620 --> 00:08:32.659
Until they've been pointed at the release notes and until I'm using 315 in production.
00:08:32.880 --> 00:08:34.219
We're going to see what the world brings.
00:08:34.440 --> 00:08:36.539
But it is trending this way and it is weird.
00:08:36.919 --> 00:08:40.700
I don't think that means that people without programming skills are not needed or don't
00:08:40.700 --> 00:08:41.140
have value.
00:08:41.400 --> 00:08:42.320
I think there's tons.
00:08:42.380 --> 00:08:45.200
It's just not in the structure level.
00:08:45.420 --> 00:08:45.700
It's like, okay,
00:08:45.960 --> 00:08:47.200
we need this kind of design pattern.
00:08:47.260 --> 00:08:48.560
We need this kind of storage.
00:08:49.160 --> 00:08:50.840
What are we going to do about, you know,
00:08:51.020 --> 00:08:54.240
durability if this data center goes down and we got our data there?
00:08:54.560 --> 00:08:55.340
That kind of questions,
00:08:55.520 --> 00:08:55.620
yeah?
00:08:55.920 --> 00:08:57.440
Yeah, and that's all things we've learned.
00:08:57.600 --> 00:09:01.220
You know, syntax was just one way that we expressed our programming knowledge.
00:09:01.860 --> 00:09:02.200
Now,
00:09:02.520 --> 00:09:06.260
you know, we're really going to express the architecture side of it because that's where,
00:09:06.640 --> 00:09:06.760
you know,
00:09:06.800 --> 00:09:09.660
we still need to think a lot about how we're going to architecture things,
00:09:09.820 --> 00:09:10.780
what the protocols are
00:09:11.200 --> 00:09:13.460
that we're going to use in order to interface across systems,
00:09:13.940 --> 00:09:15.020
which that's like a good lead
00:09:15.020 --> 00:09:16.320
in for today's topic,
00:09:16.700 --> 00:09:16.820
because,
00:09:17.040 --> 00:09:20.000
you know, that I think the protocols are increasingly the important
00:09:20.200 --> 00:09:20.340
part.
00:09:20.520 --> 00:09:20.660
Absolutely.
00:09:21.220 --> 00:09:23.380
All right. Well, let's go ahead and dive into it. I think,
00:09:23.820 --> 00:09:24.580
as I said, I kind of
00:09:24.640 --> 00:09:29.640
want to structure this around MCP because that's maybe the most obvious choice. Somebody says,
00:09:29.760 --> 00:09:32.120
I want to connect this thing to my AI. Well,
00:09:32.320 --> 00:09:33.740
MCP were obviously right.
00:09:34.020 --> 00:09:34.140
However,
00:09:34.820 --> 00:09:35.339
there's a lot of
00:09:35.320 --> 00:09:35.480
options,
00:09:35.940 --> 00:09:36.420
as we'll see.
00:09:36.620 --> 00:09:41.020
And there's times you do and don't use MCPs. But let's start with that
00:09:41.240 --> 00:09:41.400
story.
00:09:41.660 --> 00:09:47.260
So I had a Den Bilomarski on the show a while ago to talk about MCP protocol.
00:09:47.580 --> 00:09:48.240
But honestly,
00:09:48.620 --> 00:09:51.300
it's like a year ago and in AI world,
00:09:51.660 --> 00:09:53.460
you know, how crazy, how long ago was that?
00:09:53.740 --> 00:09:54.240
So maybe we
00:09:54.280 --> 00:09:55.840
should just start from the beginning.
00:09:56.040 --> 00:09:57.520
You know, what is an MCP?
00:09:58.440 --> 00:09:59.680
What is MCP? And what is an MCP
00:09:59.920 --> 00:10:00.000
server?
00:10:00.260
--> 00:10:01.240
Like, why do we care about this stuff?
00:10:01.520 --> 00:10:01.580
Right.
00:10:01.880 --> 00:10:03.520
So MCP is,
00:10:03.700 --> 00:10:04.739
you know, it's the standard
00:10:04.740 --> 00:10:08.320
for helping AI applications to discover context,
00:10:09.400 --> 00:10:12.120
or here it says to connect to external systems.
00:10:13.420 --> 00:10:15.080
We basically wanted a standard way
00:10:15.200 --> 00:10:17.360
where we could extend our agents
00:10:17.900 --> 00:10:20.120
with access to additional tools,
00:10:20.340 --> 00:10:20.420
right?
00:10:20.480 --> 00:10:22.580
So it's extensibility story for agents,
00:10:22.920 --> 00:10:23.620
and it's a standard.
00:10:23.680 --> 00:10:24.820
And it's like, the cool thing is,
00:10:24.900 --> 00:10:26.020
it's like the first standard
00:10:26.240 --> 00:10:28.840
that everybody jumped on board with, right?
00:10:28.880 --> 00:10:31.120
It is so hard to get all these companies
00:10:31.440 --> 00:10:32.800
to agree right now,
00:10:33.060 --> 00:10:34.980
And they're like fighting on Twitter.
00:10:35.140 --> 00:10:36.400
It's like, come on, can't we all get along?
00:10:37.100 --> 00:10:38.080
And finally with MCP,
00:10:38.360 --> 00:10:39.080
you know, we can all get along.
00:10:39.320 --> 00:10:39.800
So this is,
00:10:40.040 --> 00:10:42.100
you know, originally came from Anthropic with Claude.
00:10:43.080 --> 00:10:45.320
But now there's great support in ChatGVT.
00:10:45.720 --> 00:10:48.400
You know, at Microsoft, we've got GitHub Copilot and VS Code.
00:10:49.580 --> 00:10:52.920
But there's also like consumer facing tools that have support for it.
00:10:53.180 --> 00:10:55.300
My business friends talk to me about MCP.
00:10:56.720 --> 00:10:57.120
Really?
00:10:57.280 --> 00:10:57.460
Okay.
00:10:57.880 --> 00:10:58.040
Yeah,
00:10:58.240 --> 00:10:58.360
yeah.
00:10:59.140 --> 00:11:01.720
Their messaging made me like, oh, I just pitched this,
00:11:01.960 --> 00:11:02.180
you know,
00:11:02.280 --> 00:11:04.500
like extra using MCP.
00:11:04.920 --> 00:11:06.280
So yeah,
00:11:06.440 --> 00:11:07.000
because it's,
00:11:07.770 --> 00:11:07.960
you know,
00:11:08.140 --> 00:11:10.300
it's a standard that works across agents
00:11:10.560 --> 00:11:13.940
and agents are both developer facing and user agent.
00:11:14.160 --> 00:11:15.300
There's, you know, in the last few weeks,
00:11:15.480 --> 00:11:17.220
we've had GrokBot and Muse
00:11:18.810 --> 00:11:21.300
and there's so many new ones that pop out every week.
00:11:22.320 --> 00:11:26.320
And a lot of those are connecting behind the scenes using MCP.
00:11:26.350 --> 00:11:27.580
They don't always call it MCP.
00:11:27.800 --> 00:11:28.780
Chachapi calls it plugins,
00:11:29.190 --> 00:11:29.340
right?
00:11:30.220 --> 00:11:31.560
Like on their opening iDev day,
00:11:31.700 --> 00:11:33.980
They talked about ChattoBee plugins behind the scenes.
00:11:34.370 --> 00:11:37.820
Those are very much based off the MCP standard,
00:11:38.180 --> 00:11:38.280
right?
00:11:38.600 --> 00:11:38.780
So,
00:11:39.230 --> 00:11:46.620
you know, you're not always going to see MCP prominently displayed in the UI for these user-facing agents.
00:11:47.390 --> 00:11:53.820
Yeah, I think if I go to Claude and I try to connect to it, it tells me what you need to do is add a connection,
00:11:54.340 --> 00:11:55.180
not an MCP server,
00:11:55.360 --> 00:11:55.420
right?
00:11:55.460 --> 00:11:57.260
I'm like, this is where the MCP goes?
00:11:57.540 --> 00:11:57.940
You know what I mean?
00:11:58.280 --> 00:11:58.480
Yeah,
00:11:58.680 --> 00:11:58.740
yeah.
00:11:58.780 --> 00:12:00.860
So I think they call it like connectors or connections.
00:12:01.700 --> 00:12:03.640
I'd be happy if they all call them MCP,
00:12:03.800 --> 00:12:06.460
but a lot of times they do wrap some additional things on top.
00:12:06.520 --> 00:12:07.400
Like ChatGPT,
00:12:08.300 --> 00:12:14.260
they wrap plugins in some additional metadata that helps them plug into the UI certain ways.
00:12:14.580 --> 00:12:17.980
So I think that's why they're calling it,
00:12:18.600 --> 00:12:21.220
they're coming up with their own name for it,
00:12:21.420 --> 00:12:23.160
just so they can add additional things on it.
00:12:23.420 --> 00:12:24.760
Yeah, that makes a lot of sense.
00:12:25.140 --> 00:12:27.240
And I guess it's like an API,
00:12:27.860 --> 00:12:27.960
right?
00:12:28.300 --> 00:12:28.500
Right.
00:12:28.640 --> 00:12:29.900
Okay. So here's how it actually,
00:12:30.080 --> 00:12:32.200
like, I'll just tell you the actual, I mean, this is a developer,
00:12:32.560 --> 00:12:37.080
right? So what actually happens is first there's a handshake, right?
00:12:37.240 --> 00:12:43.720
So you register an MCP server and a lot of times your server is what's called an HTTP server. So there'll be actually like a URL for it.
00:12:44.460 --> 00:12:47.920
So it's like, you know, hpcoolserver.com slash MCP.
00:12:48.160 --> 00:12:51.880
And then the agent will connect to that server.
00:12:52.190 --> 00:12:54.100
So it'll send a handshake to that server.
00:12:54.270 --> 00:12:58.480
And during that handshake, it's going to ask the server what tools it has.
00:12:58.560 --> 00:13:02.540
because tools are like the there's other things that servers can expose but tools are like the
00:13:02.620 --> 00:13:09.420
really really important thing um so it'll say uh tools slash list so it sends this is a json rpc
00:13:09.420 --> 00:13:15.180
so it sends this json rpc uh you know hp requests to the server say hey what tools do you have
00:13:15.420 --> 00:13:20.360
and any other sort of discoverability it wants to do at that point mcp servers will support skills
00:13:20.620 --> 00:13:25.339
soon as well that's exciting um so it could discover those too so it discovers the tools
00:13:25.640 --> 00:13:26.700
the tools will come back.
00:13:26.900 --> 00:13:27.800
And once it has the tools,
00:13:27.980
--> 00:13:30.520
now the agent can populate its tools list
00:13:30.880 --> 00:13:32.020
with all the list of tools.
00:13:32.680 --> 00:13:37.060
And then it can decide to send those tool names to the LLM every time
00:13:37.160 --> 00:13:38.820
it's processing a user request.
00:13:39.340 --> 00:13:40.520
And if the LLM,
00:13:40.740 --> 00:13:42.000
the user request and says, oh,
00:13:42.240 --> 00:13:42.760
I've got a great
00:13:42.980 --> 00:13:44.180
tool for that, like book hotel,
00:13:44.720 --> 00:13:46.800
right? Maybe that's a tool and they want to book hotels.
00:13:47.480 --> 00:13:52.560
Then it's going to send a request to the MSP server that says it's like tools slash calls.
00:13:53.020 --> 00:13:57.280
And then it sends in arguments and says, OK, hotel in city, San Francisco,
00:13:57.640 --> 00:13:58.040
start date,
00:13:58.770 --> 00:14:01.000
October 15th, end date, October 17th.
00:14:01.190 --> 00:14:04.380
And so that sends, you know, basically like a remote procedure call like to the,
00:14:05.140 --> 00:14:09.840
you know, to that MSP server and the server processes it and responds back with,
00:14:10.000 --> 00:14:10.940
you know, JSON or,
00:14:11.240 --> 00:14:12.440
you know, however it wants to respond.
00:14:12.820 --> 00:14:16.020
Yeah, it's a little bit like an HTTP endpoint,
00:14:16.380 --> 00:14:24.600
but it's a little bit where the tools are, the individual functions that you might or the endpoints you might call with an API client.
00:14:25.020 --> 00:14:26.840
But there's kind of a negotiation as well.
00:14:26.890 --> 00:14:28.060
Like, do you support streaming?
00:14:29.180 --> 00:14:30.980
What version of MCP are you?
00:14:31.260 --> 00:14:35.400
So it's a little bit more high level than the HTTP APIs,
00:14:35.670 --> 00:14:35.800
right?
00:14:35.960 --> 00:14:40.440
Like maybe GraphQL or one of those types of something built on top of it, right?
00:14:40.500 --> 00:14:42.640
But it's still very approachable for Python people.
00:14:42.960 --> 00:14:47.280
It's more opinionated because it's saying like, you know, it's saying this is specifically for agents.
00:14:47.880 --> 00:14:49.440
Agents want to know about tools.
00:14:49.660 --> 00:14:50.500
That's what they need.
00:14:50.900 --> 00:14:52.960
And they also want to know about, you know, in the future about skills.
00:14:53.260 --> 00:14:53.360
Right.
00:14:54.459 --> 00:14:54.860
But,
00:14:55.620 --> 00:15:00.080
you know, it's using mechanisms that we understand behind the scenes like JSON RPC.
00:15:00.600 --> 00:15:00.740
Nice.
00:15:01.080 --> 00:15:04.080
Yeah, I just last year, I can't remember exactly when it was.
00:15:04.080 --> 00:15:06.420
I built a MCP server for the podcast.
00:15:07.060 --> 00:15:08.380
So you can ask it like,
00:15:08.770 --> 00:15:10.900
what did Talk Python cover on this?
00:15:11.040 --> 00:15:15.660
And instead of having to go and do a full search of all the pages of the website,
00:15:16.020 --> 00:15:20.980
the thing could just connect and run database index backed super fast queries,
00:15:21.220 --> 00:15:21.280
right?
00:15:21.290 --> 00:15:23.020
So it gets really quick answers and answers.
00:15:23.780 --> 00:15:25.500
I'm seeing now a lot of conferences.
00:15:26.000 --> 00:15:32.600
Well, not maybe a lot, but the nerdiest conferences will actually have MCP servers to interact with their data, right?
00:15:32.780 --> 00:15:34.640
So AI engineer did that and that was really fun.
00:15:34.920 --> 00:15:35.380
That's awesome.
00:15:35.660 --> 00:15:39.240
example for the talk's schedule and stuff.
00:15:39.300 --> 00:15:39.400
Like,
00:15:39.800 --> 00:15:41.200
hey, I'm interested in this.
00:15:41.260 --> 00:15:42.540
What talk should I go see next?
00:15:42.900 --> 00:15:43.000
Right.
00:15:43.140 --> 00:15:45.160
That kind of question would be awesome to answer right away.
00:15:45.580 --> 00:15:45.680
Yeah.
00:15:45.720 --> 00:15:45.920
And then,
00:15:46.140 --> 00:15:50.340
so here's what's nice about MSP is that then you can connect multiple MSP servers
00:15:50.540 --> 00:15:50.860
to your agent,
00:15:51.020 --> 00:15:51.080
right?
00:15:51.120 --> 00:15:51.400
So example,
00:15:51.600 --> 00:15:52.620
you could connect the,
00:15:52.900 --> 00:15:57.200
you know, like the AI engineer MSP server for that conference.
00:15:57.320 --> 00:15:59.400
And you could also connect like the Google Calendar,
00:15:59.800 --> 00:15:59.900
like,
00:16:00.100 --> 00:16:02.160
you know, or in my case, I
00:16:02.020 --> 00:16:05.820
use the Microsoft WorkIQ MCP server for access to my Outlook.
00:16:06.400 --> 00:16:07.580
And so then in theory, you can be
00:16:07.660 --> 00:16:07.920
like, hey,
00:16:08.080 --> 00:16:10.680
which of these talks am I even like available to attend?
00:16:11.660 --> 00:16:12.740
Could you also just like
00:16:13.080 --> 00:16:14.040
put it on my calendar?
00:16:14.520 --> 00:16:14.640
Right.
00:16:15.320 --> 00:16:20.520
So this is what excites me about MCP is that MCP enables like
00:16:20.800 --> 00:16:22.680
us to make mashups really easily.
00:16:22.880 --> 00:16:22.940
Right.
00:16:23.180 --> 00:16:23.320
Like,
00:16:23.560 --> 00:16:25.519
you know, I don't know how people know the term
00:16:25.540 --> 00:16:33.140
mashups but back with like web 2.0 i love it yeah it was like 2006 like we're you know we had this
00:16:33.400 --> 00:16:41.180
huge boom of the hdgp web 2.0 apis that were very you know fun to use like the flicker api and google
00:16:41.360 --> 00:16:45.820
maps and all that stuff and i was making like hundreds of mashups i was absolutely addicted
00:16:46.260 --> 00:16:50.560
um but it was it was so fun but like i was able to do that because i was you know i was a coder
00:16:50.920 --> 00:16:55.500
now the difference is you know obviously yes as coders we can make these mashups but we can
00:16:55.520 --> 00:16:58.380
enable anyone to make these mashups,
00:16:58.560 --> 00:17:01.180
right? Like we're putting the power of this,
00:17:01.340 --> 00:17:01.560
you know,
00:17:01.950 --> 00:17:05.579
this, this programmatic combinatorial power,
00:17:05.730 --> 00:17:07.120
we're giving it to everyone now.
00:17:07.390 --> 00:17:10.439
Yeah. For all the trouble that AI is causing trouble, I don't know,
00:17:10.600 --> 00:17:10.860
disruption,
00:17:11.689 --> 00:17:12.100
I guess,
00:17:12.260 --> 00:17:13.880
in our industry and others,
00:17:14.280 --> 00:17:16.980
you know, I do think there's something very special about being able
00:17:17.030 --> 00:17:22.060
to give people this power to speak in regular English or whatever language you speak to a
00:17:22.079 --> 00:17:24.100
computer and it's almost like programming.
00:17:24.500 --> 00:17:24.560
Yeah.
00:17:24.780 --> 00:17:26.699
Yeah. I mean, I think that's also just generally
00:17:26.959 --> 00:17:27.020
true,
00:17:27.560 --> 00:17:28.580
not just with MCP,
00:17:28.800 --> 00:17:29.000
but,
00:17:29.280 --> 00:17:32.480
you know, I gave a talk last week to CS teachers talking about,
00:17:32.620 --> 00:17:33.980
you know, the stack of programming languages.
00:17:34.240 --> 00:17:35.920
And we went up from, you know, assembly,
00:17:36.340 --> 00:17:36.400
machine,
00:17:36.840 --> 00:17:37.020
assembly,
00:17:38.340 --> 00:17:38.540
you know,
00:17:38.760 --> 00:17:39.160
C++,
00:17:39.500 --> 00:17:40.320
higher level like Python.
00:17:40.620 --> 00:17:40.960
And now,
00:17:41.360 --> 00:17:43.080
you know, we're at natural human language,
00:17:43.340 --> 00:17:49.620
right? Like we have lowered the barrier so that anyone spoken language can basically code something,
00:17:50.080 --> 00:17:50.140
Right.
00:17:50.440 --> 00:17:50.540
So,
00:17:51.080 --> 00:17:51.200
yeah.
00:17:51.500 --> 00:17:55.380
Yeah. My daughter just discovered Codex and she wanted to build a website.
00:17:55.670 --> 00:17:56.900
And after a few hours, she goes,
00:17:57.140 --> 00:17:58.780
Dad, is it OK if I stay up all night?
00:17:58.830 --> 00:17:59.640
I can't put this down.
00:17:59.860 --> 00:17:59.920
Like,
00:18:00.180 --> 00:18:01.980
you're going to run out of credits before you stay up all night.
00:18:02.030 --> 00:18:02.720
But don't do that.
00:18:03.960 --> 00:18:05.700
But that's kind of how the excitement is, you know.
00:18:06.540 --> 00:18:09.140
That reminds me of discovering the web like in like sixth grade.
00:18:09.210 --> 00:18:10.260
I definitely stayed up all.
00:18:10.430 --> 00:18:12.480
The first time you discover that you can make,
00:18:12.780 --> 00:18:15.020
you know, like a web app or a piece of software,
00:18:15.380 --> 00:18:16.040
it's a long night.
00:18:17.460 --> 00:18:18.200
It's an amazing night.
00:18:18.300 --> 00:18:19.180
But the next day, oh,
00:18:19.560 --> 00:18:20.320
boy, what have I done?
00:18:20.640 --> 00:18:21.160
What have I done?
00:18:21.560 --> 00:18:23.100
So make this a little bit concrete.
00:18:23.400 --> 00:18:27.120
Give us some specific MCP servers that you use.
00:18:27.820 --> 00:18:30.440
And I'll share a couple of mine as well, but I'm going to let you go first on this.
00:18:30.780 --> 00:18:31.040
Yeah.
00:18:31.220 --> 00:18:33.080
So the ones that I use the most often,
00:18:33.340 --> 00:18:36.540
there's the Twitter X MCP server.
00:18:37.380 --> 00:18:38.640
So I have that installed.
00:18:39.520 --> 00:18:44.980
And that, you know, can search through all the tweets, especially the tweets I've liked and bookmarked because I use that basically as like research,
00:18:45.260 --> 00:18:45.380
right?
00:18:45.600 --> 00:18:49.040
because I obviously am using Twitter purely for educational purposes
00:18:50.180 --> 00:18:51.840
and, you know, not just for procrastinating.
00:18:52.800 --> 00:18:54.460
So every week it actually like goes through and,
00:18:54.620 --> 00:18:55.320
you know, looks at stuff.
00:18:55.470 --> 00:18:58.420
And it also is like helps me like manage bookmarks,
00:18:58.680 --> 00:18:58.780
right?
00:18:58.900 --> 00:19:00.480
So I can put all my bookmarks in one place.
00:19:00.640 --> 00:19:02.140
So yeah, there's the XMCP server.
00:19:02.340 --> 00:19:03.760
I didn't know this existed.
00:19:04.160 --> 00:19:04.340
This is,
00:19:04.820 --> 00:19:06.220
this could be a problem if I learn about this.
00:19:06.660 --> 00:19:07.020
Yeah.
00:19:07.860 --> 00:19:08.220
Yeah,
00:19:08.420 --> 00:19:08.480
yeah.
00:19:08.960 --> 00:19:10.360
They've been improving it over time.
00:19:10.390 --> 00:19:12.180
You still, there's still a fair bit of setup for it.
00:19:12.260 --> 00:19:13.120
It's not the most,
00:19:13.700 --> 00:19:15.160
you know, most user friendly.
00:19:15.580 --> 00:19:24.640
um but uh you know it's it's working decently well uh let's say i also have the um a gmail mcp server
00:19:25.200 --> 00:19:29.640
which is not quite an official one but it's working well enough for now we're still waiting for it i
00:19:29.740 --> 00:19:33.560
think they're about to come out with this like google workspace mcp server so i'm excited for
00:19:33.620 --> 00:19:39.320
that oh that is exciting yeah yeah i basically my friend like vibed an unofficial this is the thing
00:19:39.380 --> 00:19:43.659
is you can make your own mcp servers that wrap things if you need it so right now i'm using like
00:19:43.680 --> 00:19:45.640
an official vibe Gmail MCP server.
00:19:46.640 --> 00:19:48.000
I use the WorkIQ MCP server.
00:19:48.060 --> 00:19:50.620
That gives me access to my work, Microsoft stuff,
00:19:50.740 --> 00:19:51.200
like Teams,
00:19:51.400 --> 00:19:51.740
Outlook,
00:19:52.700 --> 00:19:53.660
that sort of thing, Calendar.
00:19:54.860 --> 00:19:57.040
And yeah, and then I have some documentation servers.
00:19:57.160 --> 00:19:59.220
Like we have a documentation server just for Microsoft Learn,
00:19:59.340 --> 00:20:00.760
and that's where all of our documentation is.
00:20:01.380 --> 00:20:05.840
So I'm not even
using that many MCP servers,
00:20:07.220 --> 00:20:10.120
but the ones I am using are just absolutely essential,
00:20:10.340 --> 00:20:10.460
right?
00:20:10.560 --> 00:20:12.420
So like every week I hold an office hours
00:20:12.420 --> 00:20:15.060
where we talk about what's going on in generative AI.
00:20:15.530 --> 00:20:17.360
And I have a skill for that, an agent skill
00:20:17.520 --> 00:20:20.840
that specifically uses all those MCP servers to go to research.
00:20:21.080 --> 00:20:22.380
So it goes and looks through my Gmail,
00:20:22.600 --> 00:20:23.660
it looks through my Outlook,
00:20:23.690 --> 00:20:26.540
it looks through my Twitter history and says,
00:20:26.650 --> 00:20:28.500
okay, these are everything that's happened
00:20:28.860 --> 00:20:30.080
in the last seven days,
00:20:30.530 --> 00:20:30.660
right?
00:20:30.960 --> 00:20:33.820
And it can just do that every Tuesday at 9 a.m.,
00:20:34.020 --> 00:20:34.700
automatically run,
00:20:35.110 --> 00:20:35.700
and then boom,
00:20:35.900 --> 00:20:37.100
got my news roundup.
00:20:37.540 --> 00:20:40.120
And it's based off the last week
00:20:40.140 --> 00:20:43.280
of what I have been engaging with myself personally,
00:20:43.600 --> 00:20:43.700
right?
00:20:44.020 --> 00:20:44.140
Yeah,
00:20:44.360 --> 00:20:45.840
and for your role, it's really important
00:20:45.940 --> 00:20:47.260
to kind of stay on top of the news
00:20:47.440 --> 00:20:49.720
and what's happening in tech and all that, right?
00:20:49.940 --> 00:20:51.400
So being able to ask that as a question.
00:20:51.780 --> 00:20:51.980
Right,
00:20:52.160 --> 00:20:52.520
yeah, that's true.
00:20:52.560 --> 00:20:53.280
Like for every role,
00:20:53.440 --> 00:20:54.380
there's different MCP servers
00:20:54.580 --> 00:20:55.200
that are really shy.
00:20:55.280 --> 00:20:55.940
Like for other people,
00:20:56.180 --> 00:20:56.380
they're,
00:20:56.560 --> 00:20:56.680
you know,
00:20:56.780 --> 00:20:57.940
like the linear MCP server,
00:20:58.140 --> 00:20:59.140
they've had a huge,
00:20:59.260 --> 00:21:01.760
I think they get more traffic from MCP
00:21:02.100 --> 00:21:04.340
than via like their UI now or something.
00:21:04.460 --> 00:21:06.260
And they shared some chart where they're like,
00:21:06.600 --> 00:21:08.300
MCP usage is just, you know,
00:21:08.480 --> 00:21:10.000
shot way up, right?
00:21:10.080 --> 00:21:11.180
And that makes a ton of sense, right?
00:21:11.360 --> 00:21:14.020
Like if you're tracking all your issues in linear,
00:21:15.140 --> 00:21:16.540
you know, then you're going to have a lot of use.
00:21:17.060 --> 00:21:17.880
I also obviously use,
00:21:18.100 --> 00:21:18.520
I'm sorry,
00:21:18.540 --> 00:21:19.940
I didn't even think about the GitHub MSP server
00:21:20.100 --> 00:21:22.240
because it's like built in GoPilot,
00:21:22.440 --> 00:21:23.080
but you know that,
00:21:23.560 --> 00:21:23.660
you know,
00:21:23.680 --> 00:21:25.000
because my issues are stored
in GitHub.
00:21:25.660 --> 00:21:27.280
There's Azure DevOps that I'll use sometimes
00:21:27.580 --> 00:21:29.420
if I'm working on a project that is there.
00:21:29.640 --> 00:21:31.480
So depending on what your role is,
00:21:31.600 --> 00:21:32.580
you know, what your job is,
00:21:33.020 --> 00:21:34.540
you know, there's going to be different MSP servers
00:21:34.760 --> 00:21:36.580
that are going to like really enhance your productivity
00:21:37.080 --> 00:21:38.300
and other ones that you just don't need.
00:21:38.500 --> 00:21:38.660
Yeah,
00:21:38.940 --> 00:21:39.140
very cool.
00:21:39.520 --> 00:21:40.300
So for me,
00:21:40.560 --> 00:21:43.780
I make a lot of use of the Talk Python one
00:21:43.880 --> 00:21:45.140
because it lets me ask questions like,
00:21:45.220 --> 00:21:46.160
have we talked about this before?
00:21:46.420 --> 00:21:46.940
What have we covered?
00:21:47.300 --> 00:21:50.420
Is it going to be just a repeat or that kind of stuff really nicely?
00:21:51.300 --> 00:21:54.820
One, just to give a bit of an outside-of-the-box angle,
00:21:55.100 --> 00:21:56.400
is I found this place.
00:21:59.020 --> 00:21:59.420
Also,
00:21:59.740 --> 00:22:00.340
Century MCP.
00:22:00.680 --> 00:22:03.600
Century MCP is awesome because I have Century plugged into all my apps,
00:22:03.900 --> 00:22:07.320
and I love it for my web apps, but I'm a good web developer.
00:22:07.360 --> 00:22:08.520
I can do this, but you know what?
00:22:08.580 --> 00:22:10.620
I'm not a good developer of mobile apps.
00:22:10.900 --> 00:22:16.500
I'm barely hanging on to the edge to keep my mobile app going because I didn't write it.
00:22:16.530 --> 00:22:17.160
I don't know it.
00:22:17.220 --> 00:22:18.260
Like, it's just like, but okay,
00:22:18.560 --> 00:22:18.800
sort of.
00:22:19.080 --> 00:22:24.500
And I had Sentry connected to it for years and it just built up this huge backlog of errors.
00:22:25.000 --> 00:22:25.620
And I'm like, you know what?
00:22:25.860 --> 00:22:26.680
I'm tired of these errors.
00:22:27.040 --> 00:22:28.340
I think one week and I said,
00:22:28.500 --> 00:22:29.820
I bet Claude and I,
00:22:30.190 --> 00:22:32.060
given all that Sentry data with all the errors,
00:22:32.150 --> 00:22:34.220
I bet we can go fix almost all of them.
00:22:34.370 --> 00:22:38.260
And so I just connected the MCP server and I opened up VS Code with Flutter and I said,
00:22:38.360 --> 00:22:38.600
all right,
00:22:38.860 --> 00:22:39.040
Claude,
00:22:39.210 --> 00:22:39.980
I want you to look here.
00:22:40.280 --> 00:22:42.620
We're going to go there one at a time until these are gone.
00:22:43.400 --> 00:22:44.500
And it took three or four days,
00:22:44.740 --> 00:22:47.160
but I completely refreshed the app
00:22:47.500 --> 00:22:49.500
with all the details from the MCP server.
00:22:49.590 --> 00:22:50.980
And I would just say, okay, what's next?
00:22:51.150 --> 00:22:52.080
Yeah, go ahead and close that one.
00:22:52.160 --> 00:22:53.240
Let's make a GitHub issue for that.
00:22:53.340 --> 00:22:53.680
You know what I mean?
00:22:53.880 --> 00:22:54.140
And just,
00:22:54.600 --> 00:22:56.660
I kind of was just guiding it.
00:22:56.730 --> 00:22:57.580
And it completely,
00:22:57.800 --> 00:22:59.000
I think this is an amazing thing.
00:22:59.539 --> 00:23:01.960
These error-based systems that catch all the errors
00:23:02.010 --> 00:23:02.700
and you can just say,
00:23:03.040 --> 00:23:04.120
go to the Claude or Codex,
00:23:04.260 --> 00:23:04.320
go,
00:23:04.520 --> 00:23:05.860
there's an error in Sentry,
00:23:06.190 --> 00:23:06.440
fix it.
00:23:06.670 --> 00:23:07.060
You know what I mean?
00:23:07.160 --> 00:23:07.720
That's all it needs.
00:23:08.060 --> 00:23:08.280
Yeah,
00:23:08.540 --> 00:23:08.920
that's amazing.
00:23:09.060 --> 00:23:11.260
I can remember using Centurate Khan Academy
00:23:11.460 --> 00:23:13.520
and having those errors just build up over time.
00:23:13.550 --> 00:23:15.680
And you're like, one day, one day I'm going to fix them.
00:23:15.710 --> 00:23:18.820
But it is so hard to prioritize bugs
00:23:19.000 --> 00:23:19.960
when you're always like features.
00:23:20.140 --> 00:23:22.680
But now we can paralyze a bit more
00:23:23.140 --> 00:23:26.100
and you get the help of being able to sort through logs.
00:23:26.260 --> 00:23:27.620
At this point, I'm never going to look through
00:23:27.620 --> 00:23:28.620
an error traceback myself,
00:23:29.160 --> 00:23:30.240
especially with Python async.
00:23:30.290 --> 00:23:31.960
Man, Python async tangent.
00:23:32.200 --> 00:23:33.720
But Python async errors,
00:23:33.900 --> 00:23:34.920
the tracebacks
00:23:35.050 --> 00:23:37.540
are so hard to parse through, right?
00:23:37.940 --> 00:23:43.940
So these days I'm just always going to paste a trace back into an agent and be like, okay, what's the actual error here,
00:23:44.120 --> 00:23:44.180
right?
00:23:44.440 --> 00:23:44.500
Yeah.
00:23:44.900 --> 00:23:45.600
This is wrong.
00:23:46.760 --> 00:23:47.680
There's something wrong.
00:23:47.760 --> 00:23:48.520
I know this is wrong.
00:23:48.720 --> 00:23:49.620
We're fixing this,
00:23:49.800 --> 00:23:49.900
right?
00:23:50.160 --> 00:23:53.920
And then another one that I think we'll see if you would see this coming.
00:23:54.250 --> 00:23:55.240
So there's this place.
00:23:55.510 --> 00:23:57.480
So I was thinking about like retirement planning, right?
00:23:57.640 --> 00:23:59.340
Eventually I'm going to retire someday.
00:23:59.710 --> 00:24:02.460
And I'm like, I ran across this place called Bolden.
00:24:02.540 --> 00:24:03.320
It's not an advertisement.
00:24:03.480 --> 00:24:04.420
Just thought it was interesting.
00:24:04.820 --> 00:24:05.300
And it says,
00:24:05.500 --> 00:24:07.080
it's the DIY retirement.
00:24:07.380 --> 00:24:09.580
Like you can run any what if on their AI.
00:24:10.160 --> 00:24:16.180
If you put your sort of financial situation into it, you
can ask, like, if I put more in 401k now,
00:24:16.460 --> 00:24:16.880
will that save?
00:24:17.100 --> 00:24:19.260
You know, like what's this going to have an effect on, right?
00:24:19.340 --> 00:24:20.260
And if the market does this,
00:24:20.420 --> 00:24:20.940
what would that do?
00:24:20.980 --> 00:24:22.040
You know, like these kinds of things.
00:24:22.420 --> 00:24:25.300
And I asked it a question and I was like, I'll try this AI thing.
00:24:25.640 --> 00:24:26.420
So I asked it a question.
00:24:26.480 --> 00:24:27.960
It came back like that with an answer.
00:24:27.960 --> 00:24:28.340
I'm like, oh,
00:24:28.540 --> 00:24:29.660
no, I don't trust this at all.
00:24:29.960 --> 00:24:31.580
This should have taken a little bit of thinking.
00:24:31.760 --> 00:24:34.320
This is like a haiku model at best.
00:24:34.560 --> 00:24:34.940
You know what I mean?
00:24:35.120 --> 00:24:36.500
There's no way there's a good AI here.
00:24:36.860 --> 00:24:37.840
So I complained to them.
00:24:38.200 --> 00:24:41.240
And the developer wrote back and said, well, what if we build an MCP server?
00:24:41.320 --> 00:24:41.640
I said,
00:24:41.800 --> 00:24:41.960
yes.
00:24:42.340 --> 00:24:44.320
And then a few weeks later, like, here's the MCP server.
00:24:44.720 --> 00:24:48.260
So I connected it to Claude on like Fable or Opus or something.
00:24:48.440 --> 00:24:49.300
And then I'm like, okay,
00:24:49.520 --> 00:24:51.760
now I can ask questions I trust the answers to.
00:24:52.160 --> 00:24:52.920
Yeah, that's a good point.
00:24:53.020 --> 00:24:53.700
Because when you,
00:24:54.200 --> 00:24:54.840
right, that's a good point.
00:24:54.920 --> 00:24:57.300
Because a lot of these applications have,
00:24:57.540 --> 00:24:58.520
you know, this has like an agent.
00:24:58.640 --> 00:24:59.500
You can see it on this,
00:24:59.680 --> 00:25:00.920
the front web page.
00:25:00.920 --> 00:25:02.320
It says like AI planner assistant.
00:25:02.640 --> 00:25:06.800
But they need to optimize for cost, so they're not necessarily going to use the most expensive model there.
00:25:06.870 --> 00:25:08.720
They may not have access to the best model.
00:25:09.060 --> 00:25:10.420
You might,
00:25:10.620 --> 00:25:12.160
for whatever reason, you've got Fable.
00:25:12.390 --> 00:25:14.720
I don't even have Fable, but I've got Opus 5.5,
00:25:14.960 --> 00:25:15.960
which is my new bestie, right?
00:25:16.420 --> 00:25:17.220
I love 5.5.
00:25:17.270 --> 00:25:18.240
Yeah, I love Opus 5.5.
00:25:18.400 --> 00:25:19.020
It's so good.
00:25:19.220 --> 00:25:20.140
So I can.55,
00:25:20.920 --> 00:25:23.840
and I can trust that.
00:25:24.780 --> 00:25:28.500
And we should be using the EPSP server for the data.
00:25:29.240 --> 00:25:32.580
There are some MSP servers that do also basically wrap an agent.
00:25:32.970 --> 00:25:35.240
I don't love that as a design choice,
00:25:35.720 --> 00:25:40.320
but it is certainly a choice that some MSP servers are using.
00:25:41.540 --> 00:25:44.460
But yeah, I'd rather that they focus on returning the data
00:25:44.760 --> 00:25:47.360
and leave the agentic processing to people's agents.
00:25:47.820 --> 00:25:47.940
Right.
00:25:48.840 --> 00:25:51.880
Your job is to get the data to the smart agent that I'm running,
00:25:51.980 --> 00:25:53.420
not do your own thing on top of it.
00:25:53.450 --> 00:25:53.580
Exactly.
00:25:54.680 --> 00:25:56.480
I want to throw one more thing out there really quick,
00:25:56.490 --> 00:25:59.040
and maybe you can give us your thoughts if you have any.
00:25:59.300 --> 00:26:03.260
I know a lot of people when they think about AI and their website or their app,
00:26:03.420 --> 00:26:05.680
they're like, here's a thing that is swamping my app.
00:26:05.860 --> 00:26:06.780
It's making it slow.
00:26:07.040 --> 00:26:08.000
It's overwhelming the bandwidth.
00:26:08.200 --> 00:26:08.820
And I hate it.
00:26:09.120 --> 00:26:10.760
So MCP probably just makes this worse.
00:26:11.700 --> 00:26:12.940
I don't think that's true.
00:26:13.200 --> 00:26:16.040
I think that a lot of people might have this sort of thought process,
00:26:16.220 --> 00:26:16.340
right?
00:26:16.500 --> 00:26:19.780
Like it's just going to mean it's going to talk to my site more and so on.
00:26:20.060 --> 00:26:22.360
But when you build these MCP tools,
00:26:22.520 --> 00:26:24.340
as you pointed out, you build the tools.
00:26:24.540 --> 00:26:26.820
Those are basically function calls on your code.
00:26:27.160 --> 00:26:28.880
And you can do whatever you want there.
00:26:29.020 --> 00:26:29.760
You can use caching.
00:26:30.030 --> 00:26:31.460
You can use database indexes.
00:26:31.530 --> 00:26:32.840
You can make them incredibly fast.
00:26:33.150 --> 00:26:35.560
So instead of having an AI crawl all over your stuff,
00:26:35.980 --> 00:26:38.000
it can just go right to an optimized spot and go,
00:26:38.380 --> 00:26:39.360
this is what I'm actually looking for.
00:26:39.520 --> 00:26:41.600
All right, here's a super fast response.
00:26:42.540 --> 00:26:43.780
Harkening back to the PyCon,
00:26:44.040 --> 00:26:44.480
PyBay talk.
00:26:44.760 --> 00:26:48.560
Pulled up my logs in the last couple of MCP calls on my site
00:26:48.570 --> 00:26:50.020
were like two millisecond response time.
00:26:50.320 --> 00:26:51.160
That doesn't hurt my site.
00:26:51.250 --> 00:26:51.680
I don't care.
00:26:51.970 --> 00:26:53.240
They can ask questions like that.
00:26:53.600 --> 00:26:57.120
This is the way to, I think, lessen the work on your server
00:26:57.260 --> 00:26:58.420
and your app, not increase it.
00:26:58.640 --> 00:26:58.720
Yeah,
00:26:58.900 --> 00:26:59.400
that's really true.
00:26:59.620 --> 00:27:04.600
I think at this point, we should assume that people are going to use agents to try to automate
00:27:05.419 --> 00:27:07.260
interaction with the websites they're using,
00:27:07.740 --> 00:27:07.840
right?
00:27:07.960 --> 00:27:08.520
So for example,
00:27:08.680 --> 00:27:12.940
I was trying to programmatically browse Etsy the other day to help with my
00:27:13.180 --> 00:27:18.200
costume shopping because I wanted to be Link from Zelda and I needed to put together lots
00:27:18.240 --> 00:27:18.800
of different parts.
00:27:19.680 --> 00:27:20.900
And I actually have never played Zelda.
00:27:21.320 --> 00:27:21.840
So I was like,
00:27:22.360 --> 00:27:25.620
assuming the coding agent knows more about Link than I do,
00:27:25.820 --> 00:27:27.220
you know, because
00:27:27.320 --> 00:27:27.900
it's in the weights.
00:27:28.300 --> 00:27:29.220
It's not in my weights,
00:27:29.480 --> 00:27:29.580
right?
00:27:29.960 --> 00:27:32.000
But I was immediately blocked from Etsy.
00:27:32.260 --> 00:27:35.900
And Etsy does not have like a shopping MCP server.
00:27:36.280 --> 00:27:38.660
So if they'd had an MCP server,
00:27:38.900 --> 00:27:41.960
then I would have bought a lot more on Etsy.
00:27:41.960 --> 00:27:42.860
Yeah, isn't that surprising?
00:27:43.100 --> 00:27:44.780
They're like, no, it's going to block it.
00:27:44.840 --> 00:27:45.240
These are terrible.
00:27:45.400 --> 00:27:45.460
Like,
00:27:45.680 --> 00:27:47.820
I was trying to buy five different things for an outfit.
00:27:48.020 --> 00:27:48.620
You wouldn't let me,
00:27:48.920 --> 00:27:49.020
basically.
00:27:49.040 --> 00:27:49.900
Right, because if you, yeah.
00:27:50.000 --> 00:27:52.020
So it certainly does depend on what people.
00:27:52.040 --> 00:27:53.460
So because on the flip side,
00:27:53.840 --> 00:27:57.019
you know, when people use MCP servers to automate interaction
00:27:57.040 --> 00:27:58.820
with like a social media network or,
00:27:59.220 --> 00:27:59.660
you know, like,
00:28:00.140 --> 00:28:02.240
you know, like a website where people are
00:28:02.500 --> 00:28:04.140
posting text,
00:28:04.540 --> 00:28:05.680
they can make a worse experience,
00:28:05.880 --> 00:28:07.840
right? We see this on Twitter right now with all
00:28:07.960 --> 00:28:08.900
the reply bots.
00:28:09.720 --> 00:28:09.840
You know,
00:28:10.000 --> 00:28:10.180
they're,
00:28:10.360 --> 00:28:10.620
they're,
00:28:11.020 --> 00:28:11.980
it's a horrible experience.
00:28:12.200 --> 00:28:13.540
Like everything you tweet,
00:28:13.980 --> 00:28:17.160
you get back this reply that's very well written and says it's not X, but Y.
00:28:17.400 --> 00:28:17.660
And you're like,
00:28:17.800 --> 00:28:17.940
oh,
00:28:18.200 --> 00:28:18.340
why?
00:28:18.520 --> 00:28:18.980
Why did you,
00:28:19.560 --> 00:28:19.720
you know,
00:28:20.200 --> 00:28:23.379
like fill my brain with something that I should never have to read
00:28:23.400 --> 00:28:23.620
because,
00:28:24.180 --> 00:28:25.940
you know, there's no human out there that wrote it.
00:28:26.140 --> 00:28:26.200
Right.
00:28:26.640 --> 00:28:26.720
So,
00:28:27.000 --> 00:28:27.340
you know, there,
00:28:27.670 --> 00:28:27.880
you know,
00:28:27.970
--> 00:28:30.980
there, there's some design that goes into this,
00:28:31.140 --> 00:28:33.840
but there's definitely many services where if you
00:28:34.070 --> 00:28:34.900
build an MSP server,
00:28:35.310 --> 00:28:38.880
you are enabling people to use your app in,
00:28:39.600 --> 00:28:40.440
in more ways, right? So,
00:28:40.640 --> 00:28:41.220
especially for shopping,
00:28:41.420 --> 00:28:44.680
right? So DoorDash, they did add an MSP server and that makes so much
00:28:44.800 --> 00:28:45.100
sense, right?
00:28:45.260 --> 00:28:45.920
For people who's doing,
00:28:46.080 --> 00:28:48.060
you know, maybe they use DoorDash to cater to their office
00:28:48.190 --> 00:28:48.760
every single day.
00:28:49.300 --> 00:28:50.440
By having an MSP server,
00:28:50.700 --> 00:28:53.360
DoorDash is making it that much easier to do bulk orders
00:28:53.380 --> 00:28:54.060
on DoorDash,
00:28:54.220 --> 00:28:54.340
right?
00:28:54.650 --> 00:28:55.940
So if you are a shopping website,
00:28:56.630 --> 00:28:57.880
I think Shopify just announced
00:28:58.030 --> 00:28:59.900
like an MCP sort of integration.
00:29:00.160 --> 00:29:01.600
So if you are a shopping website,
00:29:01.770 --> 00:29:03.100
it makes so much sense
00:29:03.500 --> 00:29:04.320
to have an MCP server,
00:29:04.520 --> 00:29:04.580
right?
00:29:04.630 --> 00:29:05.340
Because you want that,
00:29:05.570 --> 00:29:05.940
you know, sweet,
00:29:06.100 --> 00:29:06.880
sweet consumerism,
00:29:07.140 --> 00:29:07.260
right?
00:29:07.660 --> 00:29:07.880
Exactly.
00:29:08.220 --> 00:29:09.100
Let them come purchase.
00:29:09.270 --> 00:29:10.040
Let their agents come.
00:29:10.480 --> 00:29:11.360
They'll put their credit card in.
00:29:11.580 --> 00:29:12.680
I guess the thing that it threatens
00:29:12.770 --> 00:29:13.740
the most is advertising,
00:29:13.960 --> 00:29:14.040
right?
00:29:14.100 --> 00:29:15.200
And that's always what's been threatened
00:29:15.720 --> 00:29:16.080
by,
00:29:16.530 --> 00:29:17.140
you know, ad block
00:29:17.250 --> 00:29:18.120
and programmatic scraping
00:29:18.280 --> 00:29:19.000
and all that stuff.
00:29:19.220 --> 00:29:20.320
So we'll have to figure that out.
00:29:20.620 --> 00:29:20.760
Yeah,
00:29:21.000 --> 00:29:22.020
that is a different,
00:29:22.110 --> 00:29:23.340
I think that is an absolutely
00:29:23.500 --> 00:29:27.160
significant area and totally different though than like etsy letting you buy or not buy
00:29:27.500 --> 00:29:32.120
so you gave a talk exploring mcp servers with GitHub copilot was this last year
00:29:32.580 --> 00:29:37.720
um this particular one was quite uh recent but basically like i keep doing these workshops to
00:29:37.860 --> 00:29:43.060
show people mcp uh the first one i gave was at pycon so that was you know pycon back down in long
00:29:43.220 --> 00:29:46.820
beach and that was you know like a three-hour workshop and so i've just been giving variants
00:29:47.160 --> 00:29:53.320
on this workshop for the last whatever seven months i think this might have been pi ai is that right
00:29:53.340 --> 00:29:58.720
remember uh maybe not no no no that was your um that was your one where you made an mcp server
00:29:58.850 --> 00:30:03.060
pick your outfit that was a different deal yeah you know i just talk about mcp everywhere so this
00:30:03.060 --> 00:30:08.220
was at we are developers in san jose a few weeks ago gotcha okay the reason is i want to talk about
00:30:08.360 --> 00:30:15.580
just like support for mcp servers across some of your common things like copilot codex code vs code
00:30:15.860 --> 00:30:21.380
etc it's like a can i use but can i use dot ai instead of an air.com whatever it is i know i don't
00:30:21.340 --> 00:30:25.060
even think don't please don't go there i don't know what's there but no the actual website is
00:30:25.160 --> 00:30:30.320
can i use.dev uh i told them they should get canimcp.com because i thought that would you know
00:30:30.550 --> 00:30:35.940
flow better but this is from so the people who made this is mcp jam it's this really nice uh
00:30:36.160 --> 00:30:40.620
basically like think of it as postman but for mcp servers right so really nice way of just testing
00:30:40.800 --> 00:30:44.520
out your mcp servers with all the different features and you know sending requests back and
00:30:44.650 --> 00:30:49.700
forth and being able to see your oaf flow and see it succeed so they decided to make this can i use.dev
00:30:49.980 --> 00:30:52.240
And it's supposed to be like caniuse.com,
00:30:52.640 --> 00:30:53.460
but for MSP servers,
00:30:53.820 --> 00:30:55.560
because people are always asking like, hey,
00:30:55.820 --> 00:30:56.980
you know, this new MSP feature,
00:30:57.500 --> 00:30:58.500
is it supporting these clients?
00:30:58.640 --> 00:31:00.720
Because this MSP spec is evolving all the time.
00:31:00.760 --> 00:31:04.840
They did the most recent big drop was July 28th, continually adding,
00:31:05.200 --> 00:31:06.880
you know, more stuff to it over time.
00:31:07.760 --> 00:31:12.020
But the problem is many clients don't necessarily immediately add support for these features.
00:31:12.180 --> 00:31:12.640
So as somebody,
00:31:12.960 --> 00:31:14.040
if you're building a server,
00:31:14.680 --> 00:31:14.800
you know,
00:31:14.980 --> 00:31:16.520
you might be really excited about a new feature,
00:31:17.040 --> 00:31:18.420
but you want to check and see like, hey,
00:31:18.940 --> 00:31:19.140
you know,
00:31:19.620 --> 00:31:21.340
what is the support like that,
00:31:21.600 --> 00:31:21.720
you know,
00:31:22.160 --> 00:31:23.680
for this feature across the clients?
00:31:23.800 --> 00:31:25.800
What is the user experience going to be like?
00:31:26.080 --> 00:31:26.260
Yeah.
00:31:26.320 --> 00:31:27.960
And just doesn't support it at all.
00:31:28.360 --> 00:31:28.500
You know,
00:31:28.660 --> 00:31:29.480
I know for a while,
00:31:29.780 --> 00:31:30.480
like ChatGPT,
00:31:30.840 --> 00:31:34.760
Codex supported, but I think ChatGPT wouldn't take MCP or something.
00:31:35.780 --> 00:31:36.680
Why won't you accept it?
00:31:36.740 --> 00:31:38.020
You're the most popular thing.
00:31:38.720 --> 00:31:39.160
You know what I mean?
00:31:39.200 --> 00:31:41.120
I think MCP came out of Anthropic.
00:31:41.220 --> 00:31:41.980
I can't remember exactly.
00:31:42.060 --> 00:31:47.380
But actually Codex has more support than log code, for example.
00:31:47.530 --> 00:31:49.700
So this is kind of a can I use for all the different features.
00:31:51.100 --> 00:31:51.180
Yeah,
00:31:51.340 --> 00:31:51.780
and I actually,
00:31:52.160 --> 00:31:53.140
relevant to this audience,
00:31:53.370 --> 00:31:57.920
I just asked them if they will add columns for Python agent frameworks,
00:31:58.220 --> 00:31:58.360
right?
00:31:58.540 --> 00:31:58.660
Because,
00:31:58.930 --> 00:32:00.420
for example, skills over MCP,
00:32:00.640 --> 00:32:02.480
that just got approved like a month ago.
00:32:02.930 --> 00:32:05.300
Like the spec for it got approved in merge.
00:32:05.330 --> 00:32:06.060
And so now they're,
00:32:06.220 --> 00:32:06.400
you know,
00:32:06.580 --> 00:32:07.180
making it official.
00:32:07.760 --> 00:32:14.700
And if you look for skills on can I use.dev right now, you'll see none of the current clients support it,
00:32:14.920 --> 00:32:17.200
but it is supported in a lot of the agent frameworks.
00:32:17.500 --> 00:32:22.360
So if you use like we've got like Microsoft agent framework, I happen to just know that that one supports it.
00:32:22.360 --> 00:32:23.700
But I bet you Pydantic AI does,
00:32:23.940 --> 00:32:26.100
too, because they're always quick to pick these things up.
00:32:26.220 --> 00:32:26.320
Right.
00:32:26.500 --> 00:32:30.860
So I did ask them to add columns for the agent framework.
00:32:30.980 --> 00:32:32.240
So hopefully in the near future,
00:32:32.480 --> 00:32:33.100
you'll see like,
00:32:33.860 --> 00:32:34.000
you know,
00:32:34.160 --> 00:32:35.300
does Pydantic AI,
00:32:35.720 --> 00:32:36.580
LangChain, right?
00:32:37.000 --> 00:32:39.700
You know, which of your favorite Python agent framework support it?
00:32:39.700 --> 00:32:41.420
Because that's the thing is like there's both,
00:32:42.040 --> 00:32:43.360
you know, using MCP from,
00:32:44.000 --> 00:32:45.740
you know, almost say like a user facing tool.
00:32:45.920 --> 00:32:50.380
Because in some ways, like GitHub Copilot is it's like a kind of a user facing tool, even if the users are developers.
00:32:51.880 --> 00:32:57.720
Versus using MCP as the integration layer for agents that you're writing in Python.
00:32:57.820 --> 00:33:02.260
And that's actually where we see a huge amount of uses of MCP,
00:33:02.510 --> 00:33:02.640
right?
00:33:02.710 --> 00:33:04.820
Because there's always this debate about MCP versus CLI.
00:33:05.110 --> 00:33:05.340
And yeah,
00:33:05.580 --> 00:33:07.480
locally, you can do whatever the heck you want,
00:33:07.660 --> 00:33:08.340
whatever works for you.
00:33:09.420 --> 00:33:19.700
But when it comes to putting agents into production and having them do communication with other servers when they're actually deployed to the cloud,
00:33:19.880 --> 00:33:21.320
everyone's using MCP there,
00:33:21.680 --> 00:33:21.800
right?
00:33:21.880 --> 00:33:24.360
Like for enterprise agent interconnectedness,
00:33:24.560 --> 00:33:25.580
it's all MCP.
00:33:25.820 --> 00:33:34.600
So what I tend to care most about is actually like, hey, can I write a Python agent framework that integrates with a Python agent that integrates with this MCP server?
00:33:34.820 --> 00:33:36.120
And is it going to work as expected?
00:33:36.460 --> 00:33:39.420
So people are excited about MCP probably like, oh,
00:33:39.580 --> 00:33:42.920
we're going to add this MCP thing to our topic.
00:33:43.140 --> 00:33:44.420
But I think a good question.
00:33:44.780 --> 00:33:45.280
And this one,
00:33:45.620 --> 00:33:48.840
everything we talk about, we've got to give it a little bit of a caveat of like, well,
00:33:49.180 --> 00:33:53.040
was it like last century effectively for this technology like last year?
00:33:53.600 --> 00:33:57.620
But you wrote about to MCP or not to MCP, you know,
00:33:57.780 --> 00:33:58.540
my weird joke.
00:33:58.700 --> 00:34:02.660
But there are reasons to not use it or not completely just leave it wide open,
00:34:02.900 --> 00:34:06.540
like create maybe more focus tools and then give those to your AI or to you.
00:34:06.780 --> 00:34:07.000
Yeah.
00:34:07.340 --> 00:34:08.139
Yeah. And so here,
00:34:08.720 --> 00:34:11.419
this was an example for this was Playwright,
00:34:11.679 --> 00:34:11.800
right?
00:34:12.560 --> 00:34:18.440
So Playwright is a browser automation library and there's a Python package for it.
00:34:18.560 --> 00:34:19.440
It's fantastic.
00:34:20.320 --> 00:34:25.260
And I was already using Playwright quite heavily to write my end-to-end tests for web apps, right?
00:34:25.440 --> 00:34:26.100
And so you could actually,
00:34:26.260 --> 00:34:28.080
and there's a pytest-Playwright plugin.
00:34:28.659 --> 00:34:29.700
So it's very easy to,
00:34:29.899 --> 00:34:32.720
you know, write these end-to-end tests with Playwright.
00:34:32.840 --> 00:34:36.820
And they'll, like, automatically open a headless Chromium browser or Firefox browser.
00:34:36.879 --> 00:34:37.639
And they'll click around.
00:34:37.740 --> 00:34:38.300
They'll do something.
00:34:38.379 --> 00:34:39.600
And they'll verify it all works,
00:34:39.800 --> 00:34:39.899
right?
00:34:40.639 --> 00:34:43.820
Now, Playwright was one of the first MCP servers that came out.
00:34:44.560 --> 00:34:48.300
And people loved it because suddenly people discovered browser animation.
00:34:48.520 --> 00:34:49.860
Like a lot of people, I think, had never,
00:34:50.460 --> 00:34:53.280
never knew that you could like programmatically control a
browser.
00:34:53.429 --> 00:34:54.639
And so the Playwright MCP,
00:34:54.800 --> 00:34:54.919
like,
00:34:55.179 --> 00:35:00.720
you know, it lowered the barrier for that where people were just like adding Playwright MCP server to their coding agents and,
00:35:01.020 --> 00:35:01.940
you know, having fun,
00:35:02.200 --> 00:35:02.480
you know,
00:35:02.760 --> 00:35:04.260
automatically shopping and all that stuff.
00:35:05.260 --> 00:35:05.620
So,
00:35:06.040 --> 00:35:07.700
you know, so I that that was, you know,
00:35:08.140 --> 00:35:10.720
one of the first big servers that you would hear a lot about.
00:35:11.240 --> 00:35:18.240
So I wanted to make an agent that would automatically triage my LinkedIn request to connect.
00:35:18.640 --> 00:35:19.780
So you go to a conference,
00:35:20.040 --> 00:35:22.460
you go back and you see your LinkedIn and all these people
00:35:22.540 --> 00:35:24.780
want to connect and they're all great people.
00:35:25.240 --> 00:35:27.060
But I find it like really boring to accept,
00:35:27.400 --> 00:35:27.520
accept.
00:35:27.900 --> 00:35:29.440
And every now and then it's careful,
00:35:29.660 --> 00:35:31.480
only connect with people you actually know.
00:35:31.580 --> 00:35:31.940
It's like, nope,
00:35:32.220 --> 00:35:32.960
accept, accept, accept.
00:35:33.640 --> 00:35:35.120
What am I going to be rude and tell them no?
00:35:35.300 --> 00:35:35.980
I don't know.
00:35:36.500 --> 00:35:36.580
Well,
00:35:36.760 --> 00:35:40.500
every so often you get kind of like a life coach in there.
00:35:41.180 --> 00:35:41.540
Yes.
00:35:41.900 --> 00:35:42.140
No,
00:35:42.290 --> 00:35:43.360
you do want to, yeah,
00:35:43.880 --> 00:35:45.360
like a recruiter.
00:35:45.930 --> 00:35:46.400
A recruiter.
00:35:46.560 --> 00:35:46.840
Yes,
00:35:47.140 --> 00:35:47.400
exactly.
00:35:47.740 --> 00:35:49.320
A book publisher,
00:35:49.580 --> 00:35:51.060
like, hey, would you like to write a book on this?
00:35:51.120 --> 00:35:53.340
No, if I want to write a book on it, we've already written a book on it.
00:35:54.340 --> 00:35:57.380
Yeah, I have this fantasy that one day I'll write a book,
00:35:57.720 --> 00:35:58.340
so I accept those.
00:35:59.339 --> 00:36:01.400
But yeah, so I wanted to automate that.
00:36:01.640 --> 00:36:06.480
So my first experiment was doing a pedantic AI agent with the player and MCP server.
00:36:07.220 --> 00:36:12.360
And it was like incredibly inefficient because it would like go to the LinkedIn page.
00:36:12.450 --> 00:36:13.480
It would kind of click around,
00:36:13.720 --> 00:36:14.740
try to figure out what to do.
00:36:14.940 --> 00:36:18.720
Like it was like continually reading lots and lots of tokens because it wasn't sure exactly what to do.
00:36:19.220 --> 00:36:20.700
And it did like eventually succeed.
00:36:21.799 --> 00:36:25.680
But it wasn't a good experience because one, I had like a limited token budget at that time.
00:36:26.290 --> 00:36:29.180
And two, it was just like taking a really long time and it was sometimes working,
00:36:29.350 --> 00:36:29.760
sometimes not.
00:36:29.790 --> 00:36:30.440
And I was like, well,
00:36:30.820 --> 00:36:31.160
you know what?
00:36:31.460 --> 00:36:34.040
I'm trying to do the tasks, the same task every single time,
00:36:34.210 --> 00:36:34.900
every single day.
00:36:35.200 --> 00:36:38.300
why don't I just script this using the Python Playwright SDK,
00:36:38.880 --> 00:36:39.020
right?
00:36:39.440 --> 00:36:39.980
So I just,
00:36:40.260 --> 00:36:40.740
you know, I then,
00:36:41.080 --> 00:36:42.880
you know, scripted it using SDK.
00:36:43.900 --> 00:36:45.460
You know, at that point, I hand wrote it myself.
00:36:45.780 --> 00:36:48.460
These days, I just have Copilot open up the browser and figure it out.
00:36:49.260 --> 00:36:49.600
But then,
00:36:49.920 --> 00:36:51.620
so then it becomes like much more deterministic.
00:36:51.710 --> 00:36:54.080
And I only brought the LLM in to make the decision,
00:36:54.340 --> 00:36:54.420
right?
00:36:54.450 --> 00:36:58.360
So I have like the Python Playwright SDK code is like opening my LinkedIn,
00:36:59.120 --> 00:37:02.220
restoring my auth cookies so that I'm like logged in and that had this browser.
00:37:02.630 --> 00:37:03.160
And then,
00:37:03.320 --> 00:37:03.900
you know, logging in,
00:37:04.160 --> 00:37:04.780
checking the requests.
00:37:04.860 --> 00:37:09.700
it gets a request. Okay. Then that's when it sends the information to an LLM only then. And it uses
00:37:09.940 --> 00:37:11.640
structured outputs and says, Hey, LLM,
00:37:11.960 --> 00:37:13.700
send me back some Jason that says,
00:37:13.940 --> 00:37:14.160
you know,
00:37:14.320 --> 00:37:14.680
accept,
00:37:14.940 --> 00:37:15.040
ignore,
00:37:15.300 --> 00:37:19.520
reject or undecided and give me the reason for it. Right. And I gave it a prompt that said,
00:37:19.660 --> 00:37:20.420
if it's a recruiter,
00:37:20.880 --> 00:37:23.160
a life coach or a financial consultant,
00:37:23.700 --> 00:37:23.800
uh,
00:37:24.220 --> 00:37:24.340
uh,
00:37:24.540 --> 00:37:25.540
that's basically the ignore,
00:37:26.020 --> 00:37:26.420
ignore.
00:37:26.700 --> 00:37:26.780
Yeah.
00:37:27.380 --> 00:37:27.500
Um,
00:37:27.940 --> 00:37:28.720
you know, it's very effective.
00:37:29.280 --> 00:37:29.340
So,
00:37:29.920 --> 00:37:30.580
right. So that was,
00:37:30.740 --> 00:37:31.100
you know, that's,
00:37:31.280 --> 00:37:31.620
that's,
00:37:31.700 --> 00:37:38.360
you know that's something considered right like the re like mcp enables these uh you know you to
00:37:38.660 --> 00:37:46.200
create new mashups new permutations combinations new workflows um that you know you didn't already
00:37:46.340 --> 00:37:51.760
have in your head so it makes a lot of sense if you are deploying any sort of agent that has more
00:37:51.880 --> 00:37:57.440
open-ended tasks or that like a user is ultimately going to be used in order to
do their uh you know
00:37:57.320 --> 00:37:58.660
their end tasks, right?
00:37:58.750 --> 00:38:00.760
So if there's any sort of open-endedness
00:38:01.420 --> 00:38:02.600
where it may have to do iteration
00:38:02.850 --> 00:38:03.920
and or shouldn't decide,
00:38:04.070 --> 00:38:04.240
you know,
00:38:04.270 --> 00:38:05.020
what it's going to do next,
00:38:05.680 --> 00:38:07.260
then an MSP server makes sense.
00:38:07.680 --> 00:38:09.240
But if you're doing the same thing
00:38:09.620 --> 00:38:10.400
every single time,
00:38:10.730 --> 00:38:11.520
and there's, you know,
00:38:11.630 --> 00:38:12.040
even like,
00:38:12.260 --> 00:38:12.420
you know,
00:38:12.560 --> 00:38:13.360
in the case of mine,
00:38:13.360 --> 00:38:14.240
where it's like all you're doing
00:38:14.270 --> 00:38:15.500
is tracing network requests,
00:38:16.000 --> 00:38:17.360
it's just not necessary
00:38:17.720 --> 00:38:18.440
to use MSP server
00:38:18.610 --> 00:38:20.680
and it can add more non-determinism
00:38:21.080 --> 00:38:21.740
to a workflow.
00:38:22.140 --> 00:38:22.860
Yeah, and if you're worried
00:38:22.980 --> 00:38:23.780
about it going crazy
00:38:24.020 --> 00:38:25.700
and just instead of connecting,
00:38:25.920 --> 00:38:26.120
Oh,
00:38:26.600 --> 00:38:27.620
she wants to connect with people.
00:38:27.800 --> 00:38:30.220
Let me find everyone on LinkedIn and add them as a connection.
00:38:30.440 --> 00:38:30.700
You know what I mean?
00:38:30.800 --> 00:38:31.660
Like something like that.
00:38:31.870 --> 00:38:33.300
You could think, oh, the AI went crazy.
00:38:33.680 --> 00:38:37.700
What you've given it is a much more constrained and deterministic deal, right?
00:38:37.960 --> 00:38:39.340
Like it can only look at yes,
00:38:39.500 --> 00:38:39.620
no.
00:38:40.100 --> 00:38:40.280
I mean,
00:38:40.640 --> 00:38:42.520
today almost would be a Jev sort of thing.
00:38:42.780 --> 00:38:45.100
Yeah, I could totally sub in a Jev model point,
00:38:45.260 --> 00:38:45.360
right?
00:38:45.500 --> 00:38:48.100
Like it would be a good scenario for a Jev model.
00:38:48.280 --> 00:38:48.500
Generally,
00:38:48.740 --> 00:38:49.640
like that's a whole other discussion.
00:38:49.750 --> 00:38:50.080
But yeah,
00:38:50.260 --> 00:38:53.700
generally, if anywhere we're using structured outputs where the result is a Boolean
00:38:53.720 --> 00:38:54.220
or a choice,
00:38:54.620 --> 00:38:55.960
you can go ahead and sub in
00:38:56.260 --> 00:38:56.740
JAP model,
00:38:56.980 --> 00:38:57.560
decisions API,
00:38:58.380 --> 00:38:59.880
Microsoft, we just launched decision one,
00:39:00.960 --> 00:39:02.420
you know, a decision model.
00:39:02.820 --> 00:39:05.380
And yeah, so then you don't even need a full LLM.
00:39:05.500 --> 00:39:05.760
Yeah,
00:39:06.020 --> 00:39:06.140
exactly.
00:39:06.620 --> 00:39:08.640
But I do think a lot of times just giving an LLM
00:39:08.780 --> 00:39:10.380
a chance to like, I got it close,
00:39:10.840 --> 00:39:11.740
but let's go there.
00:39:11.860 --> 00:39:14.240
I'll give you an example from my world
00:39:14.360 --> 00:39:15.540
that I found really helpful
00:39:16.020 --> 00:39:18.640
is I have Hermes chilling on my Mac mini
00:39:18.840 --> 00:39:20.160
just doing a bunch of stuff
00:39:20.600 --> 00:39:22.680
and two YouTube channels
00:39:22.700 --> 00:39:25.520
and they really are just sort of replications of the podcast.
00:39:25.880 --> 00:39:27.360
So like the description is,
00:39:27.700 --> 00:39:28.460
it's a structured thing,
00:39:28.540 --> 00:39:30.860
but it comes from a whole bunch of different pieces of data
00:39:31.020 --> 00:39:32.240
out of the podcast and so on.
00:39:32.580 --> 00:39:34.360
But especially when I was live streaming more,
00:39:34.740 --> 00:39:36.380
it would be the stuff will go up.
00:39:36.560 --> 00:39:38.360
And then eventually when the results,
00:39:38.680 --> 00:39:40.240
like all the details of the episode are together,
00:39:40.280 --> 00:39:41.920
I got to go find all of that, the transcript,
00:39:42.240 --> 00:39:42.700
the description,
00:39:42.880 --> 00:39:43.460
the guest, the links,
00:39:43.560 --> 00:39:44.680
and then go and put them back.
00:39:45.060 --> 00:39:46.060
And I just sort of,
00:39:46.540 --> 00:39:47.520
I don't know, I lost track of that.
00:39:47.760 --> 00:39:50.900
And I had like two or 300 videos on each channel
00:39:50.920 --> 00:39:52.500
that were just episode seven,
00:39:53.100 --> 00:39:53.800
episode 200.
00:39:53.960 --> 00:39:54.260
You know what I mean?
00:39:54.360 --> 00:39:54.880
Like, oh no,
00:39:55.240 --> 00:39:57.700
I can't, I cannot navigate the YouTube studio.
00:39:57.980 --> 00:40:00.120
It's so slow on every little step.
00:40:00.140 --> 00:40:02.880
I can't go and do like 400 edits of this.
00:40:03.140 --> 00:40:05.060
And so I wanted my Hermes to just,
00:40:05.420 --> 00:40:07.360
anytime that sees something appear in the RSS feed
00:40:07.360 --> 00:40:10.060
for the podcast to instantly use the MCP server,
00:40:10.240 --> 00:40:12.960
find the details and rewrite the YouTube channel.
00:40:13.380 --> 00:40:15.640
Well, I don't want to just give it full access to my YouTube.
00:40:15.820 --> 00:40:19.859
So what I did is I used Claude Code to build a Python library
00:40:19.860 --> 00:40:22.600
that does the specific things I want it to do to YouTube.
00:40:23.080 --> 00:40:24.560
And I just gave Hermes the wheel.
00:40:24.620 --> 00:40:25.580
I said, here's the wheel.
00:40:25.680 --> 00:40:27.140
You install this if you need to.
00:40:27.440 --> 00:40:29.060
Then you manage the YouTube channel through it.
00:40:29.320 --> 00:40:30.020
And it does.
00:40:30.160 --> 00:40:33.000
And it's gone through all my hundreds of videos
00:40:33.100 --> 00:40:33.760
are all up to date.
00:40:33.880 --> 00:40:34.140
It's perfect.
00:40:34.480 --> 00:40:35.420
And if I change it on the website,
00:40:35.700 --> 00:40:37.940
it automatically
changes on YouTube like 15 minutes later.
00:40:38.180 --> 00:40:38.440
Crazy.
00:40:38.780 --> 00:40:40.580
I think that's something that we can take advantage
00:40:40.860 --> 00:40:43.760
as Python developers is that it's easy for us
00:40:43.760 --> 00:40:46.620
to make our own tools that have a more restricted surface.
00:40:46.800 --> 00:40:47.240
For example,
00:40:47.480 --> 00:40:49.840
I keep meaning to VibeCode
00:40:49.840 --> 00:40:52.080
MSP server for my Pilates booking website,
00:40:52.600 --> 00:40:52.720
right?
00:40:52.920 --> 00:40:55.480
And I would just expose only the tools that I want, right?
00:40:55.500 --> 00:40:58.740
Like I wouldn't have, you know, I wouldn't have like my account.
00:40:59.120 --> 00:41:03.120
I would just have a, you know, like list this week sessions and book a session,
00:41:03.380 --> 00:41:03.480
right?
00:41:03.600 --> 00:41:03.820
So,
00:41:04.240 --> 00:41:04.600
you know, for,
00:41:05.180 --> 00:41:06.900
you know, especially for us as Python developers,
00:41:07.120 --> 00:41:07.680
this should be really
00:41:07.820 --> 00:41:07.920
easy.
00:41:08.000 --> 00:41:08.660
We just,
00:41:09.020 --> 00:41:10.020
you know, prompt and be like, hey,
00:41:10.360 --> 00:41:12.480
you know, make this MSP server that does this
00:41:12.620 --> 00:41:12.940
and this,
00:41:13.980 --> 00:41:15.760
you know, and the hardest part is like auth,
00:41:15.920 --> 00:41:16.260
but there's,
00:41:16.420 --> 00:41:16.740
you know, there's
00:41:16.740 --> 00:41:17.940
ways to set that up.
00:41:18.140 --> 00:41:22.500
And then we can like feel confident pointing our agents at these tools,
00:41:22.880 --> 00:41:24.740
these servers or CLIs or however you've done them,
00:41:25.200 --> 00:41:30.620
and not worry about something bad happening,
00:41:30.820 --> 00:41:30.920
right?
00:41:31.160 --> 00:41:36.900
I know like many people are just kind of YOLOing with the current rage of Muse and Grok Pot and that.
00:41:36.980 --> 00:41:38.700
But then, of course, every day we see this like,
00:41:38.900 --> 00:41:41.380
you know, horrible thing that happened to someone because of that.
00:41:41.780 --> 00:41:43.840
It RMRF'd our production database.
00:41:44.100 --> 00:41:46.460
Why did you give it access to your production database?
00:41:46.600 --> 00:41:47.060
What are you doing?
00:41:48.000 --> 00:41:48.220
So,
00:41:48.500 --> 00:41:52.060
you know, we we're still in an advantage as developers where,
00:41:52.640 --> 00:41:58.240
you know, if we don't have already access to tools that allow us to do restriction,
00:41:58.780 --> 00:41:59.380
then we can,
00:41:59.740 --> 00:42:02.180
you know, we can buy our own tools for that.
00:42:02.300 --> 00:42:04.360
Many of these tools, like, you know, with MCP servers,
00:42:04.560 --> 00:42:09.660
a lot of them will have a bunch of tools and you could decide to give your agent access to just some of them and not others.
00:42:09.920 --> 00:42:10.000
Right.
00:42:10.160 --> 00:42:10.220
So,
00:42:10.500 --> 00:42:10.620
you know,
00:42:10.960 --> 00:42:14.640
MCP servers will actually like annotate which of the tools are read only.
00:42:14.800 --> 00:42:15.520
And you might say, hey,
00:42:15.980 --> 00:42:18.180
you know, you can only access the read only tools.
00:42:19.100 --> 00:42:22.020
And with like the GitHub MCP server, it has this notion of tool sets.
00:42:22.160 --> 00:42:23.240
And you can say you can say like, hey,
00:42:23.780 --> 00:42:25.140
you can you're only allowed to,
00:42:25.340 --> 00:42:25.460
you know,
00:42:25.620 --> 00:42:26.620
use such and such tool set.
00:42:26.920 --> 00:42:29.100
A little bit like restricting the job that you give them.
00:42:29.560 --> 00:42:30.700
Because when they come back,
00:42:30.880 --> 00:42:32.920
it goes to the MCP and it says, what can I do?
00:42:32.960 --> 00:42:34.680
And it's like, oh, well, here's 200 things you can do.
00:42:35.400 --> 00:42:38.360
You don't necessarily want it to do those 200 things just randomly.
00:42:38.440 --> 00:42:40.720
It might be like, like you said, list schedules,
00:42:41.200 --> 00:42:41.920
check my free time,
00:42:42.220 --> 00:42:42.860
book me this thing.
00:42:43.100 --> 00:42:44.620
You get three or four tools,
00:42:44.860 --> 00:42:45.400
you know what I mean?
00:42:45.520 --> 00:42:46.020
And so,
00:42:46.280 --> 00:42:49.040
yeah, you have a talk on just stricter schemas,
00:42:49.220 --> 00:42:49.680
increased reliability,
00:42:49.980 --> 00:42:53.100
and then also on directing them to the, like, oh, the filter of the tools one.
00:42:53.180 --> 00:42:53.380
That's it.
00:42:53.500 --> 00:42:54.980
Filtering tools from MCP servers.
00:42:56.060 --> 00:42:57.780
Basically how you can save tokens,
00:42:57.970 --> 00:42:58.460
make it safer.
00:42:59.120 --> 00:43:01.060
There's some tools in Copilot,
00:43:01.360 --> 00:43:05.940
and this might also apply if you run Codex or Claude
00:43:06.260 --> 00:43:07.600
in the chat window in VS Code.
00:43:07.670 --> 00:43:08.140
I can't remember.
00:43:08.460 --> 00:43:08.680
Yeah.
00:43:08.790 --> 00:43:12.260
So when I wrote this blog post here about filtering tools,
00:43:12.540 --> 00:43:13.140
this was,
00:43:13.340 --> 00:43:13.740
what, five?
00:43:15.320 --> 00:43:15.500
Ancient.
00:43:15.860 --> 00:43:16.140
It's ancient.
00:43:16.250 --> 00:43:16.360
Ancient.
00:43:16.760 --> 00:43:17.520
So at that time,
00:43:17.760 --> 00:43:18.560
like in early days,
00:43:18.780 --> 00:43:19.420
VS Code,
00:43:19.570 --> 00:43:22.580
actually if you selected more than I think it was like 175 tools,
00:43:22.780 --> 00:43:24.780
you'd like get this warning that's like, you have more than,
00:43:25.300 --> 00:43:25.520
you know,
00:43:26.090 --> 00:43:27.180
this many tools selected,
00:43:27.400 --> 00:43:30.760
like you may want to reduce them, right? And everyone would get so stressed out, like trying
00:43:30.860 --> 00:43:33.600
to decide
which of them to like turn off and turn on.
00:43:34.040 --> 00:43:36.380
Now, a few things have changed since that time.
00:43:37.020 --> 00:43:38.420
One, obviously, our models have gotten,
00:43:38.580 --> 00:43:39.580
but two,
00:43:39.830 --> 00:43:42.780
the models have tool search and deferred tool
00:43:42.970 --> 00:43:48.820
loading built in. So both the new OpenAI models and Anthropic models, like from the last six months
00:43:48.840 --> 00:43:49.160
or so,
00:43:49.320 --> 00:43:54.340
they have a built-in capability that's actually was like trained into them as part
00:43:54.340 --> 00:43:56.600
of their RLHF, their post-training,
00:43:56.800 --> 00:44:01.320
where they know how to search for a tool and to
00:44:01.520 --> 00:44:02.140
load in a tool,
00:44:02.420 --> 00:44:07.680
like to use a deferred tool if they don't see a tool fully loaded in,
00:44:07.870 --> 00:44:08.020
right?
00:44:08.110 --> 00:44:09.960
So a lot of the modern agents will,
00:44:10.250 --> 00:44:12.280
if they're seeing that you're using a model,
00:44:12.620 --> 00:44:12.740
like our
00:44:12.920 --> 00:44:13.400
OpenAI model,
00:44:13.910 --> 00:44:17.400
they may choose to use that deferred tool.
00:44:17.780 --> 00:44:18.420
So these days,
00:44:18.840 --> 00:44:25.580
I don't really worry as much about having too many tools turned on because I know that there's,
00:44:25.740 --> 00:44:27.840
you know, much better handling of many tools.
00:44:29.120 --> 00:44:29.240
However,
00:44:29.640 --> 00:44:29.880
you know,
00:44:30.480 --> 00:44:34.000
if you like change your model to like a much worse model or something like, you know, then,
00:44:35.160 --> 00:44:36.480
you know, then you'll differ.
00:44:37.340 --> 00:44:39.680
Yeah, I played around with one of the smaller,
00:44:40.100 --> 00:44:41.320
more self-hosted like models.
00:44:41.380 --> 00:44:43.700
It wasn't quite that, but it wasn't the frontier ones.
00:44:44.020 --> 00:44:45.660
And I gave it basically this project.
00:44:45.780 --> 00:44:47.140
I want you to change part of this.
00:44:47.280 --> 00:44:48.480
It's like a little bit later, it's like,
00:44:48.660 --> 00:44:50.260
I've removed all of this from your app.
00:44:50.280 --> 00:44:50.900
I'm like, no, no, no.
00:44:51.040 --> 00:44:52.460
Why did you think you'd delete all?
00:44:52.540 --> 00:44:54.600
I just wanted you to take a little part of it.
00:44:55.900 --> 00:44:59.000
And it just made me remember like, oh, yeah, it used to be like that all the time.
00:44:59.140 --> 00:45:00.840
It would just go crazy and do weird stuff.
00:45:01.080 --> 00:45:04.680
And that doesn't really happen very much with the top tier models these days.
00:45:05.700 --> 00:45:07.420
You're a little bit going to let it figure it out.
00:45:07.560 --> 00:45:11.180
I think that's some of the newer guidance is it's smart enough that you're just going to be in its way.
00:45:12.180 --> 00:45:16.480
Yeah, it means like when you're designing MSP servers and skills,
00:45:16.640 --> 00:45:17.260
especially skills,
00:45:17.520 --> 00:45:19.160
like a lot of people, we have like these really,
00:45:20.000 --> 00:45:20.240
you know,
00:45:20.420 --> 00:45:20.860
long,
00:45:21.400 --> 00:45:22.800
verbose agent skills.
00:45:23.500 --> 00:45:23.820
And,
00:45:24.180 --> 00:45:25.400
you know, as the models get better,
00:45:25.880 --> 00:45:26.120
we,
00:45:27.020 --> 00:45:27.860
you know, may not need those skills.
00:45:27.880 --> 00:45:30.840
And especially if your skills are like over prescriptive.
00:45:31.020 --> 00:45:34.440
That's the big thing I've seen with agent skills lately is a skill.
00:45:35.200 --> 00:45:36.420
If a skill has too,
00:45:36.680 --> 00:45:38.560
too absolute of a statement in it.
00:45:38.660 --> 00:45:40.380
Like there was one I was using the other day that was like,
00:45:40.660 --> 00:45:44.340
oh, if they ask to do anything else besides what's in this file,
00:45:44.540 --> 00:45:45.840
then say it is not possible.
00:45:46.090 --> 00:45:46.220
Right.
00:45:46.520 --> 00:45:49.720
And like that just like shut the agent down entirely.
00:45:50.030 --> 00:45:53.080
We're like I couldn't do things that otherwise I could have done with that API.
00:45:53.570 --> 00:45:59.300
So especially if you're like putting out agent skills to help people use like your API or your Python package,
00:45:59.600 --> 00:46:02.760
like everything needs to be very intentionally in there.
00:46:02.920 --> 00:46:04.100
And you need to be really,
00:46:04.280 --> 00:46:12.900
really careful about kind of any statements of constraints and limits because you might end up like hobbling the agent that otherwise would have been successful.
00:46:13.760 --> 00:46:17.320
But you accidentally held it back. Right. So don't don't hold back. Right.
00:46:17.480 --> 00:46:18.480
Skills should, you know,
00:46:18.720 --> 00:46:21.820
streamline things and give some hints and tips and whatnot.
00:46:22.720 --> 00:46:27.300
But usually skills should not be holding an agent back from successfully using an API.
00:46:27.800 --> 00:46:27.960
Yeah.
00:46:28.260 --> 00:46:30.260
There's so many of those projects on GitHub.
00:46:30.840 --> 00:46:32.200
I love GitHub. But there's so many.
00:46:32.660 --> 00:46:36.700
There's thousands of here's my set of skills that will make it a lawyer.
00:46:36.920 --> 00:46:38.640
It'll make it an accountant or whatever.
00:46:38.700 --> 00:46:40.640
And you're like, I really don't want to put this.
00:46:40.720 --> 00:46:42.380
It's just going to pollute it with these ideas.
00:46:42.660 --> 00:46:44.920
I bet it would be better if I just let it be, you know?
00:46:45.200 --> 00:46:45.480
Yeah.
00:46:45.920 --> 00:46:48.320
I mean, I'm happy to use my own skills.
00:46:48.460 --> 00:46:53.840
I think what I encourage people is find skills that people are talking about that you're in shit in.
00:46:54.040 --> 00:46:56.420
Fork them and then make them your own,
right?
00:46:56.680 --> 00:47:02.700
Because like there's very few skills that I use from other people because,
00:47:03.100 --> 00:47:03.220
you know,
00:47:03.440 --> 00:47:04.180
I'm very opinionated.
00:47:04.280 --> 00:47:06.040
I want my workflows to work great for me.
00:47:06.240 --> 00:47:09.020
So I'm very happy with the skills that I maintain.
00:47:09.220 --> 00:47:13.320
Right. So I have presentation skills is my biggest repo of skills.
00:47:13.380 --> 00:47:16.020
And it's all just things related to making presentations like,
00:47:16.980 --> 00:47:19.680
you know, generating slide decks and images for them,
00:47:19.880 --> 00:47:21.620
making transcripts, lots of stuff with YouTube.
00:47:21.940 --> 00:47:22.040
Right.
00:47:22.240 --> 00:47:24.000
Like transcribing them after.
00:47:24.520 --> 00:47:29.060
And then I have some other skills that have to do with like Azure deployment and stuff.
00:47:29.440 --> 00:47:32.060
So I'm happy with those skills because I have a lot of control over them.
00:47:32.070 --> 00:47:37.620
But it's so hard to use someone else's skill and have it be a great experience for you.
00:47:37.800 --> 00:47:39.800
So find a skill you like and then fork it.
00:47:40.000 --> 00:47:40.700
Make it your own.
00:47:40.980 --> 00:47:41.160
Yeah,
00:47:41.360 --> 00:47:41.800
that's great advice.
00:47:42.280 --> 00:47:42.460
Absolutely.
00:47:42.880 --> 00:47:43.100
Now,
00:47:43.440 --> 00:47:45.560
let's talk CLIs for a minute.
00:47:45.890 --> 00:47:49.680
I think having CLIs used to be something that was just cool.
00:47:49.880 --> 00:47:52.480
So you could maybe script it or you could automate it.
00:47:52.580 --> 00:47:54.780
Like, I want to be able to do this thing with something.
00:47:55.360 --> 00:47:56.900
And if I make a CLI,
00:47:57.200 --> 00:48:00.560
then my Bash or my Ansible script or whatever can run it.
00:48:00.820 --> 00:48:02.120
So that's why we're going to have a CLI.
00:48:02.180 --> 00:48:02.820
And I think, honestly,
00:48:03.160 --> 00:48:08.680
CLIs these days are a really interesting escape hatch for agents and things like that.
00:48:08.700 --> 00:48:09.640
They're like, for some reason,
00:48:09.840 --> 00:48:12.160
they don't connect or they can't connect to an MCP.
00:48:12.400 --> 00:48:17.380
Like, maybe it's an app that only would have an MCP when it's running, but you only run it for a moment.
00:48:17.680 --> 00:48:20.720
So maybe give us your thoughts on this CLI story.
00:48:21.240 --> 00:48:24.700
Yes, we have to have the required MCP versus CLI debate.
00:48:25.860 --> 00:48:26.140
We do.
00:48:26.240 --> 00:48:27.700
It wouldn't be complete if we didn't do it.
00:48:27.900 --> 00:48:29.100
It's contractually obliged.
00:48:29.920 --> 00:48:30.400
So,
00:48:31.400 --> 00:48:32.240
yeah, it's very interesting,
00:48:32.440 --> 00:48:32.560
actually.
00:48:32.840 --> 00:48:32.920
Like,
00:48:33.740 --> 00:48:37.400
my colleague has a project that's now called Scope.
00:48:37.440 --> 00:48:38.300
And in this project,
00:48:38.520 --> 00:48:44.700
they actually will set up scenarios to see how well an agent succeeds at a particular task in a particular environment.
00:48:45.020 --> 00:48:50.060
And the example that he gave in a talk the other day was using the GitHub CLI,
00:48:50.440 --> 00:48:51.120
GH command.
00:48:51.500 --> 00:48:57.020
and the GitHub MCP server and then just nothing at all compared to see like how long would it take?
00:48:57.130 --> 00:48:58.940
How successful would it be? Like would it?
00:48:59.670 --> 00:49:02.120
So in this case, it was actually fixing a bug on one of my repos,
00:49:03.580 --> 00:49:04.620
which I didn't know he was going to do.
00:49:04.650 --> 00:49:06.880
So I was surprised to see this PR the morning of his talk.
00:49:07.060 --> 00:49:09.220
But yeah, so he's,
00:49:09.480 --> 00:49:09.640
you know,
00:49:09.800 --> 00:49:12.180
so it's comparing to see, you know, token efficiency,
00:49:12.490 --> 00:49:12.580
success,
00:49:13.500 --> 00:49:14.880
number of tool calls, all that stuff.
00:49:15.100 --> 00:49:15.160
Right.
00:49:15.640 --> 00:49:21.160
Now, the results from that particular experiment was that the GitHub CLI was the best, right?
00:49:21.420 --> 00:49:23.520
And I think a lot of people would actually predict that.
00:49:23.680 --> 00:49:29.740
It required less tokens overall and was successful more of the time.
00:49:30.680 --> 00:49:31.400
But why is that?
00:49:31.660 --> 00:49:34.680
Part of that is because the agents, like LLMs,
00:49:34.860 --> 00:49:36.040
they know the GitHub CLI.
00:49:36.160 --> 00:49:37.620
The GitHub CLI is deep,
00:49:37.880 --> 00:49:38.780
deep in the weights,
00:49:39.000 --> 00:49:39.080
right?
00:49:39.220 --> 00:49:39.980
So they're very,
00:49:40.160 --> 00:49:42.320
very good at using the GitHub CLI.
00:49:42.480 --> 00:49:44.600
they really don't know the GitHub MCP server much at all,
00:49:44.710 --> 00:49:44.820
especially,
00:49:45.050 --> 00:49:46.120
you know, it changes over time.
00:49:46.580 --> 00:49:47.380
So it's very,
00:49:47.580 --> 00:49:49.120
it's really not surprising
00:49:49.760 --> 00:49:53.760
that they would do particularly well at using that CLI.
00:49:54.620 --> 00:49:54.840
So,
00:49:55.140 --> 00:49:57.100
you know, so the takeaway from that experiment
00:49:57.380 --> 00:49:58.760
is like in that particular example,
00:49:59.160 --> 00:50:00.320
yeah, it was more successful with CLI
00:50:00.540 --> 00:50:02.580
and there were some good kind of just specific learnings
00:50:02.640 --> 00:50:05.100
for the GitHub MCP server about what it struggled with
00:50:05.110 --> 00:50:06.240
when it was calling that server.
00:50:07.140 --> 00:50:09.840
But generally what you should be doing is like ideally
00:50:10.240 --> 00:50:11.400
like always offering everything,
00:50:11.800 --> 00:50:11.880
right?
00:50:11.980 --> 00:50:14.240
So you should have a CLI probably.
00:50:14.440 -->
00:50:15.380
You should have an API,
00:50:15.560 --> 00:50:16.400
like a traditional API.
00:50:16.520 --> 00:50:17.840
Like we're not getting rid of APIs.
00:50:18.020 --> 00:50:19.520
Like APIs for HTTP services,
00:50:19.860 --> 00:50:21.580
like you still want an API,
00:50:22.080 --> 00:50:22.560
an SDK,
00:50:23.080 --> 00:50:23.720
a CLI.
00:50:24.580 --> 00:50:25.720
An MCP server,
00:50:26.240 --> 00:50:26.440
you know,
00:50:26.500 --> 00:50:29.160
is something that you've ideally optimized for agents.
00:50:29.200 --> 00:50:31.340
So you should be like running these tests with agents
00:50:31.400 --> 00:50:31.740
and saying,
00:50:31.900 --> 00:50:31.980
hey,
00:50:32.180 --> 00:50:32.800
for this scenario,
00:50:33.220 --> 00:50:34.560
for all these range of scenarios,
00:50:35.460 --> 00:50:37.960
how successful are the agents when,
00:50:38.640 --> 00:50:39.880
you know, when using our MCP server?
00:50:40.080 --> 00:50:41.100
And also with agent skills,
00:50:41.260 --> 00:50:43.000
Like we do the same test with agent skills.
00:50:43.880 --> 00:50:44.320
So these are,
00:50:44.480 --> 00:50:45.520
you know, think of these as,
00:50:45.700 --> 00:50:47.760
you know, you're developing tools for agents
00:50:48.320 --> 00:50:50.900
and you really want to see how successful agents.
00:50:51.040 --> 00:50:52.020
You can do the same with CLI.
00:50:52.130 --> 00:50:56.260
Like you could, there are definitely people who are trying to optimize their CLIs more
00:50:56.580 --> 00:50:57.260
for agents.
00:50:57.350 --> 00:51:02.380
Like there was a great talk at PyAI last year from the folks at Astral where they were talking
00:51:02.430 --> 00:51:05.600
about that there was a lot of improvements they were going to make to like rough that
00:51:05.680 --> 00:51:06.800
made it better for humans.
00:51:07.330 --> 00:51:08.560
But now they're like, well, what's the point?
00:51:08.860 --> 00:51:10.400
Humans aren't the ones running rough anymore.
00:51:10.940 --> 00:51:11.760
agents are running rough.
00:51:12.000 --> 00:51:14.240
They have all these ideas now about how they're going to make rough
00:51:14.540 --> 00:51:15.360
better for agents.
00:51:16.180 --> 00:51:17.580
So they may not even like bother.
00:51:17.860 --> 00:51:19.240
Like, I mean, yes, a couple of humans
00:51:19.640 --> 00:51:21.680
somewhere are running rough and actually looking at the results.
00:51:22.340 --> 00:51:23.760
But yeah, they're, you know,
00:51:23.800 --> 00:51:27.340
so now they're like much more focused on like optimizing the experience for agents.
00:51:27.760 --> 00:51:29.500
My agent runs rough a lot.
00:51:29.700 --> 00:51:33.520
I don't know about yours, but I told the standing rule for all of
00:51:33.600 --> 00:51:35.000
my agents, if they're doing coding,
00:51:35.300 --> 00:51:35.580
that is,
00:51:35.860 --> 00:51:37.120
is whenever you're done,
00:51:37.420 --> 00:51:38.359
you're not done until
00:51:38.380 --> 00:51:39.460
Ruff format,
00:51:40.020 --> 00:51:40.300
ruff check,
00:51:40.720 --> 00:51:41.600
and ty check.
00:51:41.960 --> 00:51:43.800
All of those run without warnings,
00:51:43.980 --> 00:51:44.560
without errors.
00:51:44.870 --> 00:51:45.300
You know what I mean?
00:51:45.780 --> 00:51:47.700
Like if you introduce something that breaks those rules,
00:51:48.240 --> 00:51:48.960
those are easy to fix.
00:51:49.480 --> 00:51:49.700
Right.
00:51:49.770 --> 00:51:50.120
So that,
00:51:50.290 --> 00:51:52.120
I mean, you can put that in your agents.md.
00:51:52.650 --> 00:51:54.500
I oftentimes have that in my agents.md.
00:51:54.730 --> 00:51:57.620
You can even formalize like a lot of these coding agents
00:51:57.840 --> 00:51:58.820
have what's called like a hook,
00:51:59.360 --> 00:52:00.620
at least VS Code, we call it a hook.
00:52:01.220 --> 00:52:03.700
So you can have a hook that runs every single time
00:52:03.880 --> 00:52:05.140
and make sure that it runs.
00:52:05.140 --> 00:52:07.200
But a lot of times if you just put it in your agents.md,
00:52:07.400 --> 00:52:09.280
then that's enough instruction to,
00:52:09.820 --> 00:52:10.200
you know, to be,
00:52:10.440 --> 00:52:11.700
to be always taking those actions.
00:52:12.200 --> 00:52:15.780
Yeah. If you want to be super old school, I mean, we're talking like 2024 old school,
00:52:16.130 --> 00:52:18.740
you could put it in a, a get pre-commit hook really.
00:52:18.870 --> 00:52:19.440
Oh yeah, of course.
00:52:19.600 --> 00:52:21.100
That's pre-commit though. Cause we're like,
00:52:21.300 --> 00:52:22.200
you know, that's even like,
00:52:22.420 --> 00:52:23.440
like, like later in the process.
00:52:23.640 --> 00:52:25.540
Right. So it depends how often, right. So you've got hooks,
00:52:26.020 --> 00:52:28.780
you know, you've got hooks for the agent hooks are,
00:52:28.940 --> 00:52:29.680
are much more frequent.
00:52:29.920 --> 00:52:29.980
Right.
00:52:30.240 --> 00:52:30.420
So,
00:52:30.730 --> 00:52:30.820
um,
00:52:31.200 --> 00:52:32.420
you know, we don't know how often you're committing.
00:52:32.790 --> 00:52:32.880
Um,
00:52:33.180 --> 00:52:34.719
but you know, if you want it to happen every
00:52:34.740 --> 00:52:38.420
time I have an agent hook that just every time the agent stops,
00:52:38.860 --> 00:52:39.920
my kid giggles,
00:52:40.320 --> 00:52:40.940
it just plays
00:52:40.940 --> 00:52:42.280
a sound of her giggling.
00:52:42.500 --> 00:52:42.760
And it's,
00:52:43.020 --> 00:52:44.340
it's very cute. It just makes,
00:52:44.530 --> 00:52:45.860
you know, it just fills my life.
00:52:47.560 --> 00:52:47.640
Yeah.
00:52:47.860 --> 00:52:52.460
And then it's programmed so that if I leave the machine for more than a minute,
00:52:52.890 --> 00:52:58.900
then it'll also like kind of giggle harder and tell me the name of the session so that I can
00:52:59.080 --> 00:53:00.240
decide whether to come back my machine.
00:53:00.400 --> 00:53:02.339
Right. So that way I can like do
my kids laundry while
00:53:02.360 --> 00:53:03.120
Yeah, yeah,
00:53:03.340 --> 00:53:04.060
yeah. That's super cool.
00:53:04.240 --> 00:53:13.320
So we're not complete with the CLI conversation. I think one of the things that I would like to encourage people who are building CLIs for agents,
00:53:13.520 --> 00:53:17.860
a lot of the things that are interesting about this is it's good for people and it's good for agents.
00:53:17.940 --> 00:53:19.740
like because they kind of both use English
00:53:20.240 --> 00:53:21.300
or natural spoken language,
00:53:21.860 --> 00:53:24.280
it's optimizing for one sort of helps the other a lot of times.
00:53:24.440 --> 00:53:26.660
Anyway, so my suggestion about this
00:53:26.690 --> 00:53:30.480
is that use a nice CLI framework like Typer or Click
00:53:30.880 --> 00:53:32.140
or even if you're using ArcPars,
00:53:32.340 --> 00:53:33.160
one of these built-in ones,
00:53:33.480 --> 00:53:36.640
make sure there's lots of help documentation and stuff
00:53:36.850 --> 00:53:39.020
because then the first thing the agent might do
00:53:39.180 --> 00:53:40.840
is your CLI --help.
00:53:41.120 --> 00:53:44.260
Okay, I now understand this tool that I have almost completely.
00:53:44.480 --> 00:53:44.800
Let's go.
00:53:44.850 --> 00:53:45.380
You know what I mean?
00:53:45.680 --> 00:53:46.860
You don't have to do much more to teach it.
00:53:46.920 --> 00:53:49.400
Yeah. And you can even ask the agent like for advice,
00:53:49.700 --> 00:53:49.980
like, hey,
00:53:50.180 --> 00:53:50.960
what would help you?
00:53:51.180 --> 00:53:51.260
Like,
00:53:51.660 --> 00:53:53.080
what would have helped you achieve that?
00:53:53.360 --> 00:53:53.720
Right.
00:53:53.960 --> 00:53:54.340
Like, you know,
00:53:54.520 --> 00:53:55.880
what were what were the issues with that?
00:53:56.260 --> 00:53:57.220
Yeah. It's interesting because like,
00:53:57.460 --> 00:53:58.260
you know, on the one hand,
00:53:58.500 --> 00:54:05.460
you think it's different to optimize something for an agent versus optimize it for a human. I think that is where some of the current tension is, especially with documentation.
00:54:05.980 --> 00:54:11.740
trying to figure out is our documentation you know who is the one actually reading it um you know so
00:54:11.800 --> 00:54:16.280
right now you know we have agents.md and that's definitely targeted agents we have readme.md and
00:54:16.340 --> 00:54:22.020
a lot of times i end up repeating similar things across both um and yeah and i think just right now
00:54:22.160 --> 00:54:26.800
it's just currently um attention i think there's some clis that will have kind of like an agent
00:54:27.280 --> 00:54:33.320
mode that might be like much more verbose for example because agents can actually i think
00:54:33.320 --> 00:54:36.240
there's actually it goes but sometimes they're like lesser rows because it depends if you're
00:54:36.240 --> 00:54:41.280
trying to reduce token count or just increase information right because uh you know lms can
00:54:41.460 --> 00:54:46.220
handle a fair bit of information like they can look through a whole python traceback error right
00:54:46.360 --> 00:54:51.200
and they can understand it whereas me like you know it takes me a while to get to like the right
00:54:51.500 --> 00:54:56.899
point in the error um so it's i think i i do find it like really fascinating to try and figure out
00:54:56.920 --> 00:54:57.440
you know,
00:54:58.040 --> 00:55:01.020
as the world is moving so much right now,
00:55:01.440 --> 00:55:01.600
you know,
00:55:01.800 --> 00:55:04.000
what kind of entity are we
00:55:04.440 --> 00:55:07.000
optimizing our developer experiences for?
00:55:07.220 --> 00:55:09.700
I promised you a GitHub CLI story.
00:55:10.090 --> 00:55:12.600
Oh, yeah. So like a year ago or so,
00:55:12.980 --> 00:55:14.480
you know, not that long ago,
00:55:14.820 --> 00:55:15.960
I was doing something with
00:55:16.160 --> 00:55:20.240
Claude and I didn't tell it to go to GitHub. I didn't tell that there was a GitHub.
00:55:20.510 --> 00:55:20.780
It just
00:55:20.970 --> 00:55:26.219
happened to be in a Git repository and I was working zero intention to go talk to GitHub or
00:55:26.240 --> 00:55:29.080
anything and I said, okay, what if we did it this way?
00:55:29.480 --> 00:55:30.280
And it says to me,
00:55:30.760 --> 00:55:31.800
I'm not logged into VS
00:55:32.000 --> 00:55:32.960
code or any of the tools.
00:55:33.500 --> 00:55:36.100
I unknowingly was logged into the GitHub CLI.
00:55:36.460 --> 00:55:37.460
And I ask it a question. It
00:55:37.460 --> 00:55:37.540
goes,
00:55:37.760 --> 00:55:37.940
well,
00:55:38.420 --> 00:55:41.960
three years ago, you added this GitHub issue and it talked about it this way, but I think
00:55:42.060 --> 00:55:43.100
it's changed. Like what,
00:55:43.600 --> 00:55:45.260
how, how did you get to my GitHub?
00:55:45.500 --> 00:55:46.720
I need to know what is going on here.
00:55:47.120 --> 00:55:52.019
And eventually like, oh, it used, I went back and looked like, oh, it used the GitHub CLI to explore
00:55:52.040 --> 00:55:56.480
the project and I didn't even tell it to him like what is it doing but in the end I was like you know
00:55:56.580 --> 00:56:00.680
what cool it brought something from a long time ago back to the future and like we're we're working
00:56:00.730 --> 00:56:05.260
on it's good but it freaked me out that that actually reminds me of when I was prepping for
00:56:05.500 --> 00:56:10.900
today's podcast I asked you know I was like hey you know it's a podcast it's about like Python and MCP
00:56:11.260 --> 00:56:16.320
and it immediately connected to my emails and my events and it found that you would like attach the
00:56:16.440 --> 00:56:19.899
Google Doc to the because I didn't know you'd made a Google Doc of what topics we were going to talk
00:56:19.920 --> 00:56:21.180
about. I had missed that.
00:56:21.430 --> 00:56:23.120
So it found the
Google Doc. I was like, okay,
00:56:23.300 --> 00:56:24.480
I've made an entire like
00:56:24.600 --> 00:56:27.560
markdown document prepping you based on the Google Doc. I'm like, what Google Doc?
00:56:28.220 --> 00:56:28.740
What are you
00:56:28.920 --> 00:56:29.300
talking about?
00:56:29.720 --> 00:56:30.080
So,
00:56:30.490 --> 00:56:31.380
you know, you know these things.
00:56:31.640 --> 00:56:31.820
Yeah,
00:56:32.100 --> 00:56:32.180
right.
00:56:32.360 --> 00:56:32.620
So like,
00:56:32.960 --> 00:56:33.120
it's,
00:56:33.420 --> 00:56:33.560
you know,
00:56:33.930 --> 00:56:35.140
these agents can be very powerful.
00:56:35.320 --> 00:56:36.080
They're very good at like,
00:56:36.280 --> 00:56:36.480
you know,
00:56:36.680 --> 00:56:38.040
searching through lots of
00:56:38.340 --> 00:56:38.480
data.
00:56:39.090 --> 00:56:39.220
I,
00:56:39.440 --> 00:56:43.240
you know, just even if it's just a read only tool, that's just searching through things
00:56:43.440 --> 00:56:43.580
like,
00:56:43.780 --> 00:56:47.219
you know, really, really helpful there because it's not going to get bored after the
00:56:47.240 --> 00:56:52.680
first page of you know search results right like it can it can keep going um so you know i think it
00:56:52.800 --> 00:56:59.280
is lowering the barrier to finding information um so you know we don't lose we can't we're not
00:56:59.280 --> 00:57:03.920
going to lose information as much in the big mess of things because we can have like these
00:57:04.070 --> 00:57:08.860
really persistent agents that are looking for this so for me from like an information accessibility
00:57:09.200 --> 00:57:13.520
perspective uh i think that's really good because i've always been very good at like searching the
00:57:13.660 --> 00:57:17.200
web to the point where even at google people would ask me to search for things because they knew i
00:57:17.220 --> 00:57:22.660
like really good at googling even at google um and even like in high school i participated in web
00:57:22.730 --> 00:57:27.620
search competitions because i'm an absolute nerd i wait hold on what search engine do you all use
00:57:27.620 --> 00:57:32.260
for that um that wasn't like lycos or anything was it in high school this was for the science
00:57:32.520 --> 00:57:38.560
olympiad um and that would have been in 2001 so i don't even i think it would have been yahoo
00:57:38.850 --> 00:57:44.339
at that point okay yeah yeah yeah i was a big yahoo user yeah those were amazing times yeah
00:57:44.660 --> 00:57:45.140
So, but now,
00:57:45.320 --> 00:57:45.440
like,
00:57:45.620 --> 00:57:46.360
you know, now it's fine.
00:57:46.370 --> 00:57:49.000
I don't have to lord my searching skills anymore.
00:57:49.300 --> 00:57:50.400
Like now everyone can,
00:57:50.800 --> 00:57:53.320
you know, use their agent to really efficiently search and find
00:57:53.370 --> 00:57:54.280
great results, which is good.
00:57:54.460 --> 00:57:58.120
We're making information universally accessible and useful,
00:57:58.340 --> 00:57:58.620
which is,
00:57:58.900 --> 00:57:59.360
I think, the mission
00:57:59.540 --> 00:58:00.320
statement of Google.
00:58:00.780 --> 00:58:01.840
But it's, you know, someone's mission.
00:58:02.180 --> 00:58:02.420
Yeah,
00:58:02.580 --> 00:58:02.760
absolutely.
00:58:03.300 --> 00:58:05.140
So final thought on CLIs.
00:58:05.240 --> 00:58:07.160
They don't have to necessarily be either or.
00:58:07.390 --> 00:58:10.640
I ended up writing a Talk Python podcast and courses CLI,
00:58:11.010 --> 00:58:11.600
which is kind of weird.
00:58:12.010 --> 00:58:12.640
But if you go,
00:58:12.940 --> 00:58:13.300
it's open source.
00:58:13.460 --> 00:58:20.200
If you go look at it, all it does is it basically calls the MCP endpoints and the actions are like composition of the tools.
00:58:20.640 --> 00:58:24.120
So it really is just a different interface to the MCP server.
00:58:24.180 --> 00:58:29.060
But I'm like, the things that want to automate this that don't have access to the MCP server,
00:58:29.280 --> 00:58:31.020
like how long would it take to write this?
00:58:31.020 --> 00:58:31.900
It wasn't that much work.
00:58:32.120 --> 00:58:32.800
So anyway,
00:58:33.020 --> 00:58:33.620
you can make them,
00:58:33.960 --> 00:58:36.020
they can coexist like cats and dogs living together.
00:58:36.220 --> 00:58:37.120
Mm-hmm, mm-hmm.
00:58:37.660 --> 00:58:37.820
Yeah,
00:58:37.980 --> 00:58:38.760
I mean, that's the thing,
00:58:38.880 --> 00:58:42.940
is that there's some agents that can connect to MCP servers
00:58:43.360 --> 00:58:44.580
that can't connect to CLIs,
00:58:44.800 --> 00:58:47.900
because not all agents have a kind of coding execution environment.
00:58:48.140 --> 00:58:50.120
Especially the cloud ones,
00:58:50.500 --> 00:58:50.600
right?
00:58:50.620 --> 00:58:53.260
If it's just a chat LLN, they're not on your machine.
00:58:53.640 --> 00:58:53.860
Right,
00:58:54.060 --> 00:58:54.200
yeah.
00:58:55.060 --> 00:58:58.480
And then there's other agents that can run CLI commands
00:58:58.620 --> 00:58:59.840
that for some reason they can't,
00:58:59.880 --> 00:59:01.520
MCP servers for whatever reason.
00:59:01.700 --> 00:59:04.580
So it's good to have both.
00:59:04.740 --> 00:59:06.100
And it's easier than it used to be.
00:59:06.160 --> 00:59:08.500
You should be like, all right, well, who's going to be on the CLI team?
00:59:08.800 --> 00:59:09.340
Now it's like,
00:59:09.800 --> 00:59:11.000
I know who's going to be on the CLI team.
00:59:12.420 --> 00:59:12.860
It's all you.
00:59:13.200 --> 00:59:13.580
It's all me.
00:59:14.160 --> 00:59:15.680
Lod, you're writing CLI today.
00:59:15.860 --> 00:59:16.300
Let's get going.
00:59:16.640 --> 00:59:17.940
Or chat or whatever,
00:59:18.220 --> 00:59:18.400
you know,
00:59:18.600 --> 00:59:18.840
co-pilot.
00:59:19.180 --> 00:59:20.620
Well, this has been super fun.
00:59:20.740 --> 00:59:20.960
I mean,
00:59:21.340 -->
00:59:23.300
let's close it out with some final thoughts.
00:59:23.800 --> 00:59:24.340
What do you think?
00:59:24.700 --> 00:59:24.760
Yeah,
00:59:24.950 --> 00:59:26.240
so final thoughts.
00:59:26.410 --> 00:59:29.340
We haven't really got into the Python aspect of MCP.
00:59:29.540 --> 00:59:35.380
So things I would tell Python developers is that there is an official Python MCP SDK.
00:59:36.680 --> 00:59:38.460
and that is to get started.
00:59:38.520 --> 00:59:41.540
But there's also a fantastic package called Fast MCP,
00:59:41.860 --> 00:59:43.440
which builds on top of that MCP SDK.
00:59:44.300 --> 00:59:45.220
And that's from Prefect.
00:59:45.500 --> 00:59:48.880
And that adds all these like really neat integrations.
00:59:49.180 --> 00:59:51.440
So I personally always use Fast MCP,
00:59:52.140 --> 00:59:53.240
but you shouldn't use one of those,
00:59:53.440 --> 00:59:53.520
right?
00:59:53.580 --> 00:59:55.860
I was actually looking at a colleague's MCP server today
00:59:56.000 --> 00:59:57.820
and it was just like handwritten from scratch.
00:59:57.960 --> 00:59:59.420
And I was like, that's not necessary,
00:59:59.600 --> 00:59:59.700
right?
00:59:59.780 --> 00:59:59.880
Like,
01:00:00.200 --> 01:00:02.020
and if there is an official MCP SDK
01:00:02.520 --> 01:00:04.359
that passes the specification
01:00:04.380 --> 01:00:07.300
And then there's Fast MCP, which builds on that.
01:00:07.300 --> 01:00:10.420
So it also is conformant, but then adds all these additional features.
01:00:11.000 --> 01:00:12.040
So if you're starting today,
01:00:12.560 --> 01:00:17.480
you can point your agent at the Fast MCP docs and have it
01:00:18.060 --> 01:00:20.520
write an MCP server using the latest version of MCP protocol,
01:00:20.800 --> 01:00:22.900
which is a really nice improved
01:00:23.120 --> 01:00:23.320
version.
01:00:23.600 --> 01:00:24.280
It's stateless,
01:00:24.480 --> 01:00:26.240
so it's more scalable and direction ready.
01:00:27.180 --> 01:00:31.560
So it is very easy to get started writing your first Python MCP server.
01:00:33.220 --> 01:00:35.480
And yeah, and there is also a conformance suite.
01:00:35.720 --> 01:00:38.280
So if for some reason you did write your own MCP server,
01:00:38.780 --> 01:00:41.280
you should at least run the conformance suite
01:00:41.660 --> 01:00:43.080
to see that it aligns the spec.
01:00:43.900 --> 01:00:48.320
But easiest way is start server and just give it a go
01:00:48.320 --> 01:00:49.360
and maybe just make one for fun
01:00:49.600 --> 01:00:52.900
just so you can understand how this new protocol works
01:00:53.240 --> 01:00:54.240
and it'll give you more insight
01:00:54.620 --> 01:00:55.900
as to when you're using MCP servers
01:00:56.260 --> 01:00:57.960
with your favorite agent.
01:00:58.240 --> 01:00:59.640
Yeah, I don't think I really understood
01:00:59.880 --> 01:01:02.160
how MCP servers really worked until I built one.
01:01:02.380 --> 01:01:02.580
Right.
01:01:02.830 --> 01:01:02.960
Yeah.
01:01:03.110 --> 01:01:06.080
Which is like, I mean, that's one of the greatest way of, you know,
01:01:06.450 --> 01:01:07.900
learning how these things work.
01:01:08.240 --> 01:01:10.180
I didn't really understand how they worked until I built one,
01:01:10.250 --> 01:01:12.200
put it in production, and then had an error with it.
01:01:13.619 --> 01:01:15.960
Wait, this is not working the way I expected.
01:01:16.140 --> 01:01:16.240
Uh-oh.
01:01:16.540 --> 01:01:17.020
What's going on?
01:01:17.320 --> 01:01:18.080
That's when you really,
01:01:18.280 --> 01:01:19.280
really understand something,
01:01:19.540 --> 01:01:19.600
right?
01:01:19.800 --> 01:01:21.100
That is for sure.
01:01:21.260 --> 01:01:22.680
That is for sure. Cool. All right. Well,
01:01:23.040 --> 01:01:23.420
Pamela,
01:01:23.640 --> 01:01:24.760
thanks for taking the time for being on the show.
01:01:24.960 --> 01:01:26.040
Always fun to...
01:01:26.300 --> 01:01:27.080
All right. Awesome.
01:01:27.340 --> 01:01:28.180
See you next time.
01:01:28.450 --> 01:01:28.700
See ya.
01:01:30.180 --> 01:01:32.460
This has been another episode of Talk Python To Me.
01:01:32.840 --> 01:01:33.560
Thank you to our sponsors.
01:01:33.790 --> 01:01:35.100
Be sure to check out what they're offering.
01:01:35.250 --> 01:01:36.620
It really helps support the show.
01:01:37.380 --> 01:01:39.220
If you or your team needs to learn Python,
01:01:39.450 --> 01:01:42.840
we have over 270 hours of beginner and advanced courses
01:01:43.160 --> 01:01:46.580
on topics ranging from complete beginners to async code,
01:01:46.720 --> 01:01:47.420
Flask, Django,
01:01:47.820 --> 01:01:49.500
HTMX, and even LLMs.
01:01:49.720 --> 01:01:50.200
Best of all,
01:01:50.420 --> 01:01:52.000
there's no subscription in sight.
01:01:52.540 --> 01:01:54.320
Browse the catalog at talkpython.fm.
01:01:55.060 --> 01:01:57.000
And if you're not already subscribed to the show
01:01:57.200 --> 01:01:58.420
on your favorite podcast player,
01:01:58.620 --> 01:01:59.680
what are you waiting for?
01:02:00.140 --> 01:02:02.120
Just search for Python in your podcast player.
01:02:02.230 --> 01:02:03.100
We should be right at the top.
01:02:03.540 --> 01:02:06.280
If you enjoyed that geeky rap song, you can download the full track.
01:02:06.510 --> 01:02:08.340
The link is actually in your podcast player show notes.
01:02:09.240 --> 01:02:09.880
This is your host,
01:02:10.100 --> 01:02:10.560
Michael Kennedy.
01:02:10.960 --> 01:02:12.020
Thank you so much for listening.
01:02:12.250 --> 01:02:13.020
I really appreciate it.
01:02:13.460 --> 01:02:14.160
I'll see you next time.