
Connects Claude to the Monster Hunter World database at mhw-db.com with no authentication required. Part of the Pipeworx gateway ecosystem, which aggregates 673+ data sources behind a single MCP interface. You can either connect to this dedicated MHW endpoint or use the full Pipeworx gateway to access everything at once. Includes an ask_pipeworx tool that lets you query in plain English instead of calling specific functions. Reach for this if you're building Monster Hunter tools, need game data for a wiki or companion app, or want to prototype something that queries equipment stats, monster info, or item databases without dealing with REST APIs directly.
MHW MCP — Monster Hunter World data (mhw-db.com, free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_monsters | Search Monster Hunter World monsters by name, species, or size class. Returns species classification, elements, ailments, and weaknesses to plan hunts. |
get_weapons | Browse Monster Hunter World weapons by type (e.g., 'Great Sword', 'Bow', 'Hammer'). Returns damage, elements, and rarity to match your playstyle. |
get_armor | Find Monster Hunter World armor by rank and type. Returns defense, elemental resistances, and skill slots for building effective sets. |
get_skills | Look up Monster Hunter World skills by name. Returns descriptions, max ranks, and level-by-level effects to optimize your build. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mhw": {
"url": "https://gateway.pipeworx.io/mhw/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/mhw/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Mhw data" })
The gateway picks the right tool and fills the arguments automatically.
MIT