DollhouseMCP
Project Status
Build & Quality
Technology
🌐 Repository: https://github.com/DollhouseMCP/mcp-server
🏪 Collection: https://github.com/DollhouseMCP/collection
📦 NPM Package: https://www.npmjs.com/package/@dollhousemcp/mcp-server
🌍 Website: https://dollhousemcp.com
Elements That Customize Your AI's Capabilities and Actions
DollhouseMCP is open source, community-powered AI customization. Create your own customization elements—personas that shape behavior, skills that add capabilities, templates for consistent outputs, and agents for automation—or use and modify an ever-growing number of customization elements from the community. Every element you create can be saved to your portfolio and used again or shared back to the DollhouseMCP Collection to help others.
What Are Customization Elements?
- Personas – Shape how your AI acts and responds in specific domains
- Skills – Add specialized capabilities your AI can use
- Templates – Ensure consistent, high-quality outputs
- Agents – Enable autonomous task completion with smart decision-making
Core Capabilities
- 🌍 Community Element Library – A growing number of tested personas, skills, templates, and agents
- ✨ Create Custom Elements – Create personas, skills, templates, and agents from scratch using natural language
- 🤝 Open Source – AGPL-3.0 licensed, ensuring community contributions stay free
- 📚 The DollhouseMCP Collection – Install any community element with one command
- 🛠️ 41 Professional Tools – Complete toolkit for element creation and management
- 🛡️ Security-First Validation – All elements validated against hundreds of attack vectors
- ⚡ Hot-Swap Elements – Change personas, skills, and templates without restarting as needed
- 📦 Personal Portfolio – Your library of custom AI configurations on your local computer or personal GitHub repo
Use Cases
Get Started
npm install @dollhousemcp/mcp-server
See Quick Start for complete setup instructions.
🎯 Element Types: Available Now & Coming Soon
✅ Available Now
🎭 Personas
Shape how your AI behaves and responds
- Creative Writer - Imaginative storyteller for engaging narratives
- Business Consultant - Strategic advisor for business decisions
- Debug Detective - Systematic problem-solver for code issues
- Security Analyst - Vulnerability assessment and threat analysis
- Technical Analyst - Deep dive technical documentation
- Use:
"Activate the creative writer persona"
💡 Skills
Add specialized capabilities your AI can use
- Code Review - Analyze code quality and suggest improvements
- Data Analysis - Statistical analysis and visualization
- Language Translation - Multi-language communication
- API Integration - Connect and interact with external services
- Testing Automation - Generate and run test suites
- Use:
"Enable the code review skill"
📝 Templates
Ensure consistent, high-quality outputs
- Project Proposal - Structured business proposals
- Penetration Test Report - Security assessment documentation
- Meeting Notes - Organized meeting summaries
- Code Review - Systematic code evaluation format
- Documentation - Technical documentation structure
- Use:
"Use the project proposal template"
🤖 Agents
Enable autonomous task completion
- Code Reviewer - Automated code quality assessment
- Task Manager - Project organization and tracking
- Research Assistant - Information gathering and synthesis
- Academic Researcher - Scholarly research and citations
- Security Fix Specialist - Vulnerability remediation
- Use:
"Run the code reviewer agent"
🔄 Coming Soon
🧠 Memory
Persistent context across sessions
- Project Context - Remember project details and decisions
- Learning Progress - Track skill development over time
- Personal Preferences - Store user-specific settings
- Conversation History - Maintain dialogue continuity
- Status: Coming Soon
🎯 Ensembles
Combine multiple elements as one unified entity
- Full-Stack Developer - Frontend + Backend + DevOps skills
- Writing Suite - Creative + Technical + Editorial capabilities
- Security Team - Analyst + Auditor + Remediation skills
- Data Science Platform - Analysis + Visualization + ML skills
- Status: Coming Soon
External function calls and commands
- Git Operations - Version control management
- Database Queries - Direct database interaction
- API Calls - External service integration
- File Operations - Advanced file manipulation
- Status: Planned
📋 Prompts
Reusable instruction sets
- Code Review Checklist - Systematic review steps
- Security Audit Guide - Vulnerability assessment process
- Writing Guidelines - Style and tone instructions
- Debug Workflow - Problem-solving methodology
- Status: Planned
💬 Natural Language Usage Examples
DollhouseMCP is designed for natural language interaction. Just describe what you want in plain English - you don't need to be overly specific, the system will figure it out.
Natural Language Examples:
"Show me all the personas in the Dollhouse Collection""What creative writing personas are available?""Install the storyteller persona from the collection""Search for Python development skills""Find templates for technical documentation"
Direct Commands (if you prefer):
browse_collection type="personas"
search_collection "creative writing"
install_content "personas/storyteller.md"
Managing Your Portfolio
Natural Language Examples:
"What's in my portfolio?""Show me all my custom personas""Sync my portfolio with GitHub""Create a backup of my elements""Search my portfolio for marketing templates"
Direct Commands (if you prefer):
portfolio_status
list_elements type="personas"
sync_portfolio
search_portfolio "marketing"
Working with Elements
Natural Language Examples:
"Activate the code reviewer persona""What's currently active?""Switch to creative writing mode""Deactivate all elements""Show me details about the data analyst skill""Create a new persona for customer support""Edit the email template to be more formal"
Direct Commands (if you prefer):
activate_element "code-reviewer" type="personas"
get_active_elements
deactivate_element type="personas"
get_element_details "data-analyst" type="skills"
create_element type="personas" name="customer-support"
Complete Workflow Example
Here's how a typical session might look:
You: "I need help with creative writing"
Assistant: "I'll help you with creative writing. Let me check what personas are available..."
You: "Show me creative writing personas in the collection"
Assistant: [Shows list of available creative writing personas]
You: "Install and activate the storyteller persona"
Assistant: "I've installed and activated the Storyteller persona. I'm now ready to help craft engaging narratives..."
You: "Actually, let me create my own persona for science fiction writing"
Assistant: "I'll help you create a custom science fiction writing persona. What characteristics would you like?"
You: "Make it focus on hard sci-fi with attention to scientific accuracy"
Assistant: [Creates custom persona with specified traits]
You: "Save that to my portfolio as 'Hard SciFi Writer'"
Assistant: "I've saved 'Hard SciFi Writer' to your portfolio. You can activate it anytime."
Pro Tips
- Be conversational:
"Help me write better code" works as well as specific commands - Stack elements:
"Activate both the code reviewer and the Python expert" - Save your favorites:
"Save this configuration as my default setup" - Share with others:
"Submit my custom persona to the community collection"
🚀 Quick Start
Choose Your Installation Method
Method 1: Local Installation (Recommended)
Create a dedicated folder for your MCP servers and install there:
# Create MCP servers directory
mkdir ~/mcp-servers
cd ~/mcp-servers
# Install DollhouseMCP
npm install @dollhousemcp/mcp-server
Configure Claude Desktop:
Add to your config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"dollhousemcp": {
"command": "node",
"args": ["/Users/YOUR_USERNAME/mcp-servers/node_modules/@dollhousemcp/mcp-server/dist/index.js"]
}
}
}
💡 Pro tip: Replace /Users/YOUR_USERNAME with your actual home directory path.
Method 2: Always Latest with npx
No installation needed! Configure Claude Desktop to always use the latest version:
{
"mcpServers": {
"dollhousemcp": {
"command": "npx",
"args": ["@dollhousemcp/mcp-server@latest"]
}
}
}
📝 Note: The @latest tag ensures you always get the newest version. Remove it to use npm's cached version.
Method 3: Global Installation
# Install globally (may require sudo/admin)
npm install -g @dollhousemcp/mcp-server
Configure Claude Desktop:
{
"mcpServers": {
"dollhousemcp": {
"command": "dollhousemcp"
}
}
}
⚠️ Warning: Only one version system-wide. Consider local installation for more flexibility.
🎯 Advanced: Multiple Configurations
Want separate portfolios for different contexts? Create multiple local installations:
# Personal assistant
mkdir ~/mcp-servers/personal
cd ~/mcp-servers/personal
npm install @dollhousemcp/mcp-server
# Work assistant
mkdir ~/mcp-servers/work
cd ~/mcp-servers/work
npm install @dollhousemcp/mcp-server
# Creative writing
mkdir ~/mcp-servers/creative
cd ~/mcp-servers/creative
npm install @dollhousemcp/mcp-server
Configure each with its own portfolio:
{
"mcpServers": {
"dollhouse-personal": {
"command": "node",
"args": ["/Users/YOU/mcp-servers/personal/node_modules/@dollhousemcp/mcp-server/dist/index.js"],
"env": {
"DOLLHOUSE_PORTFOLIO_DIR": "/Users/YOU/portfolios/personal"
}
},
"dollhouse-work": {
"command": "node",
"args": ["/Users/YOU/mcp-servers/work/node_modules/@dollhousemcp/mcp-server/dist/index.js"],
"env": {
"DOLLHOUSE_PORTFOLIO_DIR": "/Users/YOU/portfolios/work"
}
}
}
}
Now you can enable/disable different configurations in Claude Desktop as needed!
✅ Verify Installation
After configuring and restarting Claude Desktop, test with:
list_elements type="personas"
You should see your available personas. If not, check the Troubleshooting section.
📁 Default Portfolio Location
By default, your elements are stored in:
- macOS/Linux:
~/.dollhouse/portfolio/ - Windows:
%USERPROFILE%\.dollhouse\portfolio\
Use the DOLLHOUSE_PORTFOLIO_DIR environment variable to customize this location.
🎯 Getting Started
Once installed, try these commands in Claude:
# Browse available personas
list_elements type="personas"
# Activate a persona
activate_element name="creative-writer" type="personas"
# Browse the community collection
browse_collection type="personas"
# Search for specific content
search_collection query="python" type="skills"
📘 New User? Follow our Roundtrip Workflow Guide for a complete walkthrough of discovering, customizing, and sharing AI elements with the community.
✨ Key Features
| Feature | Description |
|---|
| 🎭 41 MCP Tools | Complete portfolio element management through chat interface |
| 🏪 GitHub Collection | Browse, search, install, and submit personas to community collection |
| 🔄 Roundtrip Workflow | Complete cycle: discover → customize → share → collaborate |
| 📁 GitHub Portfolio | Personal repository for storing and versioning your AI elements |
| 👤 User Identity System | Environment-based attribution for persona creators |
| 🆔 Unique ID System | Advanced ID generation: {type}_{name}_{author}_{YYYYMMDD}-{HHMMSS} |
| 💬 Chat-Based Management | Create, edit, and validate personas through conversational interface |
| 🔄 Real-time Operations | Live editing with automatic version bumping and validation |
| 📦 NPM Installation | Install MCP servers from npm with cross-platform support and atomic operations |
| 🛡️ Data Protection | Copy-on-write for default personas, comprehensive backup system |
| 🏠 Local-First Architecture | Full functionality without cloud dependency |
🎨 Portfolio System
The DollhouseMCP Portfolio system provides a comprehensive framework for managing AI elements locally and in the cloud.
Portfolio Structure
Your portfolio is organized by element type:
~/.dollhouse/portfolio/
├── personas/ # Behavioral profiles
├── skills/ # Discrete capabilities
├── templates/ # Reusable content structures
├── agents/ # Goal-oriented actors
├── memories/ # Persistent context
└── ensembles/ # Element combinations
Key Features
- Local-First Architecture: All elements stored locally with optional cloud sync
- GitHub Integration: Sync your portfolio with GitHub for backup and sharing
- Version Control: Full git integration for tracking changes
- Smart Detection: Automatically identifies element types from content
- Flexible Naming: Use any naming convention you prefer
Use the comprehensive set of MCP tools to manage your portfolio:
list_portfolio_elements - View all elements across typessync_portfolio - Synchronize with GitHubupload_to_portfolio - Share elements with the communitydownload_from_portfolio - Get elements from GitHub
For detailed portfolio documentation, see the Portfolio Guide.
🔒 Security
DollhouseMCP implements enterprise-grade security measures to protect your data and ensure safe operation.
Security Features
- Input Sanitization: All user inputs validated and sanitized
- Path Traversal Prevention: Filesystem access strictly controlled
- YAML Injection Protection: Safe parsing with validation
- Command Injection Prevention: No direct shell command execution
- Token Encryption: OAuth tokens encrypted at rest
- Rate Limiting: API calls throttled to prevent abuse
- Audit Logging: Security events tracked for analysis
Security Testing
- Automated Security Scanning: GitHub Advanced Security enabled
- Dependency Scanning: Automated vulnerability detection
- Code Analysis: Static analysis with CodeQL
- Secret Scanning: Prevents credential leaks
Reporting Security Issues
If you discover a security vulnerability, please:
- DO NOT create a public GitHub issue
- Open a private security advisory on GitHub
- Include steps to reproduce if possible
- Allow up to 48 hours for initial response
For more details, see our Security Policy.
🛠️ Development
Getting Started
# Clone the repository
git clone https://github.com/DollhouseMCP/mcp-server.git
cd mcp-server
# Install dependencies
npm install
# Build the project
npm run build
# Run tests
npm test
Development Workflow
- Create Feature Branch:
git checkout -b feature/your-feature - Make Changes: Implement your feature or fix
- Run Tests:
npm test - Build:
npm run build - Submit PR: Create pull request to develop branch
Available Scripts
npm run build - Compile TypeScriptnpm run dev - Development mode with watchnpm test - Run test suitenpm run lint - Check code stylenpm run typecheck - TypeScript type checking
Project Structure
src/
├── index.ts # Main server entry
├── tools/ # MCP tool implementations
├── utils/ # Utility functions
├── types/ # TypeScript definitions
└── elements/ # Element system
For detailed development guides, see Development Documentation.
🏭 Architecture
System Overview
DollhouseMCP follows a modular, extensible architecture built on the Model Context Protocol (MCP) standard.
Core Components
MCP Server
- Transport: StdioServerTransport for Claude Desktop integration
- Protocol: JSON-RPC 2.0 communication
- Tools: 41 MCP tools for comprehensive functionality
Element System
- BaseElement: Abstract base class for all elements
- IElement Interface: Common contract for elements
- Element Types: Personas, Skills, Templates, Agents, Memories, Ensembles
Portfolio Manager
- Local Storage: File-based element storage
- GitHub Sync: Git-based synchronization
- Version Control: Full git integration
Security Layer
- Input Validation: All inputs sanitized
- Path Security: Traversal prevention
- Token Management: Encrypted storage
Data Flow
- Client Request → MCP Server
- Tool Routing → Appropriate handler
- Element Processing → Element system
- Storage → Portfolio manager
- Response → Client
For detailed architecture documentation, see Architecture Guide.
🎯 Troubleshooting
Common Issues
MCP Server Not Connecting
Symptoms: Claude Desktop doesn't show DollhouseMCP in available servers
Solutions:
- Verify configuration file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- Check JSON syntax is valid
- Restart Claude Desktop after configuration changes
OAuth Authentication Fails
Symptoms: Cannot authenticate with GitHub
Solutions:
- Check internet connection
- Verify GitHub account has proper permissions
- Try using Personal Access Token instead:
export GITHUB_TOKEN=your_pat_token
- Clear cached credentials and retry
Elements Not Loading
Symptoms: Portfolio appears empty
Solutions:
- Check portfolio directory exists:
~/.dollhouse/portfolio/ - Verify file permissions
- Run
list_portfolio_elements tool to diagnose - Check element file format (YAML frontmatter required)
Symptoms: Slow response times
Solutions:
- Check portfolio size (large portfolios may be slow)
- Verify adequate system resources
- Consider using pagination for large lists
- Check network latency for GitHub operations
Getting Help
For detailed troubleshooting, see Troubleshooting Guide.
🤝 Contributing
We welcome contributions to DollhouseMCP! Here's how you can help:
Ways to Contribute
- 🐛 Report Bugs: Open an issue with reproduction steps
- ✨ Request Features: Suggest new functionality
- 📝 Improve Documentation: Fix typos, add examples
- 💻 Submit Code: Fix bugs or implement features
- 🎨 Share Elements: Contribute personas, skills, templates
Development Process
- Fork the Repository
gh repo fork DollhouseMCP/mcp-server
- Create Feature Branch
git checkout -b feature/your-feature
- Make Changes
- Follow existing code style
- Add tests for new functionality
- Update documentation
- Test Thoroughly
npm test
npm run lint
npm run typecheck
- Submit Pull Request
- Target the
develop branch - Provide clear description
- Reference any related issues
Code Style
- TypeScript with strict mode
- ESLint configuration provided
- Prettier for formatting
- Comprehensive JSDoc comments
Commit Messages
Follow conventional commits:
feat: New featurefix: Bug fixdocs: Documentationtest: Testingchore: Maintenance
Review Process
- Automated CI checks must pass
- Code review by maintainers
- Address feedback
- Merge when approved
For detailed guidelines, see CONTRIBUTING.md.
📚 Resources
Documentation
Repositories
External Resources
Learning Materials
- Tutorials (coming soon)
- Building Your First Persona
- Creating Custom Skills
- Portfolio Management Best Practices
- GitHub Integration Setup
- Videos (coming soon)
- Installation Walkthrough
- Feature Demonstrations
- Developer Tutorials
Support
🏷️ Version History
v1.8.1 - September 15, 2025
CI Reliability Improvements: Fixed persistent test failures across platforms
🔧 Bug Fixes
- GitHub API 409 Conflicts: Enhanced retry mechanism with jitter for parallel CI jobs
- Windows Performance Tests: Platform-specific timing thresholds for CI environments
- Test Stability: Resolved flaky tests in Extended Node Compatibility workflow
v1.8.0 - September 15, 2025
Major Portfolio System Enhancements: Full GitHub portfolio synchronization
✨ New Features
- Portfolio Sync: Complete bidirectional sync with GitHub portfolios
- Pull Functionality: Download elements from GitHub portfolios (3 sync modes)
- Configurable Repos: Portfolio repository names now configurable
- Configuration Wizard: Now manual-only (removed auto-trigger for better UX)
🔧 Improvements
- Tool Clarity: Renamed conflicting tools for better user experience
- Rate Limiting: Fixed redundant token validation causing API limits
- GitHub Integration: Comprehensive repository management
v1.7.4 - September 12, 2025
Hotfix Release: Critical build and registration fixes
🔧 Bug Fixes
- Build Infrastructure: Fixed missing TypeScript files in dist
- Tool Registration: Resolved MCP tool availability issues
- Skill System: Fixed skill registration and activation
- Test Framework: Restored test infrastructure functionality
v1.7.3 - September 9, 2025
Security & Configuration Release: Prototype pollution protection and config management
🛡️ Security
- Prototype Pollution Protection: Comprehensive validation against injection attacks
- YAML Security: Maintained FAILSAFE_SCHEMA with security documentation
- Security Audit: Achieved 0 security findings across all severity levels
✨ Improvements
- Configuration Management: Complete overhaul with atomic operations
- Test Coverage: Comprehensive security and configuration tests
- Input Normalization: All inputs normalized at MCP request layer
v1.7.2 - September 7, 2025
Security Patch Release: Critical logging vulnerability fixes
🛡️ Security Fixes
- Clear-text Logging Prevention: Comprehensive sanitization of sensitive data
- OAuth Token Protection: Prevents exposure of tokens in console output
- API Key Sanitization: Masks all credentials before logging
v1.7.1 - September 3, 2025
Maintenance Release: Documentation and compatibility improvements
🔧 Improvements
- Documentation: Updated for better clarity and accuracy
- Compatibility: Enhanced cross-platform support
- Bug Fixes: Various minor fixes and optimizations
v1.7.0 - August 30, 2025
Major Feature Release: Enhanced portfolio and collection systems
✨ New Features
- Portfolio Management: Improved local portfolio organization
- Collection Integration: Better integration with community collection
- Security Enhancements: Critical security fixes from code review
v1.6.11 - August 28, 2025
Test Reliability & Collection Fixes: Improved test suite stability and fixed collection system
🔧 Bug Fixes
- Collection Index URL: Fixed to use GitHub Pages for better reliability
- E2E Test Tokens: Improved token prioritization for CI environments
- Response Format: Enhanced compatibility with various response formats
- Type Safety: Improved TypeScript types throughout test suite
✨ Improvements
- Added helper functions for better code organization
- Enhanced test reliability in CI/CD pipelines
- General code quality improvements
v1.6.10 - August 28, 2025
Collection Submission Fix: Critical fix for collection submission pipeline
🔧 Bug Fixes
- Collection Submission: Fixed workflow failing due to missing element types
- Local Path Parameter: Added missing localPath parameter to submission tool
- Duplicate Detection: Added detection for duplicate portfolio uploads and collection issues
✨ Improvements
- Added comprehensive QA tests for collection submission validation
- Cleaned up QA documentation files
- Updated all documentation to v1.6.10
v1.6.9 - August 26, 2025
Critical Fixes: Fixed OAuth helper NPM packaging and performance testing workflow
🔧 Bug Fixes
- OAuth NPM Packaging: Fixed missing
oauth-helper.mjs file in NPM distribution- File was present in repository but not included in published package
- OAuth authentication now works correctly for NPM users
- Performance Tests: Fixed CI workflow running all tests instead of performance tests
- Performance monitoring now works correctly in GitHub Actions
v1.6.3 - August 25, 2025
OAuth Authentication Fix: Fixed invalid OAuth client ID and improved error handling
🔧 Bug Fixes
- OAuth Client ID: Updated from incorrect ID to correct
Ov23li9gyNZP6m9aJ2EP - Error Messages: Improved clarity of OAuth error messages for better debugging
- Setup Tool: Fixed
setup_github_auth tool to properly handle authentication flow
v1.6.2 - August 25, 2025
Critical Hotfix: Fixed OAuth default client ID not being used in setup_github_auth tool
🔧 Bug Fixes
- OAuth Default Client: Fixed
setup_github_auth tool not using default client ID when none provided - Authentication Flow: Restored ability to authenticate without manual client ID entry
📝 Documentation
- Added troubleshooting guide for OAuth issues
- Updated setup instructions with clearer OAuth configuration steps
v1.6.1 - August 25, 2025
⚠️ Breaking Changes:
- 🔄 Serialization Format Change -
BaseElement.serialize() now returns markdown with YAML frontmatter instead of JSON
🔧 Bug Fixes
- Serialization Format: Fixed
BaseElement.serialize() to return markdown format- Changed from JSON string to markdown with YAML frontmatter
- Maintains consistency with existing persona format
- Fixes portfolio round-trip workflow
✨ Improvements
- Code Quality: Extracted validation methods into ValidationService
- Error Handling: Improved validation error messages with specific field information
- Test Coverage: Added comprehensive tests for markdown serialization
v1.6.0 - August 25, 2025
🚀 Major Release: Portfolio System & OAuth Integration
This release introduces the complete portfolio management system with GitHub OAuth authentication, enabling secure cloud-based element synchronization and management.
✨ New Features
🔐 GitHub OAuth Authentication
- OAuth App Integration: Full OAuth flow with GitHub for secure authentication
- Personal Access Token Support: Alternative authentication method for CI/CD
- Token Management: Secure storage and rotation of authentication tokens
- Multi-Account Support: Handle multiple GitHub accounts seamlessly
📦 Portfolio Management System
- Cloud Sync: Automatic synchronization between local and GitHub portfolios
- Version Control: Full git integration for portfolio elements
- Conflict Resolution: Smart merging of local and remote changes
- Batch Operations: Upload/download multiple elements efficiently
setup_github_auth: Interactive GitHub OAuth setupcheck_github_auth: Verify authentication statusrefresh_github_token: Rotate OAuth tokenssync_portfolio: Bidirectional portfolio synchronizationupload_to_portfolio: Upload local elements to GitHubdownload_from_portfolio: Download elements from GitHubsubmit_to_portfolio: Submit elements for review- And 30 more tools for complete portfolio management
🔧 Bug Fixes
- Element Detection: Fixed smart detection of element types
- YAML Parsing: Improved handling of complex YAML structures
- Path Resolution: Fixed Windows path compatibility issues
- Token Security: Enhanced token storage encryption
📝 Documentation
- Comprehensive OAuth setup guide
- Portfolio management tutorials
- Troubleshooting guides for common issues
- API documentation for all new tools
🔒 Security
- OAuth token encryption at rest
- Secure token transmission
- Rate limiting for API calls
- Audit logging for all operations
For complete release history prior to v1.6.0, see the GitHub Releases page.
📜 License
This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0) with Platform Stability Commitments.
What This Means
✅ You CAN:
- Use the software for personal projects
- Use the software for commercial projects
- Modify the source code
- Distribute the software
- Use personas and elements you create
⚠️ You MUST:
- Include the license and copyright notice
- State changes made to the code
- Disclose your source code when distributing
- Use the same AGPL-3.0 license for derivatives
- Make network use source available (AGPL requirement)
❌ You CANNOT:
- Hold us liable for damages
- Use our trademarks without permission
- Claim warranty or guarantee of fitness
- Resell commercially
We provide additional guarantees beyond the AGPL-3.0:
- 90-day advance notice for monetization policy changes
- 12-month revenue sharing locks for content creators
- Full data portability - export all your content anytime
- 180-day transition period for platform ownership changes
- Community advisory input on major policy decisions
Contributor License Agreement
By contributing to DollhouseMCP, you agree that:
- You have the right to grant us license to your contribution
- Your contribution is licensed under AGPL-3.0
- You grant us additional rights to use your contribution in our commercial offerings
- You retain copyright to your contribution
For the complete license text, see LICENSE.
Questions?
If you have questions about the license or what you can do with DollhouseMCP:
Copyright © 2025 DollhouseMCP. All rights reserved.