Model Context Protocol | The How | How to connect MCP Servers to Claude Desktop | CampusX

The practical takeaway: Claude Desktop can connect to multiple MCP servers—both local and remote—either through one-click “connectors” (for common SaaS tools) or via manual JSON configuration (for custom or less common servers). That dual approach matters because it lets teams move fast with ready-made integrations while still retaining the freedom to run their own MCP servers when they need specialized capabilities.

The walkthrough starts by setting expectations for a three-part “How” series. Today’s focus is the “how” of MCP communication between a client and servers, using Claude Desktop as the client and existing MCP servers as the targets. The plan is to install Claude Desktop, then connect it to four MCP servers: two local servers and two remote servers. The local pair includes a File System MCP server (for manipulating specific directories on the machine) and a Manim MCP server (for generating math visualizations). The remote pair includes a Google Drive MCP server (for reading documents from Google Drive) and a Twitter/X MCP server (for searching and posting tweets).

A key concept introduced is how Claude Desktop connects to MCP servers. The default method uses a JSON configuration file inside the AI host (Claude Desktop), where server details are added manually. The alternative method uses “connectors,” a built-in Claude feature that links Claude Desktop to MCP servers automatically—without editing JSON. Connectors handle the behind-the-scenes work such as authentication, API keys, and secure sign-in flows, which reduces setup friction for non-technical users and improves consistency compared with manual configuration. The tradeoff is that connectors are curated and managed by Anthropic’s team, mainly around widely used SaaS tools. Because MCP is an open standard that allows anyone to build clients and servers, forcing every MCP server to rely on Anthropic-managed connectors would close the ecosystem and create a bottleneck.

The File System MCP server demo shows how connectors work in practice: after installing the connector and granting access to specific directories (not the entire computer), Claude Desktop asks for permission before using the tool. A search for PDFs on the desktop returns results only after the user allows access, and Claude can also write files—demonstrated by generating a Python file and then verifying it exists on disk. The emphasis is on safety: access is scoped to approved folders, and users can add more directories only if they choose.

Next comes the Manim MCP server, which is treated as a local server without a ready-made connector. Setup requires installing dependencies (Python, MCP, Manim), cloning the repository, and then manually wiring the server into Claude Desktop’s JSON config. The payoff is a workflow where a user writes a high-level English prompt for a math concept, Claude generates the Manim code, executes it, and returns a visualization video—similar to the style of the “3Blue1Brown” channel. A practical caveat appears: perfect rendering may require LaTeX, and missing LaTeX can degrade mathematical symbol output.

For remote tools, the Google Drive MCP server connects via a direct connector and supports read-only operations—summarizing a document from Drive is shown, but creating or editing files is not. The Twitter/X MCP server setup is more involved: it requires adding configuration into Claude Desktop’s JSON, supplying API keys and access tokens, and then testing both tweet search and posting. Posting may fail if the account lacks proper authorization or permissions, though reading can still work.

Finally, a Weather MCP server is configured as a remote-style integration using a code path that runs on a different environment (via UVX), and the demo ends with an API/tool error that appears machine-specific. The session closes with guidance on discovering additional MCP servers: search for “awesome MCP servers” to find a curated, updated list on GitHub, plus other marketplaces and listing sites for further exploration.