Eve MCP Server

MCP server that turns Claude into an EVE Online mentor for new and returning players — explains your losses, plans your skills, checks your fits, and

Remote serverstreamable-httpGo

What is the Eve MCP server?

MCP server that turns Claude into an EVE Online mentor for new and returning players — explains your losses, plans your skills, checks your fits, and finds your stranded assets from live EVE data. Exposed over MCP by the eve mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • esi-skills.read_skills.v1 — esi-skills.read_skillqueue.v1
  • esi-location.read_location.v1 — esi-location.read_ship_type.v1
  • esi-wallet.read_character_wallet.v1 — esi-assets.read_assets.v1
  • recent_losses — none
  • can_i_fly — optional
  • fit_readiness — optional
  • proven_fits — none
  • analyze_fit — none
  • ammo_advisor — none
  • career_test — none
  • isk_guidance — none
  • what_should_i_do_tonight — SSO

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: EVE_CLIENT_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Eve's toolset — esi-skills.read_skills.v1, esi-location.read_location.v1, esi-wallet.read_character_wallet.v1 and 11 more — is a fair guide to whether it matches your workflow. It is maintained by blacksausage; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Eve.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the eve mcp server does with a few real requests.

Available tools

ToolWhat it does
esi-skills.read_skills.v1esi-skills.read_skillqueue.v1
esi-location.read_location.v1esi-location.read_ship_type.v1
esi-wallet.read_character_wallet.v1esi-assets.read_assets.v1
recent_lossesnone
can_i_flyoptional
fit_readinessoptional
proven_fitsnone
analyze_fitnone
ammo_advisornone
career_testnone
isk_guidancenone
what_should_i_do_tonightSSO
remember_goaloptional
recall_pilot_notesoptional

How to install the Eve MCP server

{
  "mcpServers": {
    "eve-mentor": {
      "command": "npx",
      "args": ["-y", "eve-mentor-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
EVE_CLIENT_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Eve to esi-skills.read skills.v1.
  • Use Eve to esi-location.read location.v1.
  • Use Eve to esi-wallet.read character wallet.v1.

Frequently asked questions

It connects Eve to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (esi-skills.read_skills.v1, esi-location.read_location.v1, esi-wallet.read_character_wallet.v1, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Eve directly.