# Creator Brief MCP

**Give Claude the tools a creator-partnerships manager uses every day.**

An [MCP](https://modelcontextprotocol.io) server that plugs into Claude Desktop, Claude Code or any MCP client. Once connected, you can ask Claude things like:

> *"Plan a €15k Instagram campaign with 12 micro creators in Germany. What reach and cost per conversion should we expect? Then write the creator brief and check this caption is compliant."*

and Claude calls these tools to answer with real calculations instead of guesses.

| Tool | What it does |
|---|---|
| `campaign_math` | Reach, engagements, clicks, conversions, cost per 1,000 reached, cost per engagement and per conversion for a planned budget |
| `engagement_check` | Puts a creator in a follower tier and says if their engagement is healthy, weak or suspiciously high (a sign of engagement pods) |
| `check_disclosure` | Checks a sponsored caption against the paid-partnership label each market expects: **DE, AT, FR, UK, US**. Flags labels hidden behind "more" and suggests a fixed caption |
| `draft_brief` | Writes a one-page creator brief with key messages, do's and don'ts, approval flow and the right disclosure label for the market |

## Why disclosure checks matter in Europe

Labelling rules differ by country, and the details catch brands out. In Germany, media authorities expect **"Werbung"** or **"Anzeige"**, so an English `#ad` alone isn't considered enough. France's 2023 influencer law requires **"Publicité"** or **"Collaboration commerciale"**. The UK wants **"Ad"** upfront. `check_disclosure` encodes these so a whole campaign's captions can be checked in seconds.

```json
check_disclosure(caption="#ad obsessed with this serum", country="DE")
{
  "compliant": false,
  "issues": [
    "No accepted label found. Use one of: werbung, anzeige.",
    "English labels alone are not enough here."
  ],
  "suggested_caption": "Werbung | #ad obsessed with this serum"
}
```

*A summary of public regulator guidance, not legal advice. Sources are returned with every check.*

## Install

```bash
git clone https://github.com/Vishwajeetkumbhar379/creator-brief-mcp
cd creator-brief-mcp
pip install -e ".[dev]"
pytest
```

### Connect to Claude Desktop

Add this to `claude_desktop_config.json` (Settings → Developer → Edit config), then restart Claude:

```json
{
  "mcpServers": {
    "creator-brief": {
      "command": "python",
      "args": ["-m", "creator_brief_mcp"],
      "cwd": "/path/to/creator-brief-mcp"
    }
  }
}
```

### Connect to Claude Code

```bash
claude mcp add creator-brief -- python -m creator_brief_mcp
```

## Design

- **`rules.py`** holds all the business logic as plain functions with no I/O, so it's fully unit-tested (15 tests).
- **`server.py`** is a thin MCP layer built on the official Python SDK (v2). Each tool has typed inputs, so the model gets a precise schema.
- Tested end to end with a real MCP client over stdio.

---

Built by [Vishwajeet Kumbhar](https://www.linkedin.com/in/vishwajeetkumbhar379) with Claude Code. MIT licence.