Skip to main content
Glama
Sign In
cozyvtt-mcp

cozyvtt-mcp

by yanjingzhaisun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to cozyvtt-mcp

No user-submitted related servers found.

    Related Servers

    • RPG Ledger MCP Server

      sepa79
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to act as RPG Game Masters by managing campaign state including characters, inventory, quests, and logs through MCP tools. Supports campaign mutations and provides both MCP and HTTP API access to RPG session data.
      2
      -

    • Foundry VTT MCP Bridge

      adambdooley
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects Claude Desktop to Foundry VTT for AI-powered campaign management, enabling natural language interaction with game data including quest creation, character management, compendium searches, and dice rolling. Provides 20 MCP tools for seamless integration between Claude and your tabletop RPG sessions.
      82
      MIT

    • FoundryVTT MCP Server

      MCP-Mirror
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Integrates with FoundryVTT tabletop gaming sessions, allowing AI assistants to query game data, roll dice, generate content (NPCs, loot, encounters), manage combat, and provide tactical suggestions through natural language.
      7 npm
      -
    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 41 tools

    Disambiguation4/5

    Tools target distinct resource+action pairs, and descriptions actively steer callers (e.g. token_add vs token_place_creature, token_hp_update vs character_update, document_list vs campaign_document_list). A few near-neighbors remain (map_list vs campaign_get's current-map, character_hitdice_spend vs character_update), but each is explicitly cross-referenced with 'use X for Y' guidance, so misselection risk is low.

    Naming Consistency5/5

    All 41 names follow a single snake_case resource_action pattern (map_list, token_move, character_get, saved_roll_create, session_notes_update, campaign_transfer_dm). Multi-word resources like token_hp_update and character_hitdice_spend still read predictably. No camelCase or verb-style mixing.

    Tool Count2/5

    41 tools is well beyond the 3-15 well-scoped range; even for a broad VTT domain this is heavy and increases selection cost. Many are individually justified (four saved_roll CRUD ops, full document share lifecycle), but the surface could contract via grouped operations (e.g. token modifications, session lifecycle) without losing capability.

    Completeness3/5

    Strong coverage overall: maps, characters, documents, sessions, initiative, chat, dice, saved rolls, and events all have read/write surfaces. However, notable gaps exist—no token read/list or general token update (only add, place, move, delete), no chat edit/delete, and no fog/annotation tools despite map fog defaults being referenced. These force agents to work around missing operations.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources