Skip to content

Commit 5ce3d70

Browse files
다국어 지원 개선 및 언어 전환 로직 최적화
- UI에 번역이 없는 경우 홈페이지로 리디렉션하는 메시지 추가 - 언어 전환 로직 개선: 페이지 타입에 따라 적절한 URL 생성 - CSS 스타일링 업데이트: 고정 헤더 및 콘텐츠 영역 마진 조정 - Highlight.js 추가 및 초기화 스크립트 작성으로 코드 하이라이팅 지원 - 번역이 없는 언어 옵션에 대한 시각적 표시 추가
1 parent 6757734 commit 5ce3d70

4 files changed

Lines changed: 820 additions & 0 deletions
Lines changed: 215 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,215 @@
1+
---
2+
layout: post
3+
title: "Easy MCP Installation Using Existing MCPs - Practical Guide for Installing Playwright MCP"
4+
date: 2025-06-05 14:30:00 +0900
5+
categories: [Tips, Development]
6+
tags: [mcp, playwright, automation, installation, filesystem, desktop-commander, beginner]
7+
author: "Kevin Park"
8+
excerpt: "Learn practical methods for Claude to automatically install new MCPs using already installed filesystem and desktop-commander MCPs."
9+
lang: en
10+
---
11+
12+
# Easy MCP Installation Using Existing MCPs - Practical Guide for Installing Playwright MCP
13+
14+
## 🎯 Summary
15+
16+
**By leveraging already installed MCPs like filesystem and desktop-commander, Claude can directly install new MCP servers without manual installation.**
17+
18+
### Core Installation Command
19+
20+
```
21+
Request to Claude:
22+
"Install playwright MCP server and add it to the configuration file"
23+
```
24+
25+
### Automated Process
26+
- **Automatic Configuration File Editing**: Edit claude_desktop_config.json using filesystem MCP
27+
- **Automatic Dependency Installation**: Execute NPX commands via desktop-commander
28+
- **Configuration Validation**: Content verification and syntax checking
29+
- **Restart Guidance**: Claude Desktop restart guide
30+
31+
### Installing Multiple MCPs at Once
32+
```
33+
"Install and configure GitHub, Google Drive, and Playwright MCPs all at once"
34+
```
35+
36+
---
37+
38+
## 📚 Detailed Explanation
39+
40+
### Why Use Existing MCPs
41+
42+
When you already have MCPs like filesystem and desktop-commander installed, Claude can directly:
43+
- Access the file system to modify configuration files
44+
- Execute terminal commands to install packages
45+
- Validate configurations and troubleshoot issues
46+
47+
All these processes can be automated.
48+
49+
### Actual Installation Process
50+
51+
#### Step 1: Request Installation from Claude
52+
53+
```
54+
"Install playwright-mcp. Also automatically modify the configuration file"
55+
```
56+
57+
Tasks Claude automatically performs:
58+
1. Read current claude_desktop_config.json file
59+
2. Add playwright MCP configuration
60+
3. Verify dependencies with NPX
61+
4. Save configuration file
62+
63+
#### Step 2: Automatic Configuration File Modification
64+
65+
Claude uses filesystem MCP to modify as follows:
66+
67+
```json
68+
{
69+
"mcpServers": {
70+
"filesystem": {
71+
"command": "npx",
72+
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/username/Documents"]
73+
},
74+
"desktop-commander": {
75+
"command": "npx",
76+
"args": ["-y", "@executeautomation/desktop-commander-mcp"]
77+
},
78+
"playwright": {
79+
"command": "npx",
80+
"args": ["@playwright/mcp@latest"]
81+
}
82+
}
83+
}
84+
```
85+
86+
#### Step 3: Dependency Installation Verification
87+
88+
Claude executes via desktop-commander:
89+
```bash
90+
npx @playwright/mcp@latest --help
91+
```
92+
93+
### Recommended MCP Server List
94+
95+
Useful MCPs you can request Claude to install all at once:
96+
97+
```
98+
"Install all of the following MCPs:
99+
- GitHub MCP (code repository management)
100+
- Google Drive MCP (file synchronization)
101+
- Slack MCP (message management)
102+
- Brave Search MCP (web search)
103+
- Playwright MCP (browser automation)"
104+
```
105+
106+
### Installation Validation Methods
107+
108+
#### Automatic Validation Request
109+
```
110+
"Check if the installed MCPs are working properly"
111+
```
112+
113+
Validation performed by Claude:
114+
1. Configuration file JSON syntax checking
115+
2. Test execution of each MCP server
116+
3. Verify required dependency installation
117+
4. Check permission settings
118+
119+
#### Manual Validation Method
120+
1. Completely restart Claude Desktop
121+
2. Click "Allow for This Chat" in new chat
122+
3. Simple test request: "Show me the file list in the current directory"
123+
124+
### Practical Usage Tips
125+
126+
#### 1. Project-Specific MCP Configuration
127+
128+
```
129+
"Recommend and install MCPs suitable for the current project"
130+
```
131+
132+
Web Development Project:
133+
- Playwright (browser testing)
134+
- GitHub (code management)
135+
- Filesystem (file operations)
136+
137+
Data Analysis Project:
138+
- Filesystem (data file access)
139+
- Google Drive (data synchronization)
140+
- Desktop Commander (script execution)
141+
142+
#### 2. Batch Installation Script
143+
144+
```
145+
"Configure MCP environment with the following setup:
146+
1. Development MCPs: GitHub, Filesystem, Playwright
147+
2. Business MCPs: Slack, Google Drive, Calendar
148+
3. Utility MCPs: Desktop Commander, Brave Search"
149+
```
150+
151+
#### 3. Configuration Backup and Restore
152+
153+
```
154+
"Backup current MCP configuration"
155+
"Apply backed up MCP configuration to a new computer"
156+
```
157+
158+
### Troubleshooting Guide
159+
160+
#### Common Issues
161+
162+
**1. NPX Cache Issues**
163+
```
164+
"Clear NPX cache and reinstall MCP"
165+
```
166+
167+
**2. Permission Issues**
168+
```
169+
"Check and fix MCP configuration file permissions"
170+
```
171+
172+
**3. Port Conflicts**
173+
```
174+
"Check ports in use and change MCP port"
175+
```
176+
177+
#### Advanced Troubleshooting
178+
179+
**Configuration File Recovery**
180+
```
181+
"The MCP configuration file is corrupted. Please restore from backup"
182+
```
183+
184+
**Selective MCP Deactivation**
185+
```
186+
"Temporarily disable only the Playwright MCP"
187+
```
188+
189+
### Performance Optimization Tips
190+
191+
#### 1. Keep Only Necessary MCPs Active
192+
```json
193+
{
194+
"mcpServers": {
195+
// Keep only frequently used ones
196+
"filesystem": { ... },
197+
"playwright": { ... }
198+
// Comment out unused MCPs
199+
// "heavy-mcp": { ... }
200+
}
201+
}
202+
```
203+
204+
#### 2. Resource Usage Monitoring
205+
```
206+
"Check resource usage of currently running MCP servers"
207+
```
208+
209+
## Conclusion
210+
211+
Using existing MCP tools makes installing new MCPs very simple. Since Claude automates everything from file system access to dependency installation, developers can focus on actually using the features instead of complex installation processes.
212+
213+
**Key Tip**: Simply request "install it" and Claude will automatically install and complete the configuration in the optimal way.
214+
215+
**Next Steps**: Build workflow automation using the installed MCPs.

0 commit comments

Comments
 (0)