Skip to main content
Glama
rjenks

pf2e-mcp

by rjenks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pf2e-mcp

No user-submitted related servers found.

    Related Servers

    • Foliant

      magnetron01123
      F
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server for D&D 5e rules reference, answering rule questions, providing character summaries, and assisting with character creation, based on imported sources with proper attribution.
      -

    • DM20 Protocol

      Polloinfilzato
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server for managing AI-assisted Dungeons & Dragons campaigns, featuring tools for character sheets, combat tracking, and world-building. It enables players and DMs to interact with 5e game mechanics and query personal PDF rulebooks using RAG capabilities.
      97
      2
      MIT

    • Tusk's Vault

      KochiTusker
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local-first, source-cited AI answers about your TTRPG campaign lore from your own documents, usable in Discord, Foundry VTT, or any MCP client while refusing to invent information outside your sources.
      MIT
    • SagaSmith D&D MCP by SagaSmithAI

      SagaSmith D&D MCPofficial

      SagaSmithAI
      A
      license
      Not graded
      quality
      F
      maintenance
      A local MCP server for Dungeons & Dragons campaign management, combining core runtime with skill and module-generation packs. It enables campaign creation, module generation and import, rule and skill searching via tools, resources, and prompts.
      Apache 2.0
    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

    A4.1/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: rules_search returns summaries for later lookup, rules_explain gives inline answers, rules_get_entry fetches details by id/name/slug, and rules_related traverses prerequisites. Build tools are similarly separated: list_* tools cover different entity types, and validation/calculation/export/sheet-rendering are clearly distinct. Even similarly named tools like build_list_available_feats and build_check_prerequisite are well-differentiated by scope (discovery vs single-check).

    Naming Consistency4/5

    The server uses two clear prefixes, rules_ and build_, followed by mostly verb_noun patterns (e.g., rules_search, build_list_classes, build_validate_build). Minor deviations like rules_related (adjective) and rules_data_version (noun phrase) break the strict pattern but are still readable and predictable. The naming is consistent and does not mix camelCase or different verb styles.

    Tool Count4/5

    At 22 tools, this is slightly heavy but each tool justifies its presence—rules lookups, variant/subclass browsing, character-building lists, validation, math, and export/render are all needed for the server's stated purpose. It is close to the upper bound but not excessive, and the count reflects a comprehensive feature set rather than redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of building a character: referencing rules, selecting ancestries/backgrounds/classes/equipment/feats/boosts, validating the build, calculating derived stats, determining level-up choices, and exporting to Pathbuilder or rendering a character sheet. There are no obvious dead ends—every major step has a corresponding tool, and rules_get_entry can retrieve any referenced entity.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources