BrandVoice MCP - Live Brand Tone and Style Guide Context Server for Claude and Cursor

Every time a marketer asks Claude to write something, they paste their brand guide into the chat like it is 2023. BrandVoice is an MCP server that injects your full tone of voice guide, persona rules, and approved phrasing into Claude as live structured context so every output sounds like your brand without the paste-and-pray ritual.

𝕏 Post Reddit HN

Difficulty

intermediate

What is it?

Marketing teams and solo brand builders spend the first 30% of every Claude session re-establishing brand context — pasting tone guides, persona docs, and do-not-say lists. It is manual, lossy, and breaks every time context windows shift mid-conversation. BrandVoice is a Model Context Protocol server that reads your brand guide from Notion or a structured JSON config, exposes it as typed resources and prompt templates to Claude Desktop and Cursor, and injects fresh brand context into every new conversation automatically. The MCP server exposes tools like get_brand_voice, get_persona, and check_phrase_compliance so Claude can self-correct outputs against your standards. Why buildable now: the MCP SDK is stable as of early 2026, Notion API is production-ready, and the April 2026 vibe-coding wave has surfaced dozens of frustrated brand managers on X complaining that Claude keeps ignoring their tone.

Why now?

The MCP SDK reached stable 1.0 in early 2026 and Claude Desktop user base crossed 1M active users, creating the first real distribution channel for MCP servers targeting non-developer audiences like marketers.

▸MCP resource exposing full brand tone guide as structured JSON to Claude Desktop and Cursor
▸Notion API sync that refreshes brand context from a linked Notion doc on every session start
▸get_brand_voice and check_phrase_compliance MCP tools Claude calls mid-generation to self-correct
▸Web UI config builder for teams without Notion to define brand rules via form

Target Audience

Solo brand managers, marketing leads at 5-50 person startups, and freelance brand strategists — estimated 200,000 active Claude Desktop users with brand writing use cases.

Example Use Case

Sofia runs brand content for a DTC skincare startup. She sets up BrandVoice once with her Notion brand guide, and every Claude session automatically knows they write in second-person warm tone, never say synergy, and always reference their hero ingredient by its trademarked name.

User Stories

▸As a brand strategist, I want Claude to automatically know my tone rules, so that I never paste my brand guide again.
▸As a marketing lead, I want my Notion brand doc synced to Claude, so that every team member gets consistent outputs.
▸As a solo founder, I want Claude to flag off-brand phrases mid-generation, so that I catch errors before publishing.

Done When

✓MCP Resource: done when Claude Desktop lists brand voice resource in context panel without errors
✓Notion Sync: done when brand guide updates in Notion reflect in Claude within 5 minutes
✓Tool Call: done when Claude correctly calls check_phrase_compliance and returns a flag for a banned phrase
✓Stripe Billing: done when Pro upgrade unlocks unlimited brands immediately after payment.

Is it worth building?

$15/month × 200 users = $3,000 MRR at month 3. Realistic at 2% conversion from Claude Desktop community and Twitter/X brand marketing audience with consistent content.

Unit Economics

CAC: $8 via LinkedIn and X outreach (1h founder time). LTV: $300 (20 months at $15/month). Payback: under 1 month. Gross margin: 93%.

Business Model

SaaS subscription

Monetization Path

Free tier: 1 brand, 3 personas. Pro $15/month: unlimited brands, Notion sync, phrase compliance checker.

Revenue Timeline

First dollar: week 3. $1k MRR: month 2. $5k MRR: month 7. $10k MRR: month 15.

Estimated Monthly Cost

Supabase: $25, Vercel: $20, Notion API: free, Resend: $10. Total: ~$55/month at launch.

Profit Potential

Lifestyle business viable at $3k-$8k MRR. Natural upsell to agency plans at $99/month.

Scalability

Add multi-brand agency support, Figma design token sync, and brand compliance scoring on generated copy.

Success Metrics

Week 2: 30 MCP installs. Month 1: 20 paying users. Month 3: 75% retention among Pro users.

Launch & Validation Plan

Post demo video on X showing Claude auto-correcting off-brand copy, collect 50 follows before charging, DM 20 solo brand strategists on LinkedIn.

Customer Acquisition Strategy

First customer: DM 25 freelance brand strategists on LinkedIn offering free Pro setup in exchange for a feedback call and testimonial. Ongoing: X/Twitter MCP community, r/ClaudeAI, Claude Desktop user communities, ProductHunt MCP collection.

What's the competition?

Competition Level

Low

What's the roadmap?

Feature Roadmap

V1 (launch): brand resource, Notion sync, get_brand_voice tool, web config UI. V2 (month 2-3): phrase compliance tool, multi-brand support, Cursor integration. V3 (month 4+): agency team seats, brand audit scoring, Figma token sync.

Milestone Plan

Phase 1 (Week 1-2): MCP server installs and returns brand resource in Claude Desktop, 5 beta users testing. Phase 2 (Week 3-4): Notion sync, check_phrase tool, Stripe live, first paying user. Phase 3 (Month 2): 25 paid users, Cursor compatibility confirmed.

How do you build it?

Tech Stack

MCP SDK (TypeScript), Notion API, Zod for schema validation, Supabase for brand config storage — build with Cursor for MCP server logic, v0 for web config UI.

Suggested Frameworks

MCP SDK TypeScript, Notion API Client, Zod

Time to Ship

2 weeks

Required Skills

MCP SDK TypeScript, Notion API, Zod schema design, basic Supabase.

Resources

Anthropic MCP SDK docs, Notion API docs, MCP server examples on GitHub, Zod docs.

MVP Scope

mcp-server/index.ts (MCP server entry), resources/brand-voice.ts, tools/get-brand-voice.ts, tools/check-phrase.ts, notion-sync/sync.ts, supabase schema for brands/personas/phrases, web config UI (Next.js), README with Claude Desktop install instructions.

Core User Journey

Install MCP server -> connect Notion brand guide -> open Claude Desktop -> first on-brand output in under 5 minutes -> upgrade to Pro.

Architecture Pattern

User connects Notion via OAuth -> brand guide synced to Supabase -> MCP server reads Supabase on session start -> exposes brand resources and tools to Claude Desktop -> Claude calls get_brand_voice tool mid-generation -> server returns structured tone rules -> Claude self-corrects output.

Data Model

User has many Brands. Brand has one ToneGuide. Brand has many Personas. Brand has many ApprovedPhrases. Brand has many BannedPhrases. ToneGuide syncs from one NotionPage.

Integration Points

MCP SDK for Claude Desktop and Cursor tool exposure, Notion API for brand guide sync, Supabase for brand config storage, Stripe for Pro billing, Vercel for web config UI.

V1 Scope Boundaries

V1 excludes: team collaboration on brand guide, multi-model support beyond Claude, Figma integration, brand compliance scoring, white-label.

Success Definition

A brand manager installs BrandVoice via README, connects their Notion doc, opens Claude Desktop, and receives on-brand copy in their first session without any founder help.

Challenges

The hardest non-technical problem is discovery — MCP servers have no App Store yet, and most brand managers do not know what MCP is. Distribution requires educating the audience, not just building.

Avoid These Pitfalls

Do not build a full brand audit feature before validating that MCP injection alone solves the core pain. Do not assume Claude Desktop users will find the product organically — active X community posting is required. MCP server installs have friction — README must be under 5 steps or users quit.

Security Requirements

Supabase Auth with Google OAuth, RLS on all brand and user tables, Notion OAuth tokens encrypted at rest, rate limit 120 req/min per user, GDPR: brand data deletion endpoint required.

Infrastructure Plan

Vercel for Next.js config UI, Supabase for brand config storage, GitHub Actions for CI, Sentry for errors, dev/staging/prod on Vercel. Total: ~$55/month.

Performance Targets

500 DAU at launch, 2,000 MCP tool calls/day. MCP resource response under 200ms. Web UI under 2s LCP. Supabase read caching for brand config to minimize DB hits.

Go-Live Checklist

☐Security audit complete
☐Payment flow tested end-to-end
☐Sentry live
☐Monitoring configured
☐Custom domain set up
☐Privacy policy and terms published
☐5 beta brand managers signed off
☐Rollback plan documented
☐X and ProductHunt launch posts drafted.

First Run Experience

How to build it, step by step

1. Clone Anthropic MCP server TypeScript starter template from GitHub. 2. Install notion-client, zod, supabase-js dependencies. 3. Define Zod schemas for BrandVoice, Persona, and Phrase types. 4. Build resources/brand-voice.ts that reads brand config from Supabase and returns as MCP resource. 5. Build tools/get-brand-voice.ts and tools/check-phrase.ts as MCP tool handlers. 6. Build notion-sync/sync.ts that fetches Notion page blocks and maps to BrandVoice schema. 7. Run npx create-next-app brandvoice-config and build Supabase-connected brand config form UI. 8. Add Notion OAuth flow to web UI for connecting brand guide docs. 9. Add Stripe billing for Pro plan with Supabase feature flags. 10. Write README with exact Claude Desktop mcpServers config JSON and deploy web UI to Vercel.

Generated

April 17, 2026

Model

claude-sonnet-4-6

← Previous

SupplyNest - Bill of Materials Cost Tracker for Makers and Small Manufacturers

ClipVault - Short-Form Video Asset Library and Clip Tagging System for Solo Content Creators

Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.