Back to browse
DollhouseMCP 2.0, open-source MCP composable AI building blocks

DollhouseMCP 2.0, open-source MCP composable AI building blocks

by mickdarling·Apr 14, 2026·3 points·0 comments

AI Analysis

●●SolidBig BrainNiche Gem

Identity-based permissioning changes AI capabilities per active persona stack.

Strengths
  • Permission surfaces change dynamically based on which elements are activated
  • 38 bundled starter elements accelerate customization without building from scratch
  • MCP-AQL semantic endpoints enable LLM discovery of server capabilities at runtime
Weaknesses
  • MCP server ecosystem is becoming crowded with similar customization tools
  • AGPL license may limit commercial adoption compared to MIT alternatives
Category
Target Audience

AI developers, MCP ecosystem users

Similar To

Continue.dev · Cline · Windsurf

Post Description

Hi, I'm Mick. I've been building this for the last 9 months

DollhouseMCP 2.0 is an open-source MCP server for making and using composable building blocks for AI customization. You build elements as portable MD and YAML files, compose them into stacks, and activate the stacks in any MCP-compatible client.

Element types that drive behavior and permissions:

* Personas: behavioral profiles (how the AI sounds and acts)

* Skills: discrete capabilities (what the AI can do)

* Agents: goal-oriented, multi-step executors

* Ensembles: composed stacks of the above

* Plus templates for structured outputs and memories for persistent context.

Two things I think are actually new here:

1. Identity-based permissioning. When you activate a persona, skill, agent, or ensemble, its permission policy takes effect in the server. Same client, same LLM, different permission surface depending on which active elements are loaded. A read-only analyst persona blocks creates and deletes regardless of what the client allows. A security-focused ensemble can deny specific destructive operations. This runs server-side, after the client approves the call, so policy cannot be overridden by the LLM or the client.

2. A bimodal agent loop. Agents do not run free inside the LLM. Every step hands control back to the MCP server, which evaluates the proposed operation against the active permission stack, runs autonomy and risk checks, enforces any hard blocks, then returns a decision to the LLM with continue, pause, or escalate guidance. The LLM acts on what it is allowed to do, describes the next step, and hands back to the server. The loop repeats until the goal completes or a human is asked to intervene. Higher agency stays observable and bounded instead of opaque.

There's also a audit trail of approved and denied actions a danger zone lockout that will prevent the LLM from doing truly dangerous things if they go through the MCP server. And any active Dollhouse agent that is running through the DollhouseMCP server has it's actions evaluated every step.

I added easy configuration through the web console for a wide variety of MCP clients if you use the one-liner, and there are logs and metrics as well as the local and github hosted portfolio and collection to save your Dollhouse elements and share and use other's. They are all validated and scanned several times along the their distribution path to keep things as safe as we can.

The one-liner install: npx @dollhousemcp/mcp-server@latest --web

Happy to go deep on the permissioning model, the bimodal agent loop, composition patterns, YAML schema, or anything else.

Home: https://dollhousemcp.com Repo: https://github.com/DollhouseMCP/mcp-server Collection: https://collection.dollhousemcp.com

Hope you like it.

Similar Projects

Security●●Solid

Security Scanner for Agent Skills and MCP

Finally a security linter for MCP configs before you accidentally execute a prompt injection payload.

Solve My ProblemShip It
lirantal
701mo ago
Developer Tools●●Solid

Agnix – lint your AI agent configs (Claude.md, skills, MCP, hooks)

Makes agent configs first-class with 229 domain-specific rules, autofix, and LSP support — so a tiny syntax mistake stops being a silent failure. The cross-editor plugins and GitHub Action are the standout moves: lint in your IDE and enforce checks in CI. I want a clearer map of which rules target which toolchains, but the breadth of integrations is impressive.

Niche GemSolve My ProblemSlick
anotherCodder
113mo ago
AI/MLMid

A Steve Jobs in Your Pocket AI Skill

Packages product-thinking into an Agent Skill so your agent can answer like 'Steve Jobs' — heuristics, constraints and example responses live inside a deployable skill compatible with MCP-enabled platforms. Clever and immediately useful for design critiques, but the post prioritizes argument over onboarding: show the skill manifest, install steps and sample inputs up front and this would convert curiosity into actual usage.

Niche GemShip It
stubbi
203mo ago