Azeroth DB: WoW Forever

wiki.wowdbPublished by wowdb.wikiOfficial publisherv0.2.1Updated Oct 26, 2026

Search WoW Forever items, recipes, abilities and quests with page links from Azeroth DB.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Read-only MCP access to Azeroth DB's WoW Forever records: search items, recipes, abilities, quests and more, then fetch full record data and page links.

What you can do
  • Search records by name in a chosen language, filtered by kind, returning slugs and exact page paths
  • Read a record from a page path, with full English data or an explicitly marked preview
  • Browse all records of a kind in name order, continuing with nextOffset
  • Page through long arrays inside a record using field pointers and offsets
When to use it
Useful when an assistant needs to look up World of Warcraft (WoW Forever) game data such as items, recipes, abilities, talents, quests, dungeons or factions, and cite the matching Azeroth DB page. It is a read-only reference source, not a tool for player, news or map data.
Requirements
A remote Streamable HTTP endpoint at wowdb.wiki; no API key and no install. Clients that only start local stdio servers can bridge to it through mcp-remote with npx. Running from source needs Node.js 26.12.1 or later.
Before you install
Read-only: it starts no HTTP listener, reads no account records and changes no site data. Localized lookups return preview data that may have English labels, shortened lists or missing text, and nulls mean unknown. Prices are in copper and vendor observations are not auction prices. An optional WOWDB_ORIGIN environment variable changes the request origin only.

Installation

In SourceWeft

  1. Open Azeroth DB: WoW Forever in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/wiki.wowdb%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "azeroth-db-wow-forever": {
      "type": "http",
      "url": "https://wowdb.wiki/api/mcp"
    }
  }
}

README

wowdb-mcp

Read WoW Forever records from Azeroth DB over MCP. Search by a record's name, then read its values and open its exact page.

Connect

The server runs at https://wowdb.wiki/api/mcp over Streamable HTTP. It needs no API key and no install. For Claude Code, use this MCP configuration:

json
{  "mcpServers": {    "wowdb": {      "type": "http",      "url": "https://wowdb.wiki/api/mcp"    }  }}

In Claude Code: claude mcp add --transport http wowdb https://wowdb.wiki/api/mcp.

A client that only starts local stdio servers reaches the same endpoint through mcp-remote:

json
{  "mcpServers": {    "wowdb": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://wowdb.wiki/api/mcp"]    }  }}

Run from source

Requires Node.js 26.12.1 or later.

sh
npm installnode server.mjs

server.mjs serves the same tools over MCP stdio. It writes MCP messages to stdout, starts no HTTP listener, reads no account records and changes no site data. wowdb-mcp exports createServer; wowdb-mcp/http exports handleMcp, which answers one stateless Streamable HTTP request and is what the site's /api/mcp route runs.

Tools

ToolInputResult
searchquery; optional kind, locale, offset, limitMatching names with their kinds, slugs, page paths and production URLs
get_entitypath from a search or list result; optional field, offset, limitActual record data, its representation, data URL and production page URL
list_entitieskind; optional locale, offset, limitRecords in name order with continuation through nextOffset

Supported kinds are item, recipe, ability, spell, enchant, talent, legacy, race, quest, giver, camp, dungeon, achievement, faction and English guide. The server does not expose news, player records or map placement tools.

json
{"name":"search","arguments":{"query":"Empty Vial","kind":"item","limit":1}}{"name":"get_entity","arguments":{"path":"/forever/items/empty-vial"}}{"name":"search","arguments":{"query":"Leere Phiole","kind":"item","locale":"deDE","limit":1}}{"name":"get_entity","arguments":{"path":"/de/forever/gegenstaende/leere-phiole"}}

Locale codes are enUS (default), deDE, esES, esMX, frFR, koKR, ptBR, ruRU, zhCN and zhTW. Search reads the index of the requested language; lookup takes the language from the returned page path. Reuse that path rather than translating a slug or adding a locale query parameter.

Data boundaries

The English directory and named-record API provide full records for their published paths. Search also covers records with a preview API only. representation is full-record or preview so a caller can distinguish these responses. A named talent is selected from its class response, rather than returning that class as the talent.

Localized lookups return the site's preview data. Those responses may have English field labels, shortened relationship lists or missing text. They do not provide every field of the full English record. Localized guide records have no lookup API and are excluded. The API can describe an ability's last rank above the game's level cap of 60; such a preview returns a tool error instead of presenting that rank as available. The full English ability response keeps ranks with a required level at or below 60, including an unknown level when the API explicitly records it as null. Known item requirements and quest levels above 60 are excluded from discovery.

Keep nulls and missing fields unknown. An item's presence does not establish its drop chance or acquisition conditions. Prices such as sellPrice and observed.price are in copper; vendor observations are not auction prices. Every successful result contains serialized JSON in a text content block. HTTP and lookup failures return isError: true with a message; a missing record asks the caller to search again.

Pagination

limit defaults to 48 and accepts 1 through 48, matching the site's public item collection page size. Search and list results return nextOffset; pass it as offset with the same query, kind and language.

Lookup keeps scalar values and objects and limits each array to the requested page size. If an array has more entries, pagination identifies its field as a JSON pointer and supplies nextOffset. Pass both back to get_entity with the same page path. For example:

json
{"name":"get_entity","arguments":{"path":"/forever/items/empty-vial","field":"/uses","offset":0,"limit":2}}

Pointers are relative to the returned data, such as /ranks or /recipes/0/materials. They select the original API data before array paging. They cannot retrieve relationships omitted by the API itself. An offset past the final result returns a tool error, rather than repeating the first page.

Testing origin

WOWDB_ORIGIN is the single environment override for API requests, for example http://localhost:3712. It changes the request origin only. Returned page links and data links remain on https://wowdb.wiki.

The package reads its own public API contracts. It does not import site source, store API payloads on disk or retain locale indexes between calls.

Source: README.md at commit 64444a8

Tools

3

get_entity

Read a page path returned by search or list_entities. Returns the full English API record where available; localized and search-only records return explicitly marked previews. Null remains unknown. Arrays are paged at up to 48 rows; use a pagination field with its nextOffset to continue.

Parameterspathrequiredfieldlimitoffset

list_entities

Browse a kind of WoW Forever record in name order, with exact production page paths. Pass nextOffset as offset to continue. Uses the same locale and beta scope as search.

Parameterskindrequiredlimitlocaleoffset

Version history

2
  1. v0.2.1LatestOct 26, 2026
  2. v0.2.0Oct 26, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts