F
licenseA
qualityA
maintenanceEnables MCP-capable AI assistants to work with a Foundry VTT world by reading and writing journals, scenes, compendiums, actors, combat, and more, subject to Gamemaster permissions and undoable changes.
152
-
cozyvtt-mcp
Related Servers
Alternatives to cozyvtt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to act as co-GMs and GM assistants within Foundry Virtual Tabletop, providing tools for game mechanics, actors, tokens, combat, canvas placeables, scenes, and world management.31 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with Foundry Virtual Tabletop, supporting reading world data, managing combat, rolling dice, and updating actor attributes via a sidecar architecture.31 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables 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-
- FlicenseNot gradedqualityAmaintenanceConnects 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.72-
- FlicenseNot gradedqualityNot gradedmaintenanceIntegrates 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.9 npm-
TDQS
A4.1/5.0
Scored across 41 tools
Disambiguation3/5
The tools are mostly distinct in their core purposes, but some confusion arises between document_list and campaign_document_list, document_share vs document_unshare, and token_hp_update vs character_update for HP. Also, saved_roll_list and saved_roll_create are clearly different, but the direct relationship between them and dice_roll is described.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern (e.g., character_get, character_create, document_update, session_manage). However, there are a few deviations like 'campaign_document_list' which is a resource-specific variant, and 'token_place_creature' which is descriptive but less consistent with the simple verb_noun pattern.
Tool Count1/5
The server has 41 tools, which is far beyond the typical well-scoped range. While each tool has a specific purpose, the sheer number suggests an overly granular surface that could overwhelm an agent's decision-making. The count is appropriate for a complex VTT but still excessive for coherence.
Completeness4/5
The server covers CRUD for characters, maps, tokens, documents, sessions, saved rolls, and initiative, as well as cron-like operations (chat, dice, events). Some notable gaps include lack of a token_get/token_list to inspect individual tokens, and no direct way to view all saved rolls other than list, but the core lifecycle is covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues