austinnchristensen/brandman
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Agent-first brand brain: governed brand context, content workflow and MCP server. AGPL-3.0.
개요
BrandMan is an agent-first brand brain. It keeps a brand's mission, voice, compliance rules, audience personas, content sources, campaigns and results in one governed place, and lets AI agents (through MCP) and people (through a dashboard) work from that same source of truth. Channels are replaceable adapters. X, a newsletter platform or your own site sit at the edge: BrandMan drafts for them, records what happened, and learns from the results. The brand context itself never lives inside a channel. Status: early. The core runs and is tested, but expect rough edges and breaking changes. Nothing is published to a channel automatically; posting is handed off for explicit approval. - mission, voice, guidelines, personas and policy per brand, retrievable by agents and humans. - sources, campaigns, channel drafts, exact-revision approval, and a governed delivery handoff.
README
원문 README의 일부입니다. 원문 보기.
BrandMan
BrandMan is an agent-first brand brain. It keeps a brand’s mission, voice, compliance rules, audience personas, sources, campaigns, and results in one place, and lets AI agents (through MCP) and people (through a dashboard) work from that same record.
This repository is the AGPL-3.0 open core. It is free software and is not paywalled. You can run, modify, and self-host it with no BrandMan Cloud account. If you run a modified version as a network service, the AGPL requires you to offer that source to the people who use the service. The BrandMan name and logo are not covered by the license.
BrandMan Cloud is a separate paid product. It is this core plus closed components (a hosted service, billing, multi-tenancy, and similar). Cloud has more features. The open core is the smaller, functional system: one SQLite database, a password-gated dashboard, and an MCP server you run yourself. Cloud is not in this repository, and you do not need it to use the core.
Status: early (0.1.x). The core runs and is tested. Expect rough edges and breaking changes.
What the open core does
- Brand context. Mission, voice, guidelines, personas, and compliance rules, readable by agents and people.
- Content workflow. Sources, campaigns, channel drafts, and newsletter issues.
- Exact-revision approval. A person approves one revision. The MCP server can draft and submit that revision. It has no tool that approves or publishes. Editing an approved item clears the approval, bumps the revision, and sends it back to draft. Nothing is posted to a channel automatically.
- Feedback. Record what a channel did, propose a learning, and accept it into the brand context only with an explicit decision.
- Missions. Time-boxed goals with a baseline, a target, and a trajectory.
- MCP. The same flows for Claude, Cursor, and Codex, over stdio
(
brandman-mcp) or a hosted OAuth endpoint (/mcp). - Dashboard and REST API. Operator UI at
/app, and the API behind it. - Channels at the edge. X and Beehiiv are replaceable adapters. The brand record does not live inside a channel.
Install
Python 3.11 or newer. Package installers download the latest
brandman release on PyPI. This
repository can be ahead of that release. The wheel includes the dashboard, so
a PyPI install does not need Node.js.
pip install brandman
# or: uv tool install brandman
# or: pipx install brandman
In an empty directory:
brandman init # writes .env (mode 600) and brandman.db, then asks for the brand
brandman serve # http://127.0.0.1:8000/app
Sign in with BRANDMAN_PREVIEW_PASSWORD from .env. Pass --name,
--mission, --voice, --compliance, and -y to skip the prompts.
brandman init sets the brand’s approval policy to human_approval_required.
Connect Claude, Cursor, or Codex
설치
uvx --from brandman brandman-mcp설정
{
"mcpServers": {
"brandman": {
"command": "uvx",
"args": ["--from", "brandman", "brandman-mcp"],
"env": {
"BRANDMAN_DB": "/absolute/path/brandman.db",
"BRANDMAN_DATABASE_PROFILE": "operating"
}
}
}
}