Server
Configure, deploy, and troubleshoot web servers, application servers, and containerized services.
Best use case
Server is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure, deploy, and troubleshoot web servers, application servers, and containerized services.
Teams using Server 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/server/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Server Compares
| Feature / Agent | Server | 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?
Configure, deploy, and troubleshoot web servers, application servers, and containerized services.
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
## Scope This skill covers the **software layer** — what runs inside a machine. For infrastructure (provisioning VMs, SSH hardening, firewalls, backups), use the `vps` skill. ## When to Use - Configuring nginx, Caddy, or Apache - Deploying Node.js, Python, Go, or other apps - Docker and Docker Compose setups - SSL/TLS certificates with Let's Encrypt - Reverse proxy and load balancing - Process management (pm2, systemd services) - Troubleshooting port conflicts, CORS, connection errors - Self-hosting (Plex, Nextcloud, game servers) - Local development servers (Vite, webpack-dev-server) ## Common Pitfalls - **Port already in use** — Check with `lsof -i :PORT` or `ss -tlnp | grep PORT`, kill stale processes - **CORS in development** — Proxy through your dev server or configure backend headers, don't disable in production - **SSL certificate issues** — Certbot needs port 80/443 open, use `--standalone` or `--webroot` mode appropriately - **nginx config not loading** — Always run `nginx -t` before `systemctl reload nginx` - **Docker container can't reach host** — Use `host.docker.internal` (Docker Desktop) or `172.17.0.1` (Linux) - **Process dies after SSH disconnect** — Use systemd, pm2, or run inside tmux/screen - **Wrong permissions on mounted volumes** — Match container user UID with host file ownership ## Patterns by Use Case | Use Case | Recommended Stack | |----------|-------------------| | Static site | Caddy (auto-SSL, zero config) | | Node.js app | PM2 + nginx reverse proxy | | Python (Django/FastAPI) | Gunicorn + nginx | | Multiple services | Docker Compose + Traefik | | Game server | Dedicated container + port mapping | For framework-specific configs, see `configs.md`. For Docker Compose patterns, see `docker.md`. ## Debugging Checklist 1. **Is the process running?** `systemctl status` or `docker ps` 2. **Is it listening?** `ss -tlnp | grep PORT` 3. **Can you reach it locally?** `curl localhost:PORT` 4. **Firewall blocking?** Check `ufw status` or cloud security groups 5. **Reverse proxy misconfigured?** Check nginx logs: `/var/log/nginx/error.log` 6. **DNS pointing correctly?** `dig domain.com` or `nslookup`
Related Skills
ssh-server-admin
Securely connect to and manage remote Linux/Unix servers via SSH. Execute commands, transfer files (SCP/SFTP), set up port forwarding and tunnels. Use when the user asks to SSH into a server, connect to a remote machine, run remote commands, upload/download files to servers, set up tunnels, or perform server administration tasks. Works on Windows, macOS, and Linux.
sql-server-dba-dev-expert
Use when designing, implementing, optimizing, or troubleshooting AF.ECT.Database schemas, queries, stored procedures, performance tuning, data integrity, or operational database tasks while following Microsoft best practices
mcpserver-migrate-mcpapps
Migrates an MCP server with interactive widgets from the OpenAI Apps SDK (window.openai, text/html+skybridge) to the MCP Apps standard (@modelcontextprotocol/ext-apps), covering server-side and client-side changes.
mcp-server-evaluations
Test MCP servers for quality and reliability. Verify tool functionality, test error handling, generate tests, and assess response quality with no dependencies other than curl. Use this when validating MCP server implementations, testing OpenAPI-to-MCP conversions, or assessing API tool quality.
hytaleservers-workflow
Standard workflow for HyTaleServers.tech development
copilot-mcp-server
Direct access to GitHub Copilot MCP server tools for AI-powered development assistance
azure-communication-callingserver-java
Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...
aws-serverless-eda
AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions, EventBridge, SQS, SNS, and serverless patterns. Essential when user mentions serverless, Lambda, API Gateway, event-driven, async processing, queues, pub/sub, or wants to build scalable serverless applications with AWS best practices.
apollo-server-patterns
Use when building GraphQL APIs with Apollo Server requiring resolvers, data sources, schema design, and federation.
agentstack-server-debugging
Instructions for debugging agentstack-server during development
a2a-server-config
Agent-to-Agent (A2A) server configuration patterns for HTTP, STDIO, SSE, and WebSocket transports. Use when building A2A servers, configuring MCP transports, setting up server endpoints, or when user mentions A2A configuration, server transport, MCP server setup, or agent communication protocols.
dev-server-sandbox
Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)