[00:00] (0.08s)
Hey everyone, I don't know about you,
[00:02] (2.08s)
but in addition to Cursor and Windsurf,
[00:04] (4.32s)
I've also purchased a subscription for
[00:06] (6.16s)
Claude. I don't use Cursor for my
[00:08] (8.08s)
regular day-to-day tasks, but I do use
[00:10] (10.40s)
it for coding and for that I pay an
[00:12] (12.80s)
extra $20 a month. It is the same with
[00:14] (14.96s)
Windinsurf since it is a little more
[00:16] (16.56s)
expensive because it uses credits and
[00:18] (18.72s)
once those run out, you need to renew
[00:20] (20.80s)
them. Cursor still gives you slow
[00:22] (22.56s)
commands, which is nice. But beyond
[00:24] (24.88s)
those prices, if you try open-source or
[00:27] (27.52s)
free code editors or VS code extensions
[00:30] (30.24s)
like Klein or Rue Code, you have to use
[00:32] (32.56s)
your own API keys. That means you are
[00:34] (34.64s)
always thinking about your API limits
[00:36] (36.80s)
and you are limited in what you can
[00:38] (38.40s)
build. You also cannot use the latest
[00:40] (40.56s)
and greatest models easily. For example,
[00:42] (42.80s)
if you want to use the Claude 3.7 set
[00:45] (45.52s)
model, it is pretty expensive. So, you
[00:47] (47.76s)
might end up choosing Claude 3.5 instead
[00:50] (50.16s)
because it is cheaper. Today, I have a
[00:52] (52.08s)
bit of a solution for you. If you
[00:53] (53.84s)
already have Claude, this could actually
[00:55] (55.68s)
be really helpful. I am talking about a
[00:57] (57.84s)
new MCP called Desktop Commander. It is
[01:00] (60.80s)
completely free and honestly a very
[01:03] (63.04s)
impressive invention. It is built on top
[01:05] (65.12s)
of the file system MCP server and
[01:07] (67.68s)
includes the extra tools that cursor and
[01:09] (69.84s)
windsurf already offer. The best part is
[01:12] (72.56s)
that you can use it with your claw
[01:14] (74.24s)
desktop subscription. In a sense, you
[01:16] (76.56s)
get unlimited token access with no
[01:18] (78.80s)
restrictions on what you can build.
[01:20] (80.64s)
Everything is laid out clearly. You just
[01:22] (82.80s)
specify the file path, describe what you
[01:25] (85.28s)
want it to code, and it starts working.
[01:27] (87.36s)
I am going to walk you through exactly
[01:29] (89.28s)
how it works along with all the useful
[01:31] (91.60s)
features and capabilities that make this
[01:33] (93.76s)
such a powerful tool. If you want, it
[01:36] (96.08s)
can even replace cursor or windsurf for
[01:38] (98.40s)
you. All right, so first let me just
[01:40] (100.72s)
guide you through the installation. It's
[01:42] (102.96s)
relatively easy for this MCP server. You
[01:45] (105.52s)
just have to paste the configuration
[01:47] (107.28s)
into your claw desktop app. You can also
[01:49] (109.84s)
use this with other MCP clients like
[01:52] (112.08s)
cursor or windserve. But using this MCP
[01:55] (115.12s)
server with them kind of defeats the
[01:57] (117.28s)
whole purpose of having it in the first
[01:58] (118.96s)
place. So I don't think there's any need
[02:01] (121.20s)
for that. You just need to copy the
[02:02] (122.88s)
configuration. No additional parameters
[02:05] (125.20s)
or arguments required. Just go into your
[02:07] (127.52s)
claw desktop app, open the settings
[02:09] (129.84s)
panel, and you'll see I've added two MCP
[02:12] (132.48s)
servers already. I've already added it,
[02:14] (134.64s)
but all you have to do is click on edit
[02:16] (136.84s)
configuration, open it up, and paste it
[02:19] (139.44s)
right there. And that's basically it.
[02:21] (141.44s)
And now you can see that if we go into
[02:23] (143.68s)
tools and then into the desktop
[02:25] (145.60s)
commander MCP, all of these tools are
[02:28] (148.00s)
available along with the models we can
[02:30] (150.00s)
use here. Essentially, these are the
[02:32] (152.16s)
same models that cursor typically uses,
[02:34] (154.40s)
but without the extra cost. If you want
[02:36] (156.64s)
the coding IDE experience or prefer
[02:38] (158.96s)
working in a visual code editor, you can
[02:41] (161.28s)
open your code in both VS Code and Claw
[02:43] (163.68s)
Desktop at the same time. Claw Desktop
[02:46] (166.00s)
can act as your AI agent while you view
[02:48] (168.32s)
and edit the code in VS Code. Now that
[02:50] (170.72s)
everything has been added, here is the
[02:52] (172.72s)
simple and basic usage you need to know
[02:55] (175.28s)
to start building with this MCP server.
[02:57] (177.92s)
You just need to give your initial
[02:59] (179.60s)
prompt. Specify where you want to start
[03:02] (182.08s)
working and set the path. In this case,
[03:04] (184.88s)
the path points to my home directory
[03:07] (187.36s)
followed by the developer folder where I
[03:09] (189.52s)
wanted to create a new folder. And
[03:11] (191.44s)
inside that folder, it should build a
[03:13] (193.76s)
small website. Let me show you how it
[03:20] (200.20s)
works. It is going to ask for
[03:22] (202.40s)
permission. I have already granted it.
[03:24] (204.64s)
So, it is not asking me right now. Just
[03:26] (206.64s)
click allow whenever it prompts you. It
[03:29] (209.20s)
makes things a lot smoother if you plan
[03:30] (210.88s)
to keep using the server. As you can
[03:32] (212.64s)
see, it is using different tools such as
[03:34] (214.96s)
the write file tool here. These are some
[03:37] (217.28s)
of the built-in tools of the MCP server.
[03:40] (220.00s)
Since it was built on top of the file
[03:41] (221.92s)
system server, it inherited those tools
[03:44] (224.56s)
and added some really solid coding tools
[03:46] (226.88s)
as well. Okay, it looks like the website
[03:48] (228.96s)
has been created. Let's check it out.
[03:51] (231.12s)
Okay, you can see that I have my finder
[03:53] (233.20s)
window open and these are the files it
[03:55] (235.44s)
created. First, it made a simple website
[03:58] (238.16s)
folder and inside that it generated the
[04:00] (240.88s)
files. I have opened up the website here
[04:03] (243.36s)
and you can see that it is a pretty
[04:05] (245.04s)
basic site just like I asked it to make.
[04:07] (247.60s)
This is the basic way to use desktop
[04:09] (249.44s)
commander. You just specify the folder
[04:11] (251.76s)
and tell it the objective and it starts
[04:13] (253.92s)
building right in that location. Now,
[04:15] (255.68s)
let me show you more of its
[04:16] (256.96s)
capabilities. If you are enjoying the
[04:18] (258.88s)
video, I would really appreciate it if
[04:20] (260.64s)
you could subscribe to the channel. We
[04:22] (262.48s)
are aiming to reach 25,000 subscribers
[04:25] (265.04s)
by the end of this month and your
[04:26] (266.80s)
support genuinely helps. We share videos
[04:29] (269.12s)
like this three times a week, so there
[04:31] (271.12s)
is always something new and useful for
[04:32] (272.96s)
you to explore. Okay, let me show you
[04:35] (275.36s)
some of the tools available in this MCP
[04:37] (277.76s)
server that allow it to serve as a
[04:39] (279.60s)
replacement for cursor or windsurf.
[04:41] (281.68s)
First, it has its own configuration. I
[04:44] (284.32s)
asked it to get the server configuration
[04:46] (286.40s)
and it ran the tool and returned the
[04:48] (288.40s)
following details. Blocked commands,
[04:50] (290.88s)
default shell, allowed directories,
[04:53] (293.52s)
telemetry and client ID. You can change
[04:56] (296.40s)
these if you want. If you are running it
[04:58] (298.32s)
locally, you can manage this yourself.
[05:00] (300.64s)
But if you are using it as a remote MCP
[05:02] (302.88s)
server, you will need to instruct the
[05:04] (304.64s)
LLM to do it for you. I told it to
[05:06] (306.72s)
change the shell to Zshell. And that is
[05:08] (308.96s)
exactly what it did. It used the same
[05:11] (311.12s)
command you would normally use and
[05:12] (312.88s)
executed it successfully. You can modify
[05:15] (315.44s)
any configuration value using the
[05:17] (317.36s)
built-in set tools. Even if you want to
[05:19] (319.60s)
add something new, it simply uses those
[05:22] (322.00s)
tools to apply the changes. Now, one of
[05:24] (324.08s)
its biggest advantages over the original
[05:26] (326.08s)
file system MCP server is that it
[05:28] (328.48s)
supports terminal access. The file
[05:30] (330.56s)
system MCP server allowed claw desktop
[05:33] (333.04s)
to access your file system to create and
[05:35] (335.52s)
manage files. But it did not have
[05:37] (337.44s)
terminal capabilities which limited its
[05:39] (339.92s)
usefulness compared to tools like cursor
[05:42] (342.00s)
and windsurf. That has changed now. This
[05:44] (344.40s)
version includes terminal tools. For
[05:46] (346.48s)
example, it can execute commands
[05:48] (348.32s)
directly. If you want to create a nextjs
[05:50] (350.72s)
app, it can run the command without
[05:52] (352.64s)
requiring you to open a terminal. It can
[05:55] (355.04s)
also read output from terminal sessions,
[05:57] (357.44s)
list sessions, and processes and
[05:59] (359.44s)
terminate them as well. These features
[06:01] (361.44s)
help turn it into a fully autonomous
[06:03] (363.44s)
agent. Of course, it still supports all
[06:06] (366.16s)
the file system tools inherited from the
[06:08] (368.32s)
earlier server. On top of that, there is
[06:10] (370.64s)
a text edit tool designed for precise
[06:13] (373.44s)
text replacements. If you want to
[06:15] (375.36s)
replace a specific code block, you do
[06:17] (377.60s)
not need to rewrite the entire file
[06:19] (379.60s)
using the write file tool. The edit tool
[06:22] (382.00s)
can surgically replace just the parts
[06:23] (383.92s)
you want. There is also a usage example
[06:26] (386.40s)
provided. First, you specify the file
[06:29] (389.04s)
you want to change, then follow the
[06:31] (391.04s)
pattern they suggest, but honestly, that
[06:33] (393.52s)
part is optional. You can simply tell it
[06:35] (395.68s)
what to search for and what to replace
[06:37] (397.68s)
it with. Although the pattern might help
[06:39] (399.36s)
the LLM understand better. In the
[06:41] (401.20s)
example, it is replacing a console log
[06:43] (403.60s)
message with a new one. That is pretty
[06:45] (405.52s)
much it. Okay. So now I asked it to
[06:47] (407.76s)
create a directory in the developer
[06:49] (409.92s)
folder called image editor. Then I gave
[06:52] (412.40s)
it what you could call a PRD which is a
[06:54] (414.96s)
detailed prompt to build an image editor
[06:57] (417.52s)
using Nex.js with fast API and Python on
[07:00] (420.88s)
the back end. It is currently working
[07:03] (423.36s)
generating files checking everything and
[07:06] (426.08s)
I have already opened the project in VS
[07:08] (428.32s)
Code. This could easily be your new
[07:10] (430.08s)
replacement. You can open the code in VS
[07:12] (432.48s)
Code, inspect the files, make manual
[07:15] (435.20s)
edits if you want, and at the same time
[07:17] (437.36s)
use Claude code and Claude desktop to
[07:19] (439.60s)
build the app. Right now, it is
[07:21] (441.36s)
generating a project summary and has
[07:23] (443.52s)
already created the image editor web
[07:25] (445.44s)
app. The full structure is laid out.
[07:27] (447.68s)
Now, let us get it up and running and
[07:29] (449.44s)
see what it built and whether it works
[07:31] (451.44s)
as expected. I have started up the app
[07:34] (454.00s)
and I also wanted to show you that it
[07:36] (456.00s)
provided clear instructions on how to
[07:38] (458.08s)
run it, which is pretty simple. It even
[07:40] (460.32s)
added Docker support which is a nice and
[07:42] (462.72s)
efficient touch. Now this is the app it
[07:44] (464.72s)
built. I will admit that the UI is quite
[07:47] (467.04s)
basic but that is probably because I did
[07:49] (469.44s)
not ask it to use any specific
[07:51] (471.28s)
components like chat CN or anything more
[07:53] (473.84s)
advanced. Let us go ahead and choose a
[07:55] (475.84s)
file. I will use this one. It is the
[07:58] (478.16s)
thumbnail from my previous video. We
[08:00] (480.24s)
have some basic settings here. We can
[08:02] (482.24s)
crop although the manual crop is not
[08:04] (484.56s)
very useful at the moment. You can also
[08:06] (486.72s)
make adjustments and apply effects. It
[08:08] (488.96s)
looks like only grayscale, inversion and
[08:11] (491.12s)
blur are available. Let us start with
[08:13] (493.76s)
the horizontal
[08:17] (497.32s)
flip. You can see the image flipped
[08:19] (499.84s)
successfully. Now I will try converting
[08:21] (501.92s)
it to grayscale and it seems like that
[08:24] (504.16s)
part is not working. I just explained
[08:26] (506.56s)
the issue in claw desktop that the edits
[08:29] (509.04s)
were not applying consecutively and I
[08:31] (511.36s)
had to hit apply twice for them to take
[08:33] (513.44s)
effect. It resolved the problem and now
[08:35] (515.84s)
the updates happen in real time and
[08:38] (518.16s)
multiple edits work back to back. I
[08:40] (520.24s)
uploaded the same image again and now I
[08:42] (522.48s)
can apply any type of flip, convert it
[08:44] (524.64s)
to grayscale, apply hex and even rotate
[08:47] (527.60s)
it. All the edits are working smoothly.
[08:49] (529.60s)
In my opinion, this is a solid
[08:51] (531.20s)
alternative to cursor or wind surf,
[08:53] (533.12s)
especially if you already have a claw
[08:54] (534.80s)
desktop or clawed subscription. That
[08:56] (536.88s)
brings us to the end of this video. If
[08:58] (538.88s)
you would like to support the channel
[09:00] (540.24s)
and help us continue making tutorials
[09:02] (542.32s)
like this, you can do so by using the
[09:04] (544.48s)
super thanks button below. As always,
[09:06] (546.96s)
thank you for watching and I will see
[09:08] (548.88s)
you in the next