WEBVTT

00:00:00.260 --> 00:00:04.220
Related to tools,
there's one other feature you maybe

00:00:04.240 --> 00:00:08.160
know and that's MCP
or Model Context Protocol, which

00:00:08.240 --> 00:00:12.160
is a protocol that was invented to expose

00:00:12.260 --> 00:00:16.180
tools to AI agents,
which can be smartly discovered and used

00:00:16.219 --> 00:00:20.140
by AI. And Cursor supports MCP,

00:00:20.180 --> 00:00:24.130
which therefore allows you to add all
kinds of tools into Cursor even

00:00:24.160 --> 00:00:27.960
if they're not built in. Because,
just to be clear,

00:00:27.980 --> 00:00:31.820
browser use were built in. But
if you need more, you can add them

00:00:31.880 --> 00:00:35.480
with MCP. And on the Cursor website,
there is a

00:00:35.560 --> 00:00:39.410
MCP directory,
you'll find a link attached,

00:00:39.660 --> 00:00:43.430
add useful MCP servers, useful tools,
like for example,

00:00:43.480 --> 00:00:47.160
Context7, which is a very nice tool
that helps

00:00:47.200 --> 00:00:51.060
Cursor discover up-to-date documentation
for technology it

00:00:51.100 --> 00:00:54.900
might be working with.
In order to add such an MCP server,

00:00:55.000 --> 00:00:58.960
all you have to do
is click Add to Cursor and confirm

00:00:59.000 --> 00:01:02.600
this. And then here,
you see in the Cursor settings,

00:01:02.660 --> 00:01:06.220
this tool is about to be added.
You just need to click

00:01:06.260 --> 00:01:10.170
Install, and here you go. Now this
is being loaded and now it is

00:01:10.240 --> 00:01:13.980
available. And Context7 specifically
is a tool that helps Cursor

00:01:14.060 --> 00:01:17.580
discover documentation.
To show you how it works, I'll

00:01:17.740 --> 00:01:20.980
revert this last change here where the
animation was

00:01:20.990 --> 00:01:24.960
added, and I'll go back to my original

00:01:25.000 --> 00:01:28.520
prompt and I'll edit it.
And I'll remove this web search

00:01:28.560 --> 00:01:31.480
comment and also the comment regarding
viewing this in the

00:01:31.520 --> 00:01:35.280
browser. Instead,
I'll now just add the text "Use

00:01:35.360 --> 00:01:39.300
Context7" to give it a hint
that it should use this Context7

00:01:39.360 --> 00:01:42.540
MCP. That's often useful.
But it should then

00:01:42.620 --> 00:01:46.560
automatically use
that MCP to look for the motion library

00:01:46.660 --> 00:01:50.220
documentation since it should detect
that this is some technology it might need

00:01:50.260 --> 00:01:54.180
more information about.
So now it should not use web search, but

00:01:54.220 --> 00:01:58.180
instead that MCP. If I now click

00:01:58.240 --> 00:02:01.620
Enter, therefore, let's see
if it uses this tool.

00:02:01.640 --> 00:02:05.460
Yes, indeed,
here it asks me whether I want to grant it

00:02:05.480 --> 00:02:09.340
because by default,
it asks before it uses a tool,

00:02:09.400 --> 00:02:12.460
exposed tools.
So I'll allow it to take a look at

00:02:13.280 --> 00:02:17.160
this documentation for this library
through the Context7

00:02:17.200 --> 00:02:20.860
tool. Confirm this again here. And now

00:02:20.920 --> 00:02:23.440
here actually it drew a wrong conclusion.

00:02:23.460 --> 00:02:27.260
It wants to use a library called
FramerMotion, which

00:02:27.320 --> 00:02:31.280
library. So I'll not accept this.
I'll also

00:02:31.320 --> 00:02:34.700
not skip it. Instead,
I'll write the library

00:02:34.760 --> 00:02:36.860
Usage is the same but the name
is different.

00:02:36.960 --> 00:02:40.760
See package.json is already installed.
And I'll send this.

00:02:40.769 --> 00:02:44.200
This will basically reject this command
but tell

00:02:44.220 --> 00:02:47.690
Cursor why I rejected it. So here we go.

00:02:47.760 --> 00:02:51.239
This is now again looking good.
Some code is being added.

00:02:51.310 --> 00:02:54.920
And if I test this here, I can see I still

00:02:54.960 --> 00:02:58.140
got animations going on
and the list updating.

00:02:58.200 --> 00:03:01.040
This time with help of MCP server as a
tool.