Skip to main content
Glama

mcp-mhw

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.

Tools

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.

Related MCP server: wow-mcp

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "mhw": {
      "url": "https://gateway.pipeworx.io/mhw/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/mhw/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_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.

Using with ask_pipeworx

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.

More

License

MIT

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/get_monsters \
  -H 'Content-Type: application/json' \
  -d '{"limit":10}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_monsters. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    Not graded
    maintenance
    MCP Server for interacting with Old School RuneScape Wiki API and game data files, providing tools to search the OSRS Wiki and access game data definitions through the Model Context Protocol.
    19
    50 npm
    1
    -
  • F
    license
    Not graded
    quality
    F
    maintenance
    A comprehensive MCP server that wraps the complete World of Warcraft retail API into 197 tools for Game Data and Profile information. It enables users to query character statistics, achievements, collections, and game mechanics across all global regions and locales.
    9
    -