Personal Brand Mcp

io.github.closermethodPublished by GitHub account closermethodv1.0.1Updated Oct 24, 2026

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

Overview

AI-generated overview

Local MCP server that gives an assistant creator-branding frameworks: niche positioning, per-platform bio audits, content pillars and growth-signal reads.

What you can do
  • Retrieve a positioning framework with a niche statement formula, checks and proof inventory
  • Audit a bio per platform and get bio rules for TikTok, Instagram, LinkedIn, X and YouTube
  • Get a four-pillar content system with suggested share of receipts, method, story and conversion
  • Get platform strategy notes on role, conversion path, cadence and watch-outs
  • Interpret growth signals and fetch the whole pack in one payload
When to use it
Useful when a creator or personal-brand client wants structured help with positioning, bio copy, what to post, or which platform to prioritize, and prefers documented frameworks over generic advice.
Requirements
Runs as a local stdio process, typically launched with npx personal-brand-mcp or built from source with Node.js and npm. No accounts, API keys or environment variables are declared.
Before you install
The tools return static frameworks and audits rather than live platform data, so growth and bio checks are advisory; the README notes results vary with consistency, proof quality and niche. No credentials or write actions are declared.

Installation

In SourceWeft

  1. Open Personal Brand Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Personal Brand MCP

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.

Why This Exists

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.

7 Tools

ToolWhat it returns
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

Install

bash
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:

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

The Family

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

Built By

Elisabeth Hitz — 10+ years enterprise sales, reverse-engineered for creators.

License: MIT

Source: README.md at commit e4cd11b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.