As focus continues to shift toward Claude Code, it’s becoming best practice for everyone to get comfortable using it—whether from the terminal or through a GUI. Some people, myself included, prefer working directly in the terminal, while many others are more comfortable with a graphical interface. For those who prefer a GUI, you can use Claude Code within common development environments such as: 1. VS Code 2. Cursor Once you have Claude Code set up in your preferred environment, the next step is to extend its capabilities by connecting it to MCP servers. At this point, a common question comes up: Why is this necessary? If Claude Code is an AI agent, shouldn’t it already have all the capabilities of an agent? That’s a fair question. In reality, whether you’re using an AI agent or a standard LLM, none of them can automatically connect to external tools or systems unless that access is explicitly configured and permitted. Tool usage is never implicit—it must be intentionally enabled. This is where MCP servers come in. They provide the bridge that allows Claude Code to safely and reliably interact with external tools. For those of us who don’t have the funds to subscribe to Claude Code, there’s still a good alternative. You can use Claude Desktop for this setup, with some rate limitations. While the free tier has constraints, you can still achieve a Claude Code–like experience, especially for learning and experimentation. It’s also worth noting that the process for setting up MCP servers is largely the same whether you’re using Claude Code or Claude Desktop, so the knowledge transfers directly between both. There are two main ways to set this up: 1. GUI approach using Docker Desktop This is the simplest option. You can run MCP servers through Docker Desktop without manually editing configuration files—Docker handles most of the setup for you. 2. Node.js (CLI) approach Alternatively, you can use Node.js (for example, via npx) and register the MCP server by adding a JSON-formatted configuration entry to your Claude Code configuration file.

Now everyone is talking about Nanobot. Okay … maybe one guy on My LinkedIn feed so far …