Skip to main content
Glama
ArtSabintsev

Guild Wars 1 MCP

by ArtSabintsev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Guild Wars 1 MCP

No user-submitted related servers found.

    Related Servers

    • gw1-mcp

      Graphmaxer
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives LLM clients reliable, deterministic knowledge of Guild Wars 1 builds: skill data lookup, official template code encoding/decoding, and build validation.
      1
      MIT

    • wow-api-mcp

      spartanui-wow
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes structured World of Warcraft API data (functions, deprecated replacements, enums, events, widget methods) to AI agents, enabling querying and exploration of WoW API without wiki parsing.
      24 npm
      13
      MIT
    • OSRS MCP Server by WaterSippin

      OSRS MCP Serverofficial

      WaterSippin
      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
      44 npm
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool has a clearly defined target (wiki, Reddit, YouTube, builds, templates, local), and the cross-source content_search is explicitly an aggregate over the narrower searches. The only mild ambiguity is between gw1_sources and gw1_local_inventory, both touching local inventory, but one lists known surfaces and the other performs scanning.

    Naming Consistency5/5

    All 14 tools share the gw1_ prefix, snake_case, and a predictable gw1_<domain>_<kind/action> shape (search, page, encode, analyze, videos, sources). This is a consistent convention even though some suffixes are nouns rather than verbs.

    Tool Count5/5

    14 tools is within the ideal 3-15 range and each tool covers a distinct task, from wiki browsing to template encoding to cross-source search. None feel redundant or padding.

    Completeness4/5

    The set covers the main read/research workflows: wiki search/fetch/updates, community content search, build search, template encode/decode, and local inventory discovery. Minor gaps remain—no equipment/build template handling or wiki history/diff tools—but core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources