Personal MCP Server

Positioning framework, per-platform bio auditing, 4-pillar content system, growth-signal reads.

Local serverstdio

What is the Personal MCP server?

Most developer tooling work still happens through a UI a human drives. Personal MCP server moves it into the conversation instead. Positioning framework, per-platform bio auditing, 4-pillar content system, growth-signal reads.

The short version

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 tools it exposes

The server publishes 7 tools. What each one is for:

  • 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

Getting it running

Installation goes through your MCP client rather than a global install: point it at personal-brand-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Personal's toolset — get_positioning_framework, audit_bio, get_bio_rules and 4 more — is a fair guide to whether it matches your workflow. It is maintained by closermethod; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Personal's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_positioning_frameworkThe niche statement formula (WHO x OUTCOME x HOW x RECEIPT), 4 checks, proof inventory, moat check
audit_bioPASS/NEEDS WORK per platform: char limits, hype titles, title-first openers, missing outcome
get_bio_rulesBio architecture per platform (tiktok, instagram, linkedin, x, youtube)
get_content_pillarsThe 4-pillar system: receipts ~30%, method ~40%, story ~20%, conversion ~10%
get_platform_strategyEach platform's strategic role, conversion path, cadence floor, watch-out
interpret_growth_signalWhat your growth pattern means (high views/flat followers, high DMs/low sales...) and the fix
get_full_packEverything in one payload

How to install the Personal MCP server

Claude Desktop config:
```json
{ "mcpServers": { "personal-brand": { "command": "npx", "args": ["personal-brand-mcp"] } } }

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Personal to get positioning framework.
  • Use Personal to audit bio.
  • Use Personal to get bio rules.

Frequently asked questions

It connects Personal to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (get_positioning_framework, audit_bio, get_bio_rules, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Personal directly.