Positioning framework, per-platform bio auditing, 4-pillar content system, growth-signal reads.
Positioning, bios, content pillars, platform strategy — the frameworks for building an audience that buys, not just watches.
Disclaimer. Structured positioning frameworks from documented practice. Growth varies with consistency, proof quality, and niche.
Every creator's AI assistant gets asked the same four questions: who is my content for, what should my bio say, what should I post, and which platform matters. Most agents answer with vibes. This MCP answers with frameworks and audits — and it refuses to let positioning outrun proof.
The house rule: positioning without receipts is a costume.
| Tool | What it returns |
|---|---|
get_positioning_framework | The niche statement formula (WHO x OUTCOME x HOW x RECEIPT), 4 checks, proof inventory, moat check |
audit_bio | PASS/NEEDS WORK per platform: char limits, hype titles, title-first openers, missing outcome |
get_bio_rules | Bio architecture per platform (tiktok, instagram, linkedin, x, youtube) |
get_content_pillars | The 4-pillar system: receipts ~30%, method ~40%, story ~20%, conversion ~10% |
get_platform_strategy | Each platform's strategic role, conversion path, cadence floor, watch-out |
interpret_growth_signal | What your growth pattern means (high views/flat followers, high DMs/low sales...) and the fix |
get_full_pack | Everything in one payload |
npx personal-brand-mcp # once published to npm
# or from source:
git clone https://github.com/closermethod/personal-brand-mcp && cd personal-brand-mcp && npm i && npm run build && node dist/main.js
Claude Desktop config:
{ "mcpServers": { "personal-brand": { "command": "npx", "args": ["personal-brand-mcp"] } } }
Get positioned (this one) → get seen (content-hooks-mcp) → get the reply (outbound-engine-mcp) → price the deal (creator-deals-mcp) → own the audience (newsletter-growth-mcp). Full catalog: MCP Hub
Elisabeth Hitz — 10+ years enterprise sales, reverse-engineered for creators.
License: MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y personal-brand-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-closermethod-personal-brand-mcp": {
"command": "npx",
"args": [
"-y",
"personal-brand-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencepersonal-brand-mcpnpmio.github.closermethod/personal-brand-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.