Switching between "act as my CFO" and "now think like a CTO" prompts works -- sort of. But every time you switch, Claude loses the role. The analysis gets shallow. There's no framework, no structure, no memory of what the CEO said when the CFO takes over.
StudioMeyer Crew is an MCP server that gives Claude 8 expert personas with real business frameworks. Activate a CEO, and Claude uses Porter's Five Forces. Switch to CFO, and Claude runs unit economics with your actual numbers. Zero extra API cost -- runs entirely in your Claude subscription.
What does Crew actually do?
Instead of writing long system prompts yourself, you activate a persona with one command:
"Activate the CEO persona."
Claude instantly adopts the role -- with domain-specific frameworks, output formats, decision patterns, and constraints. Not a generic "act like a CEO" prompt, but a battle-tested system prompt with few-shot examples and anti-patterns.
8 Built-in Personas
| Persona | Category | What they bring |
|---|---|---|
| CEO | Business | Strategy, vision, Porter's Five Forces, SWOT, delegation frameworks |
| CFO | Business | Unit economics, ROI analysis, pricing models, budget planning |
| CMO | Business | Growth strategy, AARRR funnel, content marketing, SEO/GEO |
| CTO | Tech | Architecture review, DORA metrics, tech debt assessment, code review |
| PM | Business | RICE/ICE scoring, user stories, PRD generation, JTBD framework |
| Analyst | Ops | Market research, competitive intelligence, data analysis |
| Support | Ops | Customer communication, FAQ writing, onboarding guides |
| Creative | Creative | Brand voice, copy, storytelling, design briefs |
10 Tools
| Tool | What it does |
|---|---|
crew_activate | Switch to a persona (loads frameworks + memory context) |
crew_deactivate | Back to default Claude |
crew_list | Show all available personas |
crew_status | Who am I right now? Duration, token estimate |
crew_feedback | Rate the persona (1-5) |
crew_create | Build your own custom persona |
crew_delete | Remove a custom persona |
crew_workflow_list | Available multi-persona workflows |
crew_workflow_run | Run a full workflow (e.g. CEO then CFO then CTO) |
crew_guide | Help and onboarding |
Getting started: 30 seconds
Add the server URL in Claude Desktop or Cursor:
https://crew.studiomeyer.io/mcp
Or via Claude Code:
claude mcp add crew --transport streamable-http https://crew.studiomeyer.io/mcp
Works with Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and Zed.
What you can actually do with it
Strategy session in 5 minutes
"Activate CEO. Review our pricing strategy: we have 4 MCP products ranging from free to $49/month."
Claude as CEO runs a structured analysis: market positioning, competitive landscape, pricing psychology, revenue projections. Not a vague opinion -- a framework-driven assessment with clear recommendations.
Financial sanity check
"Switch to CFO. Are these unit economics sustainable?"
The CFO persona calculates: customer acquisition cost, lifetime value, margin per tier, break-even timeline. With actual numbers, not hypotheticals.
Multi-persona workflows
The real power: chaining personas. Three built-in workflows:
| Workflow | Personas | What happens |
|---|---|---|
| Strategy Review | CEO, then CFO, then CTO | CEO defines strategy, CFO validates finances, CTO checks feasibility |
| Content Pipeline | CMO, then Analyst, then Creative | CMO plans content, Analyst fact-checks, Creative polishes |
| Product Launch | Analyst, PM, CEO, CMO, CTO | Full launch analysis from research to go-live checklist |
"Run the strategy review workflow for our Q2 plans."
Each persona builds on the previous one's output. The CFO doesn't repeat what the CEO said -- they challenge it.
Memory Bridge
If you also use StudioMeyer Memory, Crew automatically loads relevant context when activating a persona. The CFO searches for "revenue, costs, pricing decisions" in your memory. The CTO loads "architecture, tech stack, dependencies."
No manual context switching. The persona knows your history.
What makes this different
| Feature | StudioMeyer Crew | DollhouseMCP | Ruflo |
|---|---|---|---|
| Personas | 8 (deep, with frameworks) | 150+ (generic) | 60+ (swarm) |
| Memory integration | StudioMeyer Memory | None | Own DB (AgentDB) |
| Multi-persona workflows | 3 built-in | None | Swarm topology |
| Custom personas | Yes (Markdown + YAML) | No | No |
| API cost | $0 (Claude subscription) | $0 | Requires API keys |
| Domain frameworks | DORA, Porter, AARRR, RICE | Generic prompts | Generic prompts |
The key difference: Crew personas aren't just role descriptions. They include decision frameworks, few-shot examples, output format constraints, and anti-patterns. A CFO persona that says "consider ROI" is useless. A CFO persona that runs a 5-year DCF model with your inputs is useful.
Custom personas
Don't need a CFO but need a Legal Advisor? Create your own:
"Create a persona called Legal Advisor, focused on contract review, GDPR compliance, and risk assessment."
Crew saves it as a Markdown file with YAML frontmatter. Your custom personas persist across sessions and work exactly like built-in ones.
Pricing
Free. All 10 tools, all 8 personas, all 3 workflows. No API keys, no credit system, no hidden costs. Runs in your existing Claude subscription.
We built Crew because we got tired of writing the same "act as my CFO" prompts and getting shallow results every time. Eight personas, tested across hundreds of real business decisions at StudioMeyer. If you want Claude to think like an expert instead of a generalist -- try it.
