LatteandClaude Opus 4.8
4223141cf7
Add a thin async ESI client (httpx, descriptive User-Agent, uniform errors, mockable transport) plus name<->id resolution. New read-only tools: - universe: resolve_names, get_item, get_system, get_station, get_region, get_route - market: list_hubs, get_market_price, get_market_orders, compare_hubs Trade-hub IDs (Jita/Amarr/Dodixie/Rens/Hek) are hardcoded constants. Market aggregation (best buy/sell, spread, order book) lives in pure helpers. 30 unit tests with mocked ESI; coverage 99%. SDE bulk-load deferred to a later phase. Closes #2 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
familiar
Your familiar across New Eden — a read-only EVE Online MCP server that lets a local AI see your entire account and find anything in EVE.
In EVE, your familiar isn't a cat on the windowsill. It's the companion that rides along through New Eden, sees what you see, remembers what you can't, and fetches anything you ask for. familiar is exactly that: an MCP server that gives a local AI (Claude Code, Claude Desktop, Cowork) a complete, read-only window into your EVE Online account and the entire game universe.
Ask your familiar where your assets are, what your skill queue looks like, what Tritanium sells for in Jita, the safest route to a lowsec system, or whether a fit is worth building. It looks, it finds, it reports back.
Principles
- Read-only by design.
familiaronly ever reads. No market orders, no fittings changes, no mail sent, no waypoints set. The AI can see everything and break nothing. - Local-first. Runs on your own machine. Your refresh token and account data never leave your control.
- Everything, eventually. The goal is full coverage: every read scope ESI exposes, plus the complete static universe. Built in phases so it actually ships.
How it works
Two data sources sit behind the server:
- ESI (the EVE Swagger Interface) — the official REST API. Public endpoints (market, universe, industry indices) need no login. Character and corp data (wallet, assets, skills, industry, contracts, mail, location) come through EVE SSO with read-only OAuth2 scopes.
- SDE (the Static Data Export) — the full static dataset of items, blueprints, systems and stations, cached locally for fast lookups and anything name- or recipe-based.
Built in Python with FastMCP, OAuth via PKCE with a localhost callback, refresh token stored encrypted on disk. ESI Expires headers are respected for caching, and the SDE is loaded into a local store.
Roadmap
Built in phases. Each phase is independently useful, so the project stays shippable.
Phase 0 — Skeleton
- Repo, project scaffold, FastMCP server that starts and exposes a health/ping tool.
- App registered on developers.eveonline.com.
Phase 1 — Public lookups (no auth)
- Market: prices and order book for any item in any hub, spreads between hubs.
- Universe via SDE: items, systems, stations, security, basic route/jumps.
- Quick win: useful before any OAuth complexity exists.
Phase 2 — Account read (OAuth)
- EVE SSO login flow, encrypted refresh token storage.
- Wallet, assets (search across characters), skills + skill queue, current location and clones.
Phase 3 — Industry & contracts
- Industry jobs, blueprints (SDE-backed), manufacturing cost/profit lookups.
- Personal and corp contracts, market orders.
Phase 4 — Everything else
- Mail, planetary interaction, loyalty points, fittings, corp roles.
- zKillboard integration for kill/PvP data.
Phase 5 — Polish
- Caching, error-limit safety, packaging, setup docs. Optional: prep a public, generic single-user release as a portfolio case.
Status
Phase 0. Just hatched.
License
MIT