DollhouseMCP
Manage personas, skills, templates, agents, and memories in one OSS MCP layer so every coding session matches how you actually work.
Overview
io.github.DollhouseMCP/mcp-server is a Build-phase MCP server that lets you create and manage personas, skills, templates, agents, and memories to customize your AI tooling.
What is this MCP server?
- OSS MCP server for Personas, Skills, Templates, Agents, and Memories
- npm @dollhousemcp/mcp-server v2.0.8 with stdio transport
- Central place to customize AI experience beyond default system prompts
- Supports reusable skill and template libraries for repeat solo-builder workflows
- Server version 2.0.8
- npm package @dollhousemcp/mcp-server
Community signal: 35 GitHub stars.
What problem does it solve?
Default agent behavior and ad-hoc prompts do not scale when you need consistent personas, skills, and memories across many solo-builder projects.
Who is it for?
Builders who treat agents as a long-lived workstation and want OSS-controlled customization instead of one-off system prompt hacks.
Skip if: Teams that only need a single fixed skill with no persona or memory management overhead.
What do I get? / Deliverables
After registration, you maintain structured Dollhouse artifacts via MCP so agents load the right persona, skills, templates, and memories per task.
- Managed personas, skills, templates, agents, and memory records via MCP
- Reusable customization layer across multiple projects
- Version 2.0.8 DollhouseMCP server wired into local agent config
Recommended MCP Servers
Journey fit
Customizing agent behavior is foundational agent-tooling during build, but the same persona and memory assets carry into ship review habits and grow support tone. DollhouseMCP is the customization plane for MCP hosts—structured artifacts that define who the agent is and what it remembers, not a single API integration.
How it compares
Agent customization and memory MCP platform, not a one-shot codegen skill or external API bridge.
Common Questions / FAQ
Who is io.github.DollhouseMCP/mcp-server for?
Solo and indie developers who want an open-source MCP layer to define personas, skills, templates, agents, and memories for their coding agents.
When should I use io.github.DollhouseMCP/mcp-server?
Use it while building your agent toolchain and whenever you need repeatable agent identity and memory across validate, ship, and grow tasks—not only during initial setup.
How do I add io.github.DollhouseMCP/mcp-server to my agent?
Install @dollhousemcp/mcp-server v2.0.8 via npm, add the stdio MCP entry in Claude Code or Cursor, and configure personas and memories per DollhouseMCP documentation on GitHub.