laurigates/foundryvtt-mcp
If you are the rightful owner of foundryvtt-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The FoundryVTT MCP Server is a Model Context Protocol server that integrates with FoundryVTT, enabling AI assistants to interact with tabletop gaming sessions.
roll_dice
Roll dice with any formula.
search_actors
Find characters, NPCs, monsters.
generate_npc
Create random NPCs.
FoundryVTT MCP Server
A Model Context Protocol (MCP) server that integrates with FoundryVTT, allowing AI assistants to interact with your tabletop gaming sessions. Query actors, roll dice, generate content, and manage your game world through natural language.
Features
Core Functionality
- š² Dice Rolling - Roll dice with standard RPG notation
- š Data Querying - Search actors, items, scenes, and journal entries
- š Game State - Access current scene, combat status, and world information
- š Content Generation - Generate NPCs, loot, and random encounters
- š Rule Lookup - Query game rules and mechanical information
Real-time Integration
- š Live Updates - WebSocket connection for real-time game state
- āļø Combat Management - Track initiative and combat state
- š„ User Awareness - See who's online and their status
AI-Powered Features
- š§ Tactical Suggestions - Get combat advice and strategy tips
- šŖ Story Assistance - Generate plot hooks and narrative elements
- šØ World Building - Create locations, NPCs, and quests on demand
Installation
Prerequisites
- Node.js 18+
- FoundryVTT server running and accessible
- MCP-compatible AI client (Claude Desktop, etc.)
Quick Setup (Recommended)
š§āāļø Interactive Setup Wizard:
git clone <repository-url>
cd foundry-mcp-server
npm install
npm run setup-wizard
The setup wizard will:
- Automatically detect your FoundryVTT server
- Test connectivity and authentication
- Generate your
.env
configuration file - Validate the complete setup
Manual Setup
- Clone and install:
git clone <repository-url>
cd foundry-mcp-server
npm install
- Configure environment:
cp .env.example .env
# Edit .env with your FoundryVTT details
- Required environment variables:
FOUNDRY_URL=http://localhost:30000
FOUNDRY_API_KEY=your_api_key_here
# OR use username/password:
FOUNDRY_USERNAME=your_username
FOUNDRY_PASSWORD=your_password
- Test and start:
npm run test-connection # Verify setup
npm run build
npm start
Development Mode
npm run dev
FoundryVTT Configuration
The MCP server supports two secure, local-only authentication methods:
Option 1: Local REST API Module (š Recommended)
Benefits:
- ā 100% Local - No external dependencies or third-party services
- ā Maximum Privacy - Your game data never leaves your network
- ā Full Control - You own and manage all authentication
- ā Better Performance - Direct local API access
- ā Complete API Access - Full access to all FoundryVTT features
Setup:
- Install the Foundry Local REST API module:
- In FoundryVTT: Setup ā Add-on Modules ā Install Module
- Paste:
https://github.com/laurigates/foundryvtt-mcp/releases/latest/download/module.json
- Enable the module in your world
- Go to Settings ā Configure Settings ā Module Settings
- Find "Foundry Local REST API" and check "Enable REST API"
- Copy the generated API Key
- Add to your
.env
file:FOUNDRY_URL=http://localhost:30000 FOUNDRY_API_KEY=your_local_api_key_here
Option 2: Username/Password (Fallback)
Use when: Local REST API module is not available or for simple setups.
Limitations: Some advanced features may not work properly.
- Ensure your FoundryVTT user has appropriate permissions
- Add credentials to
.env
file:FOUNDRY_URL=http://localhost:30000 FOUNDRY_USERNAME=your_username FOUNDRY_PASSWORD=your_password
Comparison Table
Feature | Local REST API Module | Username/Password |
---|---|---|
Privacy | ā 100% Local | ā 100% Local |
Security | ā API Key auth | ā ļø Password auth |
Performance | ā Direct API access | ā ļø WebSocket only |
Features | ā Complete API access | ā Limited functionality |
Setup | ā ļø Module install required | ā Simple credentials |
Reliability | ā Stable API | ā ļø Connection dependent |
Required Permissions (All Methods)
Your FoundryVTT user needs these permissions:
- View actors, items, scenes, and journals
- Create and modify journal entries (for content generation)
- Access compendium data
- Use dice rolling API
Usage
Basic Queries
Ask your AI assistant things like:
Dice Rolling:
- "Roll 1d20+5 for an attack roll"
- "Roll 4d6 drop lowest for ability scores"
- "Roll 2d10+3 for damage"
Game Data:
- "Show me all the NPCs in this scene"
- "Find magic weapons in the party's inventory"
- "What's the current combat initiative order?"
- "Search for healing potions"
Content Generation:
- "Generate a random NPC merchant"
- "Create loot for a CR 5 encounter"
- "Generate a tavern with NPCs and plot hooks"
Advanced Features
Rule Lookups:
- "Look up the grappling rules"
- "How does the Fireball spell work?"
- "What are the conditions for being frightened?"
Tactical Advice:
- "Suggest tactics for fighting a dragon"
- "What should our wizard do this turn?"
- "Analyze this combat encounter"
World Building:
- "Create a mysterious forest location"
- "Generate a side quest involving missing merchants"
- "Design a magic item appropriate for level 8 characters"
Available Tools
Data Access
search_actors
- Find characters, NPCs, monsterssearch_items
- Find equipment, spells, consumablessearch_journals
- Search notes and handoutsget_scene_info
- Current scene detailsget_actor_details
- Detailed character information
Game Mechanics
roll_dice
- Roll dice with any formulaupdate_actor_hp
- Modify character healthget_combat_status
- Combat state and initiativelookup_rule
- Game rules and spell descriptions
Content Generation
generate_npc
- Create random NPCsgenerate_loot
- Create treasure appropriate for levelroll_table
- Random encounters, events, weathersuggest_tactics
- Combat advice and strategy
Diagnostics & System Health
get_system_health
- Server performance and health metricsget_recent_logs
- Retrieve filtered FoundryVTT logssearch_logs
- Search logs with regex patternsdiagnose_errors
- Analyze errors with troubleshooting suggestions
Available Resources
The server exposes these FoundryVTT resources:
foundry://world/info
- World and campaign informationfoundry://world/actors
- All actors in the worldfoundry://scene/current
- Current active scenefoundry://combat/current
- Active combat statefoundry://compendium/spells
- Spell databasefoundry://compendium/monsters
- Monster database
Configuration
Server Settings
Edit .env
to customize:
# Logging
LOG_LEVEL=info # debug, info, warn, error
# Performance
FOUNDRY_TIMEOUT=10000 # Request timeout (ms)
FOUNDRY_RETRY_ATTEMPTS=3 # Retry failed requests
CACHE_TTL_SECONDS=300 # Cache data for 5 minutes
Security
- Use API keys instead of passwords when possible
- Limit FoundryVTT user permissions to minimum required
- Run server on internal network only
- Monitor logs for suspicious activity
Diagnostics & Troubleshooting
Built-in Diagnostics
The server includes comprehensive diagnostic tools to help troubleshoot connection and performance issues:
Connection Testing:
# Test complete MCP connection and functionality
npm run test-connection
# Clean build and test setup
npm run setup
Diagnostic Tools (via AI assistant):
- System Health: "Get the FoundryVTT system health status"
- Error Analysis: "Diagnose recent errors and provide recommendations"
- Log Search: "Search logs for 'connection' patterns in the last hour"
- Recent Issues: "Show me recent error logs"
Advanced Diagnostics
When using the Local REST API module, you get access to advanced diagnostic features:
- š Real-time Log Analysis - Monitor FoundryVTT console output and notifications
- š System Health Metrics - Server performance, memory usage, and client connections
- šÆ Error Pattern Recognition - Automatic detection of common issues
- š” Smart Suggestions - Context-aware troubleshooting recommendations
- š Performance Monitoring - Track server uptime and response times
Connection Issues
# Test FoundryVTT connection
curl http://localhost:30000/api/status
# Check server logs
npm run dev # Shows detailed logging
Common Problems
"Failed to connect to FoundryVTT"
- Verify FOUNDRY_URL is correct
- Check if FoundryVTT is running
- Ensure API access is enabled
"Authentication failed"
- Verify API key or username/password
- Check user permissions in FoundryVTT
- Ensure user is not banned/restricted
"Tool not found" errors
- Update to latest server version
- Check tool name spelling
- Review available tools in logs
Development
Project Structure
src/
āāā config/ # Configuration management
āāā foundry/ # FoundryVTT client and types
āāā tools/ # MCP tool definitions
āāā resources/ # MCP resource definitions
āāā utils/ # Utilities and logging
āāā index.ts # Main server entry point
Adding New Tools
- Define tool schema in
src/tools/index.ts
- Add handler method in
src/index.ts
- Implement FoundryVTT API calls in
src/foundry/client.ts
- Add TypeScript types in
src/foundry/types.ts
- Test with your AI assistant
Testing
# Run tests
npm test
# Run with coverage
npm run test:coverage
# Lint code
npm run lint
Building
# Development build
npm run build
# Clean build
npm run clean && npm run build
API Reference
Environment Variables
Variable | Required | Description | Default |
---|---|---|---|
FOUNDRY_URL | ā | FoundryVTT server URL | - |
FOUNDRY_API_KEY | ā | API key for authentication | - |
FOUNDRY_USERNAME | ā | Username (if no API key) | - |
FOUNDRY_PASSWORD | ā | Password (if no API key) | - |
LOG_LEVEL | ā | Logging verbosity | info |
NODE_ENV | ā | Environment mode | development |
FOUNDRY_TIMEOUT | ā | Request timeout (ms) | 10000 |
FOUNDRY_RETRY_ATTEMPTS | ā | Retry failed requests | 3 |
CACHE_TTL_SECONDS | ā | Cache duration | 300 |
ā Either API key OR username/password required
Tool Schemas
roll_dice
{
"formula": "1d20+5",
"reason": "Attack roll against goblin"
}
search_actors
{
"query": "goblin",
"type": "npc",
"limit": 10
}
generate_npc
{
"race": "human",
"level": 5,
"role": "merchant",
"alignment": "neutral good"
}
Integration Examples
Claude Desktop Configuration
Add to your Claude Desktop MCP settings:
{
"mcpServers": {
"foundry": {
"command": "node",
"args": ["/path/to/foundry-mcp-server/dist/index.js"],
"env": {
"FOUNDRY_URL": "http://localhost:30000",
"FOUNDRY_API_KEY": "your_api_key_here"
}
}
}
}
Custom MCP Client
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
const transport = new StdioClientTransport({
command: "node",
args: ["./dist/index.js"],
});
const client = new Client(
{
name: "foundry-client",
version: "1.0.0",
},
{
capabilities: {},
},
);
await client.connect(transport);
// Roll dice
const result = await client.request({
method: "tools/call",
params: {
name: "roll_dice",
arguments: {
formula: "1d20+5",
reason: "Initiative roll",
},
},
});
Roadmap
Version 0.2.0
- Combat management tools (start/end combat, advance initiative)
- Token manipulation (move, update status effects)
- Scene navigation and switching
- Playlist controls and ambient audio
Version 0.3.0
- Character sheet editing (level up, add equipment)
- Journal entry creation and editing
- Macro execution and management
- Advanced content generation (dungeons, NPCs with full stats)
Version 1.0.0
- Multi-world support
- User permission management
- Webhook support for external triggers
- Performance optimization and caching
- Full test coverage
- Docker deployment
Documentation
Complete API documentation is available in the docs/
directory, auto-generated from TypeScript source code and JSDoc comments.
š Viewing Documentation
Local development:
npm run docs # Generate documentation
npm run docs:serve # Generate and serve locally
Online: Browse the docs/
folder in this repository or visit the GitHub Pages site (if enabled).
š What's Documented
- FoundryClient API - Complete client documentation with examples
- TypeScript Interfaces - All data structures and type definitions
- Configuration - Environment variables and setup options
- Utilities - Helper functions and logging
- Usage Examples - Code samples for common operations
The documentation is automatically updated via GitHub Actions when source code changes.
Contributing
- Fork the repository
- Create a feature branch:
git checkout -b feature/amazing-feature
- Make your changes and add tests
- Commit:
git commit -m 'Add amazing feature'
- Push:
git push origin feature/amazing-feature
- Open a Pull Request
Code Style
- Use TypeScript strict mode
- Follow existing naming conventions
- Add JSDoc comments for public APIs
- Write tests for new functionality
- Use meaningful commit messages
License
MIT License - see file for details.
Troubleshooting
š Quick Diagnostics
npm run test-connection # Test FoundryVTT connectivity
npm run setup-wizard # Re-run interactive setup
š„ Health Check
Use the get_health_status
MCP tool for comprehensive diagnostics, or check server logs during startup for detailed status information.
š Common Issues
- Connection refused: Ensure FoundryVTT is running on the configured port
- Authentication failed: Verify API key or username/password in
.env
- Empty search results: Install and enable the "Foundry Local REST API" module
- Limited functionality: REST API module required for full features
š Detailed troubleshooting guide:
Support
- Issues: GitHub Issues for bugs and feature requests
- Discord: FoundryVTT Discord #api-development
- Documentation: FoundryVTT API Docs
- Troubleshooting:
Acknowledgments
- FoundryVTT team for the excellent VTT platform
- Anthropic for the Model Context Protocol
- The tabletop gaming community for inspiration and feedback
Happy Gaming! š²