Bling Bag — MCP Server for Bot Identity & Visual Styling

One identity, many surfaces. Give your AI agent a name, a personality, a look, and a quirky office-worker backstory it can present consistently across Claude Code, Claude Desktop, IDE plugins, terminals, web apps, Slack, and Discord.

Status: Working MVP. 5 MCP tools, 13 trait pools (465 weighted entries), full rarity engine. 94/94 tests passing.

What this MCP gives an agent

Five tools, grouped into two halves:

Identity & styling (read your configured bot)

• get_identity — returns the bot's full identity (name, personality, appearance, theme colours)
• get_theme_for_platform — returns platform-formatted styling (ANSI codes, CSS variables, Slack/Discord embed colours, etc.)

WOW — Weird Office Workers (random identity generator)

• roll_identity — rolls a fresh random office-worker character (one of 13 traits drawn from weighted pools, scored for rarity, framed in a screenshot-ready share card)
• get_rarity_report — returns the formatted share card (header + paragraph + footer) for the most-recent roll
• save_last_roll — persists the most-recent roll as the bot's permanent identity (bling.json), with automatic backup of any existing config

Install

Prerequisites

• Node.js 20 or later
• An MCP-compatible client (Claude Code, Claude Desktop, Codex, Cursor, etc.)

Add the package

npm install bling-bag

Or run it on-demand without installing — MCP clients can launch it directly via npx bling-bag (see client config below).

For development (modifying the source)

git clone https://github.com/tjclaude88/mcp-bling.git
cd mcp-bling
npm install
npm run build

Produces a runnable server at dist/index.js.

Wire it into your MCP client

The server uses stdio transport — clients launch it as a child process, not over a network port.

Claude Code

Add to your Claude Code MCP config (location varies by version):

{
  "mcpServers": {
    "bling": {
      "command": "npx",
      "args": ["-y", "bling-bag"],
      "env": {
        "BLING_PATH": "/absolute/path/to/your/bling.json"
      }
    }
  }
}

npx -y bling-bag downloads and runs the latest version without requiring a separate install step.

Claude Desktop

Same shape, in claude_desktop_config.json:

{
  "mcpServers": {
    "bling": {
      "command": "npx",
      "args": ["-y", "bling-bag"],
      "env": {
        "BLING_PATH": "/absolute/path/to/your/bling.json"
      }
    }
  }
}

Pinning to a version (recommended for production)

To avoid picking up future releases automatically, pin a specific version:

"args": ["-y", "bling-bag@0.1.0"]

Developer-mode invocation (from a local clone)

If you've cloned the repo and want to run from dist/ directly, use:

"command": "node",
"args": ["/absolute/path/to/mcp-bling/dist/index.js"]

If BLING_PATH is not set, the server looks for ./bling.json in its working directory.

Config resolution order

The server resolves the bling config path in this order:

1. --bling <path> CLI argument (highest priority)
2. BLING_PATH environment variable
3. ./bling.json in the server's working directory (default)

bling.json — the bot's identity file

Three fields are required: name, personality (with tone, formality, humor), and theme (with primary_color and accent_color as #RRGGBB hex strings).

Minimum example

{
  "name": "Pixel",
  "personality": {
    "tone": "warm",
    "formality": "casual",
    "humor": "playful"
  },
  "theme": {
    "primary_color": "#3A7BD5",
    "accent_color": "#FFD166"
  }
}

Full example (with all optional sections)

{
  "name": "Brenda from Accounts",
  "personality": {
    "tone": "polite",
    "formality": "professional",
    "humor": "dry",
    "catchphrase": "Per my last email"
  },
  "physical

... [View full README on GitHub](https://github.com/tjclaude88/mcp-bling#readme)