admin-mcp
MCP server management for Claude Desktop. Profile-aware - reads MCP server inventoryfrom profile.mcp.servers{} and config path from profile.paths.claudeConfig.Use when: installing MCP servers, configuring Claude Desktop, troubleshooting MCP issues.
When & Why to Use This Skill
The admin-mcp skill is a comprehensive management utility designed for Claude Desktop's Model Context Protocol (MCP) servers. It streamlines the lifecycle of MCP integrations by providing a profile-aware framework for installation, configuration, and troubleshooting. By automating manual JSON edits and providing diagnostic tools, it ensures a stable and extensible environment for developers looking to enhance Claude's capabilities with custom tools and data sources.
Use Cases
- Automated Server Installation: Quickly install and configure new MCP servers using NPX, global npm packages, or local source code with automated config backups.
- Inventory & Status Tracking: Maintain a clear overview of all installed MCP servers, including their operational status, tool counts, and versioning through a centralized profile.
- Configuration Management: Safely modify the Claude Desktop configuration file (claude_desktop_config.json) to manage environment variables, paths, and server arguments without manual errors.
- System Troubleshooting: Diagnose and resolve common MCP issues such as 'spawn ENOENT' errors, JSON syntax mistakes, and permission conflicts using built-in diagnostic patterns.
- Issue Lifecycle Tracking: Log and monitor specific MCP-related bugs or connectivity issues within the admin profile to maintain long-term system health.
| name | admin-mcp |
|---|---|
| description | | |
| Use when | installing MCP servers, configuring Claude Desktop, troubleshooting MCP issues. |
| license | MIT |
MCP Server Management
Requires: Node.js 18+, Claude Desktop
Profile-First Approach
MCP config and servers tracked in profile:
# Config file location
$AdminProfile.mcp.configFile
# "C:/Users/Owner/AppData/Roaming/Claude/claude_desktop_config.json"
# Installed servers
$AdminProfile.mcp.servers | Format-Table
jq '.mcp' "$ADMIN_PROFILE_PATH"
List MCP Servers
$AdminProfile.mcp.servers.PSObject.Properties | ForEach-Object {
[PSCustomObject]@{
Name = $_.Name
Package = $_.Value.package
Status = $_.Value.status
Tools = $_.Value.toolCount
}
}
Example output:
Name Package Status Tools
---- ------- ------ -----
win-cli D:/mcp/win-cli-mcp-server working 12
coolify @pashvc/mcp-server-coolify working 50
Config File Location
From profile:
$configPath = $AdminProfile.mcp.configFile
# Or
$configPath = $AdminProfile.paths.claudeConfig
# Read current config
$config = Get-Content $configPath | ConvertFrom-Json
$config.mcpServers
Install New MCP Server
Step 1: Backup Config
$configPath = $AdminProfile.mcp.configFile
$backup = "$configPath.backup.$(Get-Date -Format 'yyyyMMdd-HHmmss')"
Copy-Item $configPath $backup
Step 2: Add Server Entry
$config = Get-Content $configPath | ConvertFrom-Json
# NPX pattern (most common)
$config.mcpServers | Add-Member -NotePropertyName "new-server" -NotePropertyValue @{
command = "npx"
args = @("-y", "@some/mcp-server")
}
# Save
$config | ConvertTo-Json -Depth 10 | Set-Content $configPath
Step 3: Update Profile
$AdminProfile.mcp.servers["new-server"] = @{
name = "new-server"
package = "@some/mcp-server"
version = "1.0.0"
command = "npx -y @some/mcp-server"
configFile = $null
environment = @{}
status = "pending"
toolCount = 0
notes = "Just installed"
}
$AdminProfile | ConvertTo-Json -Depth 10 | Set-Content $AdminProfile.paths.deviceProfile
Step 4: Restart Claude Desktop
Close and reopen Claude Desktop, then verify tools appear.
Step 5: Update Status
$AdminProfile.mcp.servers["new-server"].status = "working"
$AdminProfile.mcp.servers["new-server"].toolCount = 15 # Count from Claude
$AdminProfile | ConvertTo-Json -Depth 10 | Set-Content $AdminProfile.paths.deviceProfile
Installation Patterns
NPX (Recommended)
{
"command": "npx",
"args": ["-y", "@package/mcp-server"]
}
Global npm
{
"command": "mcp-server-name"
}
Requires: npm install -g @package/mcp-server
Local Clone
{
"command": "node",
"args": ["D:/mcp/server-name/dist/index.js"]
}
With Environment Variables
{
"command": "npx",
"args": ["-y", "@package/mcp-server"],
"env": {
"API_KEY": "your-key",
"BASE_URL": "https://api.example.com"
}
}
Troubleshooting
Check Profile for Issues
# Known MCP issues
$AdminProfile.issues.current | Where-Object { $_.tool -like "*mcp*" }
Common Problems
| Error | Cause | Fix |
|---|---|---|
spawn ENOENT |
Command not found | Check path, install globally |
Server not starting |
Config syntax | Validate JSON |
Tools not appearing |
Didn't restart | Close/reopen Claude |
Permission denied |
Path issue | Use absolute Windows paths |
Diagnostics
# Check Node
node --version
# Check npm global
npm list -g --depth=0
# Validate config JSON
$configPath = $AdminProfile.mcp.configFile
try {
Get-Content $configPath | ConvertFrom-Json | Out-Null
Write-Host "Config JSON valid"
} catch {
Write-Host "Config JSON invalid: $_"
}
Track MCP Issue
$AdminProfile.issues.current += @{
id = "mcp-$(Get-Date -Format 'yyyyMMdd-HHmmss')"
tool = "mcp-server-name"
issue = "Server fails to start - spawn ENOENT"
priority = "high"
status = "pending"
created = (Get-Date).ToString("o")
}
$AdminProfile | ConvertTo-Json -Depth 10 | Set-Content $AdminProfile.paths.deviceProfile
Remove MCP Server
From Claude Config
$config = Get-Content $AdminProfile.mcp.configFile | ConvertFrom-Json
$config.mcpServers.PSObject.Properties.Remove("server-to-remove")
$config | ConvertTo-Json -Depth 10 | Set-Content $AdminProfile.mcp.configFile
From Profile
$AdminProfile.mcp.servers.PSObject.Properties.Remove("server-to-remove")
$AdminProfile | ConvertTo-Json -Depth 10 | Set-Content $AdminProfile.paths.deviceProfile
References
references/INSTALLATION.md- Detailed install patternsreferences/CONFIGURATION.md- Config file structurereferences/TROUBLESHOOTING.md- Common fixes