Hi all,
EVE MCP Server is an open-source Model Context Protocol server exposing EVE’s public ESI endpoints as tools an AI assistant can call directly.
Repo: GitHub - pfh59/eve-mcp-server · GitHub — v1.1.0, C# / .NET 10, MIT
Why
Ask an LLM about EVE data without tooling and you get confident nonsense: hallucinated type IDs, invented systems, market numbers from nowhere. MCP is an open standard that lets a client (Claude Desktop, VS Code, others) call real tools instead of guessing. This server is the ESI side of that contract.
Coverage — 52 tools, all prefixed eve_
| Domain | Tools | Examples |
|---|---|---|
| Universe | 21 | Regions, systems, stations, stargates, types, groups, factions, jumps/kills |
| Market | 6 | Prices, orders by region/type, history, market groups |
| Character | 6 | Character / corporation / alliance public info, affiliations |
| Search | 2 | Name → ID and ID → name resolution |
| Gameplay | 7 | Server status, killmails, wars, incursions, insurance |
| Infrastructure | 10 | Routes, industry facilities, sovereignty, dogma, LP store |
Install — two options, no .NET SDK required either way
Option A — prebuilt executable
Grab the archive for your platform from the Releases page: eve-mcp-server-win-x64.zip or eve-mcp-server-linux-x64.tar.gz. These are self-contained single-file builds — unzip and point your MCP client at the binary, nothing else to install.
{
"mcpServers": {
"eve-online": {
"command": "C:\\path\\to\\eve-mcp-server.exe",
"env": {
"ESI__UserAgent": "my-eve-assistant/1.0 (you@example.com)"
}
}
}
}
Option B — Docker
Multi-arch images (amd64 + arm64) on GHCR, chiselled distroless runtime, non-root.
{
"mcpServers": {
"eve-online": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "ESI__UserAgent=my-eve-assistant/1.0 (you@example.com)",
"ghcr.io/pfh59/eve-mcp-server:latest"
]
}
}
}
-i is mandatory — the stdio transport needs