austinnchristensen/brandman

开发工具

本页由 AI 翻译，技术细节请以原文为准。查看原文

0 stars 0 forks 质量 79 趋势 20AGPL-3.0

Repository Install

以代理为先的品牌大脑：受品牌语境、内容工作流程和MCP服务器管理。AGPL-3.0。

概览

BrandMan是一个以代理为先的品牌大脑。它将品牌的使命、声音、合规规则、受众形象、内容来源、活动和成果集中在一个受控的地方，让AI代理（通过MCP）和人员（通过仪表盘）从同一真实来源工作。频道是可替代的适配器。X、新闻通讯平台或你自己的网站处于边缘：BrandMan为它们起草、记录发生了什么，并从结果中学习。品牌语境本身从不存在于频道内部。状态：早期。核心运行并测试，但会遇到粗糙和破坏性变更。不会自动发布到频道;发布过程需明确审核。 - 每个品牌的使命、声音、指南、人物和政策，可由代理和人工检索。- 来源、活动、渠道草稿、精确修订批准及受控交付切换。

概述（AI 翻译）

BrandMan是一个以代理为先的品牌大脑。它保持品牌的使命和声音，合规规则、受众画像、来源、活动和结果合一并让AI代理（通过MCP）和人员（通过仪表盘）工作出自同一张唱片。

本仓库为AGPL-3.0开核。 它是自由软件，但不是付费墙。你可以运行、修改和自托管，无需BrandMan云账户。如果你运行修改过的版本作为网络服务，AGPL要求你将该资源提供给使用该服务的人。BrandMan 这个名字以及标志不受许可保护。

BrandMan云是一个独立的付费产品。确实如此该核心加上封闭组件（托管服务、计费、多租户和类似）。云端功能更多。开放核心较小，功能更实用 system：一个SQLite数据库，一个密码门控仪表盘，以及一个MCP服务器，你自己运行。这个仓库里没有云，你也不需要它来使用。核心。

状态：早期（0.1.x）。核心运行并测试中。预计会出现粗糙的边缘和破坏性变更。

开放核心的作用

品牌背景。 使命、声音、指南、人物形象和合规规则，

本页由 AI 翻译，技术细节请以原文为准。

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.

Quick links: Quickstart · Architecture · Docs · Contributing · Security · BrandMan Cloud · PyPI

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. An approval covers one exact revision. Editing an approved item clears the approval, bumps the revision, and sends it back to draft. Nothing is posted until its current revision is approved. Human review of each post is optional: you choose who approves (a person in the dashboard, or your own automation through the REST API), and the brand’s approval policy is a setting. The MCP server can draft and submit for approval; it has no tool that approves or publishes.
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.

Architecture

Claude / Cursor / Codex ──MCP──┐
browser ──► dashboard (/app) ──┤
scripts ──► REST API (/api) ───┴─► FastAPI app (brandman.main)
                                    ├─ brand context, campaigns, newsletters

在 GitHub 查看完整 README

安装

uvx --from brandman brandman-mcp

新手？先看 mcpskill.org 教程 →

配置

{
  "mcpServers": {
    "brandman": {
      "command": "uvx",
      "args": ["--from", "brandman", "brandman-mcp"],
      "env": {
        "BRANDMAN_DB": "/absolute/path/brandman.db",
        "BRANDMAN_DATABASE_PROFILE": "operating"
      }
    }
  }
}