Knowledge
Claude Simplified: The Truth Behind the Complexity — Hands-On MCP Setup in Practice Part 3
If you’ve grasped the concepts in parts 1 and 2, part 3 is hands-on practice. From installation to MCP connection, we’ll complete it without any obstacles.
1. Installation — You Only Need 2 Things
1-1. Install Node.js First
Claude Code runs on Node.js. You need to install it first if you don’t have it.
→ nodejs.org → Download LTS version → Install
node –version
# v20.x.x or higher is OK
1-2. Install Claude Code — One Line Done
npm install -g @anthropic-ai/claude-code
claude –version
# Complete when version number appears
That’s all. No separate program installation needed.
2. When You First Launch — Just Learn 10 Commands
Navigate to your project folder and type claude to start. These commands solve everything.
2-1. Basic Status Check Commands
| Command | Function | When to Use |
|---|---|---|
/status |
Check login status, plan, usage | Habitually when first launching |
/mcp |
Check list of connected MCP servers | Verify MCP is properly connected |
/permissions |
Check and edit allowed tools list | When permission errors occur |
/memory |
Check and edit CLAUDE.md content | When changing project settings |
/doctor |
Diagnose entire installation environment | First thing when something seems wrong |
2-2. Workflow Commands
| Command | Function | When to Use |
|---|---|---|
/clear |
Initialize current conversation context | When switching tasks, when response is odd |
/compact |
Compress conversation (save tokens) | When conversation gets long |
/resume |
Resume from previous session | When continuing yesterday’s work |
/review |
Review work just completed | When validating results |
/bug |
Report Claude Code bug | When Claude Code malfunctions |
Actually, the most frequently used are /status, /mcp, /clear — these 3. Use the rest when needed.
3. CLAUDE.md Practical Template
Create a CLAUDE.md file in your project root folder and paste the content below.
3-1. For 3D Artists (Blender)
# Project Settings
– This project is for Blender 3D automation
– Blender version: 4.x
– Python 3.11 used
# Work Rules
– Save all output files to /outputs folder
– Save texture files to /textures folder
– Use lowercase English + underscore for filenames
# Communication
– Explain in Korean
– Always confirm save status after completing task
3-2. For Automation Pipeline
# Project Settings
– Content automation pipeline project
– Python 3.11 used
# Work Rules
– Save logs to /logs folder by date
– Never put API keys directly in code, use .env file
– Send Telegram notification when error occurs
# Communication
– Explain in Korean
– Always show execution plan first before working
“Always show execution plan first before working” — This one line drastically reduces mistakes.
4. 3 Recommended MCP Servers
4-1. GitHub MCP
claude mcp add github — npx -y @modelcontextprotocol/server-github
“Show me today’s new issues list.”
“Analyze ISSUE-42 and create fix proposal.”
“Write PR draft from current branch changes.”
4-2. Filesystem MCP
claude mcp add filesystem — npx -y @modelcontextprotocol/server-filesystem /Users/yourname/Documents
“Show files modified today in Documents folder.”
“Create backup folder and copy important files.”
4-3. Blender MCP
claude mcp add blender — npx -y @ahujasid/blender-mcp
※ Blender must be running first.
“Show me the object list in current scene.”
“Unwrap UV of selected mesh.”
“Adjust camera position and render.”
5. 2 Common Roadblocks
5-1. When MCP Connection Fails
Try this first:
claude –mcp-debug
With this option, the entire MCP connection process is visible. You’ll immediately see where it’s stuck.
✔ Verify Node.js version is 20 or higher (node --version)
✔ Options must be written before server name
✔ /mcp shows server exists but 0 tools → Server itself has issues
5-2. When Permission Errors Occur
Claude Code asks permission before modifying files or executing commands each time. If you’re tired of clicking every time, you can pre-allow in /permissions.
Edit → Always allow file editing
Bash(git commit:*) → Always allow git commit
mcp__blender__* → Allow entire Blender MCP
I recommend checking one by one and allowing individually at first. If you don’t know what you allowed, it’s hard to find later when problems occur.
6. Summary
| Item | Key Point |
|---|---|
| Installation | Node.js → Claude Code one line, done |
| Essential Commands | /status, /mcp, /clear — these 3 cover 80% |
| CLAUDE.md | Key is one line: “Show execution plan first” |
| MCP Start | GitHub → Filesystem → Blender in order |
| Error Resolution | Start with –mcp-debug, cause immediately visible |
7. Next Episode Preview
Part 4 is a practical automation pipeline.
✔ How to run Claude as a 24-hour agent
✔ Connect Telegram / Discord to auto-respond to external events
✔ Attach scheduler to run automatically daily
If you get stuck during installation, leave it in the comments. Also let me know which MCP you’re more curious about.
Complex Claude, Actually This Simple — Complete MCP Beginner’s Guide Part 1
Complex Claude, Actually This Simple — Complete Skills Organization Part 2