eve-online-traffic

eve-online-traffic is an MCP server that provides comprehensive EVE Online data access by combining real-time data from the ESI API with static data from the SDE, enabling name-to-ID lookups, system information, stargate details, and route calculations. It exposes a set of tools designed to help you translate human-readable EVE Online names into IDs, inspect solar system data from multiple data sources, and compute routes or maps between systems. Typical workflows involve looking up IDs for entities (systems, stations, regions, etc.), retrieving system details (coordinates, stargates, stations), and calculating routes or ranges to support planning and analysis. The server also includes utilities for aggregating data from ESI, SDE, and EVE-KILL APIs for richer context.

Prerequisites:

• Node.js and npm installed on your machine
• Git installed
• Optional: a working internet connection for npm install and API access

Manual installation steps:

1. Clone the repository: git clone https://github.com/kongyo2/eve-online-traffic-mcp.git
2. Navigate to the project directory: cd eve-online-traffic-mcp
3. Install dependencies: npm install
4. Build the TypeScript sources (if applicable): npm run build
5. Run in development mode (with CLI interactivity): npm run dev
6. Run in production mode: npm run start

If you want to install via Smithery (automatic installation): npx -y @smithery/cli install @kongyo2/eve-online-traffic-mcp --client claude

Tips and common considerations:

• The server integrates data from ESI (real-time) and SDE (static) to provide robust name resolution and context. Ensure that API access is not blocked by rate limits or network restrictions.
• When constructing queries, prefer English entity names (e.g., "Jita", "Amarr", "The Forge") to maximize name resolution accuracy.
• If you plan to run in production, consider building the project first and running the built dist/index.js entry point to improve startup time.
• Review environment variables and API keys if you need to customize data sources, rate limits, or authentication for protected endpoints.
• This MCP server is described as beta; expect ongoing changes to APIs, data models, and capabilities.