Verifying the Installation
After deploying the MCP stack, verify everything is working correctly.
Health Check Script
Run the built-in health check:
bash scripts/health-check.sh
This checks the status of all Docker containers and reports any that are not running.
Expected output shows all containers as "running":
✓ ubuntu-mcp: running
✓ obsidian-mcp: running
✓ synology-mcp: running
✓ github-mcp: running
✓ mcp-webui: running
✓ docs-site: running
Manual Container Check
docker compose ps
All services should show Up status. If any show Exited or Restarting, check the logs:
docker compose logs <service-name>
Web UI Access
- Navigate to
http://<your-server>:8280 - You should see the login page
- Log in with the
WEBUI_API_KEYfrom your.envfile - The dashboard should show all server cards
If the login fails:
- Verify
WEBUI_API_KEYmatches exactly in.envand what you're typing - Check the
mcp-webuicontainer logs:docker compose logs mcp-webui - Ensure the port mapping is correct in
docker-compose.yml
Testing MCP Connectivity
Test SSH Connection
From your local machine, verify SSH access to the server works:
ssh <UBUNTU_SERVER_USER>@<UBUNTU_SERVER_HOST>
Test Docker Exec
Once SSH'd into the server, test that docker exec works for each MCP:
# Test Ubuntu MCP
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | \
docker exec -i ubuntu-mcp python -m ubuntu_mcp
A successful response lists all 12 tools with their schemas.
# Test Obsidian MCP
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | \
docker exec -i obsidian-mcp python -m obsidian_mcp
Test from Claude Code
Add the MCP servers to your ~/.claude/settings.json (see Connecting Claude Code) and restart Claude Code. In Claude Code, ask:
List the available tools for the ubuntu-server MCP
Claude should list all 12 Ubuntu MCP tools.
Permission Check
- Open the Web UI dashboard
- Click on a server card (e.g., Ubuntu Server)
- Verify you see path and command permission tables
- The default config should show at least one path rule and one command rule
If the page shows "No config":
- Ensure the configs directory is mounted correctly:
ls -la configs/ - Check the YAML files exist:
ls configs/ubuntu-server.yaml - Verify the volume mount in
docker-compose.yml
Audit Log Check
- In the Web UI, navigate to a server's detail page
- Scroll to the Audit Log section
- After making any MCP request from Claude Code, new entries should appear
- Audit log files are at
/var/log/mcp/<server>/audit.logon the host
Common Startup Issues
Container exits immediately
Check the logs for the failing container:
docker compose logs <service-name>
Common causes:
- Missing
.envvariables (checkSYNOLOGY_NAS_HOST,OBSIDIAN_VAULT_PATH) - Incorrect volume mount paths
- Docker socket permission issues (
/var/run/docker.sock)
Port already in use
If port 8280 or 3000 is already bound:
# Find what's using the port
sudo lsof -i :8280
# Change the port in .env
WEBUI_PORT=8281
Permission denied on volume mounts
Ensure the directories exist and have correct permissions:
sudo mkdir -p /var/log/mcp/{ubuntu,obsidian,synology,github}
sudo chown -R 1000:1000 /var/log/mcp
Synology connection fails
Verify NAS connectivity from the Docker host:
curl -k https://<SYNOLOGY_NAS_HOST>:<SYNOLOGY_NAS_PORT>/webapi/query.cgi?api=SYNO.API.Info&version=1&method=query
Next Steps
- Connect Claude Code to start using the MCP servers
- Configure permissions to control access
- Explore the Web UI guide for managing everything graphically