MCP overview
Give an AI assistant Everloot's data, with the source on every answer.
Point an AI assistant at Everloot and it can look up lore and the facts players have reported, with the source and licence on every answer. The server speaks the Model Context Protocol (MCP) over streamable HTTP.
The endpoint#
The hosted server needs no sign-in and no key.
https://everloot.app/mcp/public
Quick example#
Add the server to Claude Code, give the URL to any other client, or call it once with curl. The server keeps no session, so one call is enough.
claude mcp add --transport http everloot https://everloot.app/mcp/public
{
"mcpServers": {
"everloot": {
"type": "http",
"url": "https://everloot.app/mcp/public"
}
}
}curl -s https://everloot.app/mcp/public \ -H "content-type: application/json" \ -H "accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_by_name","arguments":{"name":"Thrall"}}}'
Other clients are on Connect a client.
Core concepts#
Player data and the 3-install rule#
Tools built on player data, marked below, state a fact only after 3 installs agree on it. They say when something is not recorded yet, and an unrecorded answer is never a zero. Anything read from the game files is labelled "found in game files, unconfirmed", with its build. How Everloot works explains the rule.
structuredContent#
Every tool returns structuredContent beside the text, of the shape in its schema file at /schema/mcp/<tool>.json. Each tool page lists the top-level fields. Answers built on player data start with connected and dataAsOf, and carry a page only when a corpus was read: an absent page is not a measured zero.
Sources and credit#
Lore hits carry their source URL and licence. Keep them with the text. Answers built on player data end with the licence and the credit line, as Everloot's data is CC BY-SA 4.0. See Licence and credit.
Data age#
Answers built on player data end with the age of the data. Read it before you quote a number.
Tools#
Every tool has its own page with arguments, the answer and a working call. Tools marked player data follow the 3-install rule; the others carry their sources inside the answer. The same list is at /schema/index.json.
Search and lore#
| Tool | What it does |
|---|---|
search_knowledge | Search lore and reference data. Every hit has its source and licence. |
get_entity | One record, by the id a search hit gives you. |
get_by_name | Records with exactly this name, for telling similar names apart. |
answer_sourcesplayer data | The evidence behind a question, each piece with its source, licence and date, so an assistant can answer and cite. |
search | The same search in the shape ChatGPT connectors and deep research call by name: results with an id, a title and a URL to cite. |
fetch | One record by a search result's id, whole, with its URL and the source, licence and date as metadata. ChatGPT's second tool. |
Database#
| Tool | What it does |
|---|---|
item_pageplayer data | One item: agreed name, drop rate with kill count, map pin. |
npc_pageplayer data | One NPC: agreed name and map pins. |
object_pageplayer data | One game object (a chest, herb, ore vein or fishing pool): the items players looted from it, with loot windows and install counts. |
quest_pageplayer data | One quest: title, level, giver, turn-in and rewards. |
vendor_pageplayer data | What one vendor sells, with copper prices. |
entity_relationsplayer data | How an item, NPC, spell or quest connects to others: dropped by, sold by, created by, reagent for, set, same icon. Each relation says if players saw it (3 installs) or the game files hold it (unconfirmed, with the build). |
item_categories | Item classes, subclasses, slots and qualities from the game files, with item counts; one item's category path, or the items in a category. Found in game files, unconfirmed, with the build. |
world_map_nearplayer data | What is near a spot: entrances, observed NPCs and vendors, with distances in yards. |
Planning#
| Tool | What it does |
|---|---|
talent_tree | One class's talent trees from the game files: every node with its talents, ranks, position, prerequisites and row gate. Found in game files, unconfirmed, with the build. |
talent_plan | Reads a talent share code or calculator link: the talents and ranks it holds, points per tree, the lowest level for it, and every problem in plain words. |
profession_pathplayer data | A leveling path for one profession, from what players reported. |
recipe_thresholdsplayer data | The skill ranges where a recipe turns yellow, green and grey. |
Market and characters#
| Tool | What it does |
|---|---|
market_valueplayer data | Market value, minimum buyout, historical value and units listed for one item on one realm, from full scans players started. |
auction_historyplayer data | Daily median auction price for one item on one realm. |
gold_ledgerplayer data | Peak gold and money events for one character, from that player's own upload. |
collection_gapplayer data | What one install is missing from a collection, such as Mounts. |
completion_progressplayer data | What one install's characters finished in achievements, reputation, titles and quest chains, and what is closest to done. |
guild_boardplayer data | A guild's roster, bosses, loot and attendance, from officer uploads. |
World and project#
| Tool | What it does |
|---|---|
populationplayer data | How many characters play each race, class, faction and level band, from players who turned the census on. Every answer says its window, and a count is hidden when too few players report it. |
recent_changes | Recent Blizzard staff posts, hotfixes and new game builds, newest first, with links to the originals. |
ecosystem_projects | Forever addons and open-source projects, ranked on five boards, with GitHub facts and install counts from 3 installs. |
everloot_plan | What is built, what is next and what is waiting. Read it before assuming a tool exists. |
Beyond tools#
- Resources and prompts: documents the assistant reads whole, and ready-made instructions a client offers as commands.
- Every tool also answers a plain GET at
/api/tools/{tool}, with no MCP client. See the endpoint.