MCP is easier to understand if you stop treating it like "another AI plugin".
It is closer to a connection standard between an AI client and external tools.
The basic vocabulary:
- Host/client: Claude Desktop, Claude Code, Cursor, etc.
- MCP server: the program exposing tools or resources
- Tools: actions the assistant can request
- Resources: files, schemas or data the assistant can read
- Permissions: the part people should not skip
The safest beginner setup is read-only and narrow.
For example, if you expose a filesystem server, do not point it at your whole home directory. Point it at one project folder.
The progression I recommend:
- Understand what the server can read
- Test on a non-sensitive project
- Add one server at a time
- Observe suggested actions before enabling writes
- Disable anything you do not understand
I wrote a French guide for GoGoKodo that explains MCP with Claude, local servers, common mistakes and when it becomes useful for developers:
Top comments (0)