High-Command: High-Command API MCP Server

A Model Context Protocol (MCP) server for seamless integration with the High-Command API. This project provides tools and resources to access real-time Helldivers 2 game data through a comprehensive, dedicated game data API.

Features

• 🔌 MCP Server: Full Model Context Protocol implementation with HTTP and Stdio transports
• 🎮 High-Command API: Direct access to game data (war status, campaigns, planets, biomes, factions, statistics)
• 📦 Async/Await: Built with modern async Python and httpx
• 🐳 Docker Support: Easy containerization with multi-stage builds
• 🧪 Comprehensive Tests: 17 tests, 50% coverage
• 📚 Documentation: Complete API and usage documentation
• 🔄 CI/CD: GitHub Actions workflows for testing and Docker builds
• ⚙️ Configurable: Environment-based configuration for API endpoints and logging

Quick Start

Prerequisites

• Python 3.14.0+
• pip or uv
• Docker (optional)

Installation

# Clone the repository
git clone https://github.com/yourusername/high-command.git
cd high-command

# Install dependencies
make install

# Install development dependencies
make dev

Running the Server

# Run with make
make run

# Or with Docker
make docker-run

# Or directly
python -m highcommand.server

Running Tests

# Run all tests with coverage
make test

# Run tests quickly without coverage
make test-fast

# Run specific test file
pytest tests/test_api_client.py -v

Code Quality

# Format code
make format

# Run linters
make lint

# Run all checks
make check

� Docker & Kubernetes Support

Docker

# Build image
make docker-build

# Run container
make docker-run

# Or manually
docker build -t high-command:latest .
docker run -p 8000:8000 high-command:latest

Kubernetes

High-Command supports HTTP/SSE transport for Kubernetes deployments:

# Install with Kubernetes support
pip install high-command[kubernetes]

# Deploy to cluster
kubectl apply -f k8s/rbac.yaml
kubectl apply -f k8s/deployment.yaml
kubectl apply -f k8s/service.yaml
kubectl apply -f k8s/hpa.yaml

# Check status
kubectl get pods -l app=high-command
kubectl port-forward svc/high-command 8000:80

Note: Kubernetes deployment manifests are available in the k8s/ directory. Configure them according to your cluster setup.

�💻 VS Code Integration

The High-Command MCP server integrates seamlessly with VS Code and GitHub Copilot.

Setup

1. Install dependencies:

   make dev

2. Add to VS Code MCP config (~/.config/Code/User/mcp.json):

   {
     "servers": {
       "high-command": {
         "type": "stdio",
         "command": "/full/path/to/python",
         "args": ["-m", "highcommand.server"],
         "cwd": "/path/to/high-command-mcp"
       }
     }
   }

3. Reload VS Code and start using the tools with Copilot

Example Usage

/ask Get the current war status from Helldivers 2
/ask List all available planets
/ask Show me the game statistics

Configuration: The above setup enables the MCP server to work with VS Code's Copilot integration. Adjust paths as needed for your environment.

API Tools

The MCP server exposes the following tools:

get_war_status

Get current war status from the High-Command API.

Parameters: None

Returns: War information including war ID, start/end times.

get_planets

Get planet information.

Parameters: None

Returns: List of planets with names, sectors, biomes, and positions.

get_statistics

Get global game statistics.

Parameters: None

Returns: Aggregated statistics including missions won/lost, kills, accuracy, etc.

get_campaign_info

Get active campaign information.

Parameters: None

Returns: List of campaigns with planet assignments and types.

get_planet_status

Get status for a specific planet.

Parameters:

• planet_index (integer, required): The index of the planet

Returns: Detailed status information for the specified planet.

Project Structure

high-command/
├── mcp/                    # Main MCP server package
│   ├── __init__.py
│   ├── server.py           # MCP server implementation
│   ├── api_client.py       # Helldivers 2 API client
│   ├── models.py           # Pydantic data models
│   └── tools.py            # MCP tool definitions
├── tests/                  # Test suite
│   ├── test_api_client.py
│   └── test_models.py
├── docs/                   # Documentation
├── Makefile                # Build and development tasks
├── Dockerfile              # Docker container definition
├── docker-compose.yml      # Docker Compose configuration
└── pyproject.toml          # Python project configuration

Docker

Building the Image

make docker-build

Running the Container

docker run -it --rm high-command:latest

Using Docker Compose

docker-compose up

Environment Variables

• LOG_LEVEL: Logging level (default: INFO)

Development

Setting up the Development Environment

# Install development dependencies
make dev

# Run formatter
make format

# Run linters
make lint

# Run tests
make test

Contributing

See CONTRIBUTING.md for guidelines.

API Rate Limiting

The High-Command MCP client detects rate limit responses but does not implement automatic retry logic:

• ✅ Detects 429 errors - Logs rate limit warnings when API returns "Too Many Requests"
• ✅ Transparent error handling - Propagates rate limit errors to calling application
• ⚠️ No automatic retries - Applications must implement their own exponential backoff strategy
• ✅ Example implementations - See docs/API.md#rate-limiting for backoff patterns

Best practices for production:

1. Implement exponential backoff in your application layer (example in API docs)
2. Cache results locally when possible to minimize API calls
3. Avoid making unnecessary or repeated requests
4. Monitor logs for repeated rate limit warnings (logger.warning("Rate limit exceeded"))
5. Consider request batching and throttling at the application level

Why no automatic retries? The MCP client follows a transparent error model, giving applications full control over retry logic and timeout behavior rather than hiding delays behind automatic retries.

See docs/API.md#rate-limiting for detailed information and code examples.

Troubleshooting

API Returns Bot Detection HTML

The Helldivers 2 API has Cloudflare bot protection. Make sure you're including the required headers:

• X-Super-Client
• X-Super-Contact

Connection Timeouts

Increase the timeout value in HighCommandAPIClient:

client = HighCommandAPIClient(timeout=60.0)  # 60 seconds

License

This project is licensed under the Apache License, Version 2.0 — see the LICENSE file for details.

Copyright 2026 DataKnifeAI

Acknowledgments

• HellHub Collective API
• Model Context Protocol
• Helldivers 2

Support

For issues and questions:

• 📝 GitHub Issues
• 💬 GitHub Discussions

---

Development

This project was built using GitHub Copilot with Claude Haiku 4.5, demonstrating the capabilities of AI-assisted software development for creating production-ready MCP servers.

---

Made with ❤️ for the Helldivers 2 community