foundry-vtt

This MCP server acts as a bridge between Foundry VTT and Claude Desktop, enabling AI-assisted interactions with your Foundry world. Once configured, Claude can query and manipulate your Foundry data, generate quests and journals, search the compendium, manage characters and tokens, and orchestrate map generation via an optional ComfyUI backend. The bridge supports core capabilities like Quest Creation, Character Management, Compendium Search, Content Creation, Scene Information, Dice Coordination, Campaign Management, and Map Generation, making it possible to have natural language conversations that translate into concrete in-world actions. Use Claude to ask for things like stat blocks, item searches, or to generate a new quest prompt, and the MCP bridge will route those requests to Foundry VTT and return structured results.

Prerequisites:

• Foundry VTT v13
• Claude Desktop with MCP support
• Node.js 18+ (for manual installation)

Option A: Manual Installation

1. Clone the repository and install dependencies:

git clone https://github.com/adambdooley/foundry-vtt-mcp.git
cd foundry-vtt-mcp
npm install
npm run build

2. Configure Claude Desktop to point at the MCP server by editing claude_desktop_config.json and add:

{
  "mcpServers": {
    "foundry-mcp": {
      "command": "node",
      "args": ["path/to/foundry-vtt-mcp/packages/mcp-server/dist/index.js"],
      "env": {
        "FOUNDRY_HOST": "localhost",
        "FOUNDRY_PORT": "31415"
      }
    }
  }
}

3. Start Foundry VTT and Claude Desktop. The MCP server will be started by Claude Desktop when configured.

Option B: Windows Installer / Mac Installer (if using the provided installers)

• Download the installer from the Releases page for your platform and run it.
• The installer bundles Node.js, configures Claude Desktop, and optionally installs the Foundry module and ComfyUI map generation components.
• After installation, restart Claude Desktop and enable the Foundry MCP Bridge in Module Management.

Notes and tips:

• Ensure Foundry VTT is accessible at the host/port configured in the MCP server (default localhost:31415 in the example).
• The Foundry module ID and folder name must not be renamed; the MCP backend and Claude integration expect the folder to be foundry-mcp-bridge for socket routing.
• If you enable the ComfyUI Map Generation feature, you’ll need the optional ComfyUI backend configured as part of your Foundry setup.
• For local network setups, you can adjust the Connection Type to WebSocket and set the Websocket Server Host accordingly.
• If Claude cannot see Foundry data, verify the MCP server process is running and that the environment variables (FOUNDRY_HOST, FOUNDRY_PORT) match your Foundry instance.
• The MCP Tools cover system-agnostic operations; certain advanced features like detailed token manipulation and map generation rely on the Foundry module and optional ComfyUI backend being installed and configured.