Tech • AI • Robotics • Game
How Complete Beginners Master Claude Code MCP in 19 Minutes
7/10TL;DR
Model Context Protocol lets Claude connect live to local folders and hosted services such as Notion, reducing manual copy-paste workflows and enabling one prompt to act across multiple systems.
KEY POINTS
What MCP does
MCP, short for Model Context Protocol, is a standard for connecting Claude to external tools, databases, APIs and documents. Instead of relying only on text pasted into a chat, it can access approved sources directly and use them during a conversation. The key distinction is that this is a live connection, not code generated for later use.
Two server types matter
MCP servers generally fall into two categories: local servers that run on a user’s computer, and hosted servers that run online. Local servers are added through a JSON configuration file, while hosted servers are connected through Settings and Connectors, usually by pasting a URL and signing in. Confusing those two paths is a common cause of failed setups.
How local setup works
In Claude Desktop, the local MCP configuration can be opened through File, Settings, Developer, and Edit Settings. If the file does not yet exist, the app creates it. Each local server entry includes a server name, a command, arguments, and sometimes environment variables for credentials.
Windows users face a common trap
On Windows, any local MCP server launched through NPX needs a CMD wrapper. The command should be cmd, with arguments beginning /c and npx. Using npx directly as the command can trigger a spawn error in which the server appears registered but never actually connects.
File system access is limited by folder path
A practical first example is the file system server, which requires no account or API token. Once added to the config, it allows Claude to read and create files only inside the explicitly approved folder path. That path acts as a hard boundary, meaning the rest of the computer remains inaccessible.
Restarting is required
After changing the local config, users must fully quit Claude Desktop and reopen it. Simply closing the window is not enough because the application only reads the configuration at startup. Once restarted, users can ask which tools are available and verify that file system tools are loaded.
Testing local tools proves the connection
A proper test includes asking Claude to list files in the approved folder, read one of them, and create a new file. The result can then be verified in Windows Explorer. That confirms the system is interacting with a real directory rather than summarizing uploaded content.
Hosted Notion setup follows a different path
Notion uses a hosted MCP server and is not added through the JSON file. Instead, users go to Settings, open Connectors, add a custom connector, paste the Notion MCP URL, and complete the browser sign-in flow. This option requires a Pro, Max, Team, or Enterprise plan and is unavailable on the free tier.
Live Notion access avoids stale exports
Once authorized, Claude can read documents from a live Notion workspace using the same account permissions already in place. That removes the need to export pages, generate separate API tokens, or manually share individual pages. It also avoids the problem of working from outdated file snapshots when documents are frequently updated.
One prompt can fan out to multiple systems
With both the file system server and Notion active, a single prompt can trigger a combined workflow. A sample task involved researching a topic, saving the findings to a local file, and creating a matching Notion page. The research was performed once and then written to two destinations, a pattern often described as fan out.
The most frequent errors are easy to classify
Broken local commands usually show a clear disconnection error, while invalid JSON can prevent the settings file from loading and may reset it to defaults. A missing comma can therefore wipe out a working setup, making backups important. The most confusing failure is silent: placing a hosted service like Notion in the local config produces no useful warning and simply never appears.
CONCLUSION
The practical rule is simple: if an MCP server runs on the local machine, it belongs in the config file; if it runs online, it belongs under connectors. Once both are set up correctly, Claude can move information across real tools and documents with far less manual work.
Ask a question