tjclaude88/mcp-bling

> Give your bot an identity.
Your bot has a name. Now give it a personality, a look, and a backstory.
Roll the wheel and see what you get — or write your own in a bling.json file.
---
What you get
Five MCP tools and two identity pools:
WOW — Weird Office Workers
Roll a random quirky office-worker bot: name, job title, desk setup, habits, coffee ritual, and a screenshot-ready share card. 99/99 tests, full rarity engine, 13 weighted trait pools.
Legends — Historical Figures
Same engine, different universe. Roll a historical figure in an absurd corporate role — Julius Caesar as Hostile Takeover Specialist, Marie Curie as Lab Safety's Most Wanted, Napoleon as Regional Manager (France & Surrounding Areas).
Pass variant: "legends" to roll_identity to use it. Default is "wow".
---
Install
Prerequisites
- Node.js 20 or later
- An MCP-compatible client (Claude Code, Claude Desktop, Codex, Cursor, etc.)
Add the package
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)
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):
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:
Pinning to a version (recommended for production)
To avoid picking up future releases automatically, pin a specific version:
Developer-mode invocation (from a local clone)
If you've cloned the repo and want to run from dist/ directly, use:
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 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
Full example (with all optional sections)
Validation rules
- name — non-empty string
- personality.tone, personality.formality, personality.humor — non-empty strings
- theme.primary_color, theme.accent_color — must match ^#[0-9A-Fa-f]{6}$ (no shorthand #RGB, no missing #)
Validation errors come back as isError: true with a structured { error: "..." } body that names the missing or malformed field — agents can self-correct.
---
Typical agent flows
Flow A — adopt the configured identity
Flow B — generate a fresh random identity
---
Tool reference
| Tool | Read/Write | Idempotent | Description |
|------|------------|------------|-------------|
| get_identity | read (disk) | yes | Returns the configured bling.json identity |
| get_theme_for_platform | read (disk) | yes | Platform-formatted styling. Args: platform ∈ {terminal, web, slack, discord, ide} |