EVE Online MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVE_CLIENT_ID | No | Non-default override for automation or existing credentials | |
| ESI_USER_AGENT | No | Optional override for a downstream app's identity/contact | |
| ESI_OPENAPI_PATH | No | Loads a different local OpenAPI document for development | |
| EVE_ACCESS_TOKEN | No | Non-default override for automation or existing credentials | |
| EVE_CLIENT_SECRET | No | Non-default override for automation or existing credentials | |
| EVE_REFRESH_TOKEN | No | Non-default override for automation or existing credentials | |
| EVE_CREDENTIALS_PATH | No | Overrides the OS credential file location | |
| EVE_DISABLE_AUTO_SSO | No | Set to `1` to prevent browser login on protected calls | |
| EVE_SSO_REDIRECT_URI | No | Overrides the localhost callback for a custom application | |
| ESI_MAX_RESPONSE_BYTES | No | Overrides the 5,000,000-byte response ceiling |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_esi_operationsA | Find read-only EVE Online ESI operations by natural-language keywords, exact tag, or authentication requirement. Start here when choosing which game data to retrieve. |
| get_esi_operationA | Return the exact path/query/header parameters, OAuth scopes, cache hints, and rate-limit metadata for one read-only ESI operation before calling it. |
| call_esiA | Execute an ESI GET/HEAD operation selected by operationId. Only parameters declared by the pinned OpenAPI schema are accepted. Mutating ESI operations cannot be selected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_eve_adventure | Guide the model to use live ESI data when helping decide what to do next in EVE Online |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| esi-catalog | Summary of the pinned ESI schema and the operations this server exposes |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search discovers operations, get returns metadata for a specific operation, and call executes the operation. There is no meaningful overlap or ambiguity between them.
The names are all snake_case with a verb-first pattern, which is consistent and predictable. The only minor deviation is call_esi omitting the 'operation' noun that appears in the other two tool names.
Three tools is an appropriate and focused size for a gateway that discovers, inspects, and executes read-only ESI operations. Each tool serves a necessary step in the workflow without redundancy.
For its stated purpose of providing read-only EVE Online ESI access, the set is complete: search, inspect, and call cover the full lifecycle. Mutating operations are intentionally excluded and clearly communicated, so there are no obvious gaps.