This MCP server integrates with the airplanes.live API to provide real-time aircraft tracking capabilities to Claude Desktop. Track flights, find aircraft by callsign, registration, or position - all directly from Claude!
📖 Educational and Non-Commercial Use Only
This project uses the airplanes.live API which is provided for educational and non-commercial purposes only. Please respect their terms of service.
- ✅ Educational projects - Learning and research
- ✅ Personal use - Non-commercial tracking
- ✅ Open source contributions - Community development
- ❌ Commercial applications - Business/profit purposes
- ❌ High-volume requests - Respect rate limits
The author of this MCP server does not assume any responsibility for the use of this software. This is a community contribution intended for educational purposes and to demonstrate MCP server development. Users are responsible for complying with airplanes.live API terms and any applicable regulations.
This project does NOT intend to replace or compete with the official airplanes.live globe viewer. The official globe is the primary and recommended way to visualize flight data. This MCP server is designed as a complementary educational tool for Claude Desktop integration and MCP development learning.
📖 Full API Terms: https://airplanes.live/api-guide/
🌍 Official Globe Viewer: https://globe.airplanes.live
- 🔍 Search by Callsign - Find specific flights (e.g., UAL123)
- 📋 Registration Lookup - Track by tail number (e.g., N12345)
- 🎯 Position-based Search - Aircraft near coordinates
- 🏷️ Hex ID Search - Mode S transponder codes
- 🛡️ Military Aircraft - Tracked military flights
- 🚁 LADD Aircraft - Law enforcement tracking
- ⭐ PIA Aircraft - Private/Interesting aircraft
- 📡 Squawk Codes - Emergency and special codes
Various API search examples
- 🐍 Python MCP Server - Async server implementation
- 🌐 MCP Framework - Modern server architecture
- ⚡ httpx Client - High-performance HTTP requests
- 📊 Data Formatter - Clean, readable aircraft information
- 🔌 Claude Integration - Direct MCP protocol support
graph TD
A[Claude Desktop] --> B[MCP Protocol]
B --> C[airplane_server.py]
C --> D[API Functions]
D --> E[airplanes.live API]
E --> F[Aircraft Data]
F --> G[Formatted Response]
G --> A
System architecture and data flow
- 🐍 Python 3.8+
- 💻 Claude Desktop
- 🌐 Internet connection
# 1. Clone the repository
git clone https://github.com/Bellaposa/airplanes-live-mcp.git
cd airplanes-live-mcp
# 2. Create virtual environment (REQUIRED!)
python -m venv .venv
# 3. Activate virtual environment
# macOS/Linux:
source .venv/bin/activate
# Windows:
.venv\Scripts\activate
# 4. Install dependencies
pip install -r requirements.txt
# 5. Test the server
python airplane_server.py🔥 Virtual Environment is MANDATORY!
- If you skip step 2-3, you'll get
ModuleNotFoundError: No module named 'httpx' - Claude Desktop needs the full path to the venv Python, not system Python
- Without venv, dependencies aren't isolated and things break
🪟 Windows Users:
- Virtual env creates
.venv\Scripts\folder (not.venv\bin\) - Use
Scripts\python.exein Claude config, notbin/python - Always use double backslashes
\\in JSON paths
🐍 Python Path Issues:
- Make sure Python 3.8+ is installed:
python --version - If
pythondoesn't work, trypython3orpy - Virtual environment MUST exist before configuring Claude Desktop
Skip Python setup headaches - use Docker instead!
- 🐳 Docker Desktop installed and running
- 💻 Claude Desktop
# 1. Clone the repository
git clone https://github.com/Bellaposa/airplanes-live-mcp.git
cd airplanes-live-mcp
# 2. Build Docker image
docker build -t airplane-mcp-server .
# 3. Test the container
docker run --rm -it airplane-mcp-server python airplane_server.pyAdd to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"airplanes-live": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"airplane-mcp-server",
"python", "airplane_server.py"
]
}
}
}Add to %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"airplanes-live": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"airplane-mcp-server",
"python", "airplane_server.py"
]
}
}
}# Build the image
docker build -t airplane-mcp-server .
# Run interactively for testing
docker run --rm -it airplane-mcp-server bash
# Check if image exists
docker images | grep airplane-mcp-server
# Remove image if needed
docker rmi airplane-mcp-server
# View container logs (if running detached)
docker logs <container_id>- 🚀 No Python setup required - Everything pre-configured
- 🔒 Isolated environment - No dependency conflicts
- 🌍 Works everywhere - Same setup on Windows/Mac/Linux
- 📦 Easy updates - Just rebuild the image
- 🛡️ Consistent behavior - Eliminates "works on my machine"
Problem: "docker: command not found"
# Install Docker Desktop first
# macOS: https://docs.docker.com/desktop/install/mac-install/
# Windows: https://docs.docker.com/desktop/install/windows-install/
# Linux: https://docs.docker.com/desktop/install/linux-install/Problem: "Cannot connect to Docker daemon"
# Start Docker Desktop application
# Wait for Docker to fully start (green icon)Problem: "Permission denied" (Linux)
# Add user to docker group
sudo usermod -aG docker $USER
# Log out and back in, or:
newgrp dockerProblem: Image build fails
# Clean Docker cache
docker system prune -a
# Try building again
docker build --no-cache -t airplane-mcp-server .For the simplest setup, use Docker Compose:
# 1. Clone and enter directory
git clone https://github.com/Bellaposa/airplanes-live-mcp.git
cd airplanes-live-mcp
# 2. Build and run with one command
docker-compose up --build
# 3. In another terminal, test the server
docker-compose exec airplane-mcp-server python airplane_server.pyDocker Compose Claude Configuration:
{
"mcpServers": {
"airplanes-live": {
"command": "docker-compose",
"args": [
"-f", "/path/to/airplanes-live-mcp/docker-compose.yml",
"exec", "-T", "airplane-mcp-server",
"python", "airplane_server.py"
],
"cwd": "/path/to/airplanes-live-mcp"
}
}
}Configuration for all platforms:
{
"mcpServers": {
"airplanes-live": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"airplane-mcp-server",
"python", "airplane_server.py"
]
}
}
}Configuration with full paths:
{
"mcpServers": {
"airplanes-live": {
"command": "docker-compose",
"args": [
"-f", "/full/path/to/your/airplanes-live-mcp/docker-compose.yml",
"exec", "-T", "airplane-mcp-server",
"python", "airplane_server.py"
],
"cwd": "/full/path/to/your/airplanes-live-mcp"
}
}
}# 1. Clone and build
git clone https://github.com/Bellaposa/airplanes-live-mcp.git
cd airplanes-live-mcp
docker build -t airplane-mcp-server .
# 2. Configure Claude Desktop with Method 1 (above)
# 3. Restart Claude Desktop completely
# 4. Test with: "Show me aircraft near New York"| Method | Pros | Cons | Best For |
|---|---|---|---|
| Docker | ✅ No Python setup ✅ Works everywhere ✅ Isolated |
❌ Requires Docker ❌ Slight overhead |
Beginners, Windows users |
| Python | ✅ Direct execution ✅ Easy debugging ✅ No Docker needed |
❌ Manual Python setup ❌ OS-specific issues |
Developers, experienced users |
Docker Compose Commands:
# Start services in background
docker-compose up -d
# View logs
docker-compose logs airplane-mcp-server
# Stop services
docker-compose down
# Rebuild and restart
docker-compose up --build
### ⚙️ Claude Desktop Configuration
#### 🍎 **macOS/Linux Configuration**
Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `~/.config/claude-desktop/config.json` (Linux):
```json
{
"mcpServers": {
"airplanes-live": {
"command": "/path/to/airplanes-live-mcp/.venv/bin/python",
"args": ["/path/to/airplanes-live-mcp/airplane_server.py"],
"env": {
"PYTHONPATH": "/path/to/airplanes-live-mcp"
}
}
}
}
Add to %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"airplanes-live": {
"command": "C:\\Users\\YourUsername\\airplanes-live-mcp\\.venv\\Scripts\\python.exe",
"args": ["C:\\Users\\YourUsername\\airplanes-live-mcp\\airplane_server.py"],
"env": {
"PYTHONPATH": "C:\\Users\\YourUsername\\airplanes-live-mcp"
}
}
}
}- Use
Scripts\\python.exe(notbin/python) - Replace
YourUsernamewith your actual Windows username - Use double backslashes
\\in paths - Make sure the virtual environment is created with
python -m venv .venv
Claude Desktop configuration
🔍 Find flight UAL123
📍 Show aircraft near 40.7128, -74.0060 within 50nm
🛡️ Show all military aircraft
All tools use async to handle multiple requests efficiently:
@mcp.tool()
async def aircraft_near_position(latitude: str = "", longitude: str = "", radius: str = "250") -> str:This allows the server to handle concurrent requests without blocking.
All parameters are strings because MCP protocols work best with simple types:
# Correct
def tool(param: str = "") -> str:
# Avoid
def tool(param: Optional[int] = None) -> str:Every tool includes comprehensive error handling:
try:
# Main logic
except ValueError:
return f"❌ Error: Invalid input"
except Exception as e:
return f"❌ Error: {str(e)}"The format_aircraft_data() function provides consistent, readable output:
def format_aircraft_data(aircraft_data):
# Handles both single aircraft and lists
# Formats all available fields with emoji indicators
# Returns human-readable stringsThe make_api_request() function centralizes HTTP logic:
async def make_api_request(endpoint):
async with httpx.AsyncClient(timeout=15) as client:
url = f"{API_BASE_URL}{endpoint}"
response = await client.get(url)
response.raise_for_status()
return response.json()This approach:
- Centralizes error handling
- Manages timeouts
- Logs all requests
- Makes it easy to add authentication later
Purpose: Search for aircraft by Mode S hex identifier
Input: Comma-separated hex IDs (e.g., "45211e,45212f")
Returns: List of matching aircraft with full details
Example:
User: "Show me aircraft with hex 45211e"
Tool: "🔍 Found 1 aircraft: ✈️ Callsign: RYR123 ..."
Purpose: Search for aircraft by flight callsign
Input: Comma-separated callsigns (e.g., "BA387,AA123")
Returns: Aircraft matching the callsign
Example:
User: "Find flight BA387"
Tool: "🔍 Found 1 aircraft: ✈️ Callsign: BA387 ..."
Purpose: Search for aircraft by tail number/registration
Input: Comma-separated registrations (e.g., "N123AB,G-EUPA")
Returns: Aircraft matching the registration
Example:
User: "Show aircraft with tail N123AB"
Tool: "🔍 Found 1 aircraft: 📋 Registration: N123AB ..."
Purpose: Search for aircraft by ICAO type code
Input: Type codes (A321, B738, C172, E190, etc.)
Returns: All aircraft of that type currently flying
Example:
User: "Show all Boeing 737s"
Tool: "🔍 Found 247 aircraft of type B738: ..."
Purpose: Search for aircraft by squawk code
Input: 4-digit squawk code (e.g., "7500", "7600", "7700")
Returns: Aircraft squawking that code
Note: 7700 = Emergency, 7600 = Communications failure, 7500 = Hijacking
Example:
User: "Find aircraft squawking 7700"
Tool: "🔍 Found aircraft in emergency: ..."
Purpose: Find all aircraft within a radius of coordinates
Input:
- latitude (decimal degrees, -90 to 90)
- longitude (decimal degrees, -180 to 180)
- radius (nautical miles, max 250)
Returns: All aircraft within the radius
Example:
User: "Show aircraft within 50 nm of Madrid (40.4168, -3.7038)"
Tool: "📍 Found 23 aircraft within 50 nm of 40.4168, -3.7038: ..."
Purpose: List all military aircraft
Input: None
Returns: All aircraft tagged as military
Example:
User: "What military aircraft are flying?"
Tool: "🎖️ Found 12 military aircraft: ..."
Purpose: List law enforcement and security aircraft
Input: None
Returns: All LADD (Law Enforcement/Security) aircraft
Example:
User: "Show law enforcement aircraft"
Tool: "🚁 Found 8 LADD aircraft: ..."
Purpose: List interesting/special aircraft
Input: None
Returns: All PIA (special interest) aircraft
Example:
User: "Show special/private aircraft"
Tool: "🛡️ Found 156 PIA aircraft: ..."
All tools return formatted strings with emoji indicators:
✈️ Callsign: BA387
📋 Registration: G-EUPA
🛩️ Type: A350
📍 Position: 51.4769, -0.4589
📏 Altitude: 35000 ft
⚡ Ground Speed: 485 knots
🧭 Track: 089°
🔖 Mode S Hex: 406ee9
👁️ Last Seen: 3 seconds ago
This provides:
- Visual clarity with emojis
- Easy scanning of information
- Consistent formatting
- Professional appearance
To add a new tool to this server:
@mcp.tool()
async def new_tool(param1: str = "", param2: str = "") -> str:
"""Single-line description of what this tool does."""
if not param1.strip():
return "❌ Error: param1 is required"
try:
# Your implementation
result = await make_api_request("/endpoint")
formatted = format_aircraft_data(result.get('ac', []))
return f"✅ Success:\n\n{formatted}"
except Exception as e:
return f"❌ Error: {str(e)}"Update the tools: section in custom.yaml:
tools:
- name: new_tooldocker build -t airplane-mcp-server .The new tool will automatically appear.
import asyncio
async def test_aircraft_by_callsign():
result = await aircraft_by_callsign("BA387")
assert "✈️" in result
assert "Found" in result
print(result)
# Run with: asyncio.run(test_aircraft_by_callsign())# Start server
python airplane_server.py
# In another terminal, test via stdin:
echo '{"jsonrpc":"2.0","method":"tools/list","id":1}' | python airplane_server.py- Typical: 500ms - 1s
- Complex queries: 1s - 2s
- Timeout: 15 seconds
- Max 1000 aircraft per query (API limit)
- Radius search: max 250 nautical miles
- Callsign/registration: comma-separated up to 8000 chars
- Use specific searches - Narrow searches are faster
- Avoid hammering the API - Reasonable request frequency
- Cache results locally - Consider storing recent queries
- Monitor timeouts - API may be slow during peak traffic
Solution:
- Verify image built:
docker images | grep airplane - Check catalog:
cat ~/.docker/mcp/catalogs/custom.yaml - Verify registry:
cat ~/.docker/mcp/registry.yaml - Restart Claude: Quit completely, then reopen
Causes:
- Wrong coordinates (verify lat/lon format)
- Radius too small
- No traffic in that area
- Wrong type code (try uppercase)
Solution: Try a broader search or different parameters
Cause: API is slow or rate-limited
Solution:
- Wait 30 seconds
- Try a simpler query
- Check internet connection
Solution:
# Add user to docker group
sudo usermod -aG docker $USER
# Log out and back in
newgrp docker
⚠️ Important Note: This planned dashboard is intended as an educational complement to the excellent official airplanes.live globe viewer, not a replacement. The goal is to demonstrate web development integration with MCP servers for learning purposes.
- Caching System - Redis cache to reduce API calls
- Rate Limiting - Smart request throttling
- Export Features - Save results as JSON/CSV/KML
- Enhanced Formatting - Better data visualization in Claude
- Flight Alerts - Notify when specific aircraft appear
- Historical Tracking - Store and track aircraft movements
- Statistics Dashboard - Aggregate data and analytics
- API Extensions - Additional airplanes.live endpoints
- 🧠 Flight Prediction - ML-based flight path estimation
- 📈 Pattern Analysis - Identify unusual flight patterns
- 🚨 Anomaly Detection - Automated alerts for interesting events
- 📊 Trend Analysis - Historical data insights
- No authentication required (public API data)
- Consider applying for an API key for production use
- No sensitive credentials stored
- Runs as non-root user
- Input validation on all parameters
- Add rate limiting if needed
- Implement query logging for monitoring
- Consider caching to reduce API calls
- Add input sanitization for custom endpoints
- API Documentation: https://airplanes.live/
- API Terms of Use: https://airplanes.live/api-guide/
- MCP Specification: https://docs.anthropic.com/mcp
- FastMCP Documentation: https://github.com/jlowin/fastmcp
- httpx Documentation: https://www.python-httpx.org/
This is an open-source educational project! Contributions are welcome:
- 🐛 Bug Reports - Open an issue
- 💡 Feature Requests - Suggest improvements
- 🔧 Pull Requests - Submit code changes
- 📖 Documentation - Improve guides and examples
MIT License - Feel free to use, modify, and distribute for educational purposes.
- This software is provided "AS IS" without warranty
- Author assumes no responsibility for usage or compliance
- Users must respect airplanes.live API terms
- Educational and non-commercial use only
- Not affiliated with airplanes.live
This project is a community contribution for educational purposes, demonstrating MCP server development and API integration. The goal is to help developers learn and contribute to the MCP ecosystem, not for commercial gain.
Made with ❤️ for the MCP community
Remember: Always respect API terms and use responsibly!

