admin-mcp
MCP server management for Claude Desktop. Profile-aware - reads MCP server inventory from profile.mcp.servers{} and config path from profile.paths.claudeConfig. Use when: installing MCP servers, configuring Claude Desktop, troubleshooting MCP issues.
Best use case
admin-mcp is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
MCP server management for Claude Desktop. Profile-aware - reads MCP server inventory from profile.mcp.servers{} and config path from profile.paths.claudeConfig. Use when: installing MCP servers, configuring Claude Desktop, troubleshooting MCP issues.
Teams using admin-mcp should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/admin-mcp/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How admin-mcp Compares
| Feature / Agent | admin-mcp | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
MCP server management for Claude Desktop. Profile-aware - reads MCP server inventory from profile.mcp.servers{} and config path from profile.paths.claudeConfig. Use when: installing MCP servers, configuring Claude Desktop, troubleshooting MCP issues.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# MCP Server Management
**Requires**: Node.js 18+, Claude Desktop
---
## Profile-First Approach
MCP config and servers tracked in profile:
```powershell
# Config file location
$AdminProfile.mcp.configFile
# "C:/Users/Owner/AppData/Roaming/Claude/claude_desktop_config.json"
# Installed servers
$AdminProfile.mcp.servers | Format-Table
```
```bash
jq '.mcp' "$ADMIN_PROFILE_PATH"
```
---
## List MCP Servers
```powershell
$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:
```powershell
$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
```powershell
$configPath = $AdminProfile.mcp.configFile
$backup = "$configPath.backup.$(Get-Date -Format 'yyyyMMdd-HHmmss')"
Copy-Item $configPath $backup
```
### Step 2: Add Server Entry
```powershell
$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
```powershell
$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
```powershell
$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)
```json
{
"command": "npx",
"args": ["-y", "@package/mcp-server"]
}
```
### Global npm
```json
{
"command": "mcp-server-name"
}
```
Requires: `npm install -g @package/mcp-server`
### Local Clone
```json
{
"command": "node",
"args": ["D:/mcp/server-name/dist/index.js"]
}
```
### With Environment Variables
```json
{
"command": "npx",
"args": ["-y", "@package/mcp-server"],
"env": {
"API_KEY": "your-key",
"BASE_URL": "https://api.example.com"
}
}
```
---
## Troubleshooting
### Check Profile for Issues
```powershell
# 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
```powershell
# 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
```powershell
$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
```powershell
$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
```powershell
$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 patterns
- `references/CONFIGURATION.md` - Config file structure
- `references/TROUBLESHOOTING.md` - Common fixesRelated Skills
administration
How to monitor usage, track costs, configure analytics, and measure ROI for Claude Code. Use when user asks about monitoring, telemetry, metrics, costs, analytics, or OpenTelemetry.
administering-linux
Manage Linux systems covering systemd services, process management, filesystems, networking, performance tuning, and troubleshooting. Use when deploying applications, optimizing server performance, diagnosing production issues, or managing users and security on Linux servers.
admin
Admin panel - RBAC, config, admin tools. Use when building admin UI.
admin-wsl
WSL2 Ubuntu administration from Linux side. Profile-aware - reads preferences from Windows-side profile at /mnt/c/Users/{WIN_USER}/.admin/profiles/{hostname}.json Use when: Inside WSL for apt packages, Docker, Python/uv, shell configs, systemd. Coordinates with admin-windows via shared profile ON THE WINDOWS SIDE.
admin-windows
Windows system administration with PowerShell 7.x. Profile-aware - reads your preferences for package managers (scoop vs winget), paths, and installed tools. Use when: Windows-specific admin tasks, PowerShell automation, PATH configuration, package installation, bash-to-PowerShell translation.
admin-unix
Native macOS and Linux administration (non-WSL). Profile-aware - reads preferences from ~/.admin/profiles/{hostname}.json. Use when: macOS/Linux system admin, Homebrew (macOS), apt (Linux), services. NOT for WSL - use admin-wsl instead.
admin-panel-builder
Expert assistant for creating and maintaining admin panel pages in the KR92 Bible Voice project. Use when creating admin pages, building admin components, integrating with admin navigation, or adding admin features.
admin-interface-rules
Rules for the Admin interface functionalities
admin-infra-vultr
Deploys infrastructure on Vultr with Cloud Compute instances, High-Frequency servers, and VPCs. Excellent value with Kubernetes autoscaling support and global data centers. Use when: setting up Vultr infrastructure, deploying cloud compute or high-frequency instances, configuring firewalls, needing good price/performance with global reach. Keywords: vultr, vultr-cli, VPS, cloud compute, high-frequency, firewall, VPC, kubernetes autoscale, infrastructure
admin-infra-oci
Deploys infrastructure on Oracle Cloud Infrastructure (OCI) with ARM64 instances (Always Free tier eligible). Handles compartments, VCNs, subnets, security lists, and compute instances. Use when: setting up Oracle Cloud infrastructure, deploying ARM64 instances, troubleshooting OUT_OF_HOST_CAPACITY errors, optimizing for Always Free tier. Keywords: oracle cloud, OCI, ARM64, VM.Standard.A1.Flex, Always Free tier, OUT_OF_HOST_CAPACITY, oci compartment, oci vcn
admin-infra-linode
Deploys infrastructure on Linode (Akamai Cloud) with Linodes, Firewalls, and VLANs. Strong Kubernetes support with Cluster Autoscaler and Akamai edge network integration. Use when: setting up Linode/Akamai infrastructure, deploying Linodes, configuring firewalls, needing Kubernetes autoscaling, wanting Akamai CDN integration. Keywords: linode, akamai, linode-cli, VPS, dedicated CPU, firewall, VLAN, kubernetes autoscale, infrastructure
admin-infra-hetzner
Deploys infrastructure on Hetzner Cloud with ARM64 or x86 servers. Cost-effective European cloud with excellent price/performance ratio. Use when: setting up Hetzner Cloud infrastructure, deploying ARM64 servers (CAX), x86 servers (CX/CPX), looking for affordable alternative to OCI. Keywords: hetzner, hcloud, ARM64, CAX, CX, CPX, infrastructure, server setup, european cloud