identitypersonascustomizationdeveloper-tools
MCP server for configuring bot identities, platform styling, and randomized office-worker or historical-figure personas.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Configure a persistent bot name, personality, and visual theme
Generate a random Weird Office Worker identity
Generate a historical figure in an absurd corporate role
Format identity styling for terminal, web, Slack, Discord, or IDE output
Save a generated identity as the active bling.json configuration
Key features
Reads and validates a bling.json identity file
Generates WOW and Legends identities
Provides rarity reports and screenshot-ready share cards
Formats themes for supported platforms
Saves generated identities with a backup of the previous configuration
Uses stdio transport for local MCP clients
Capabilities & Tool Schemas (5)
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Bling.
get_identityReturns the configured bling.json identity
get_theme_for_platformPlatform-formatted styling. Args: `platform` ∈ {`terminal`, `web`, `slack`, `discord`, `ide`}
roll_identityGenerates a random WOW character with rarity scoring
save_last_rollPersists the most-recent roll to bling.json (creates `<path>.bak` first)
get_rarity_reportReturns the share-card text for the most-recent roll
Documentation Overview
Bling Bag
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:
--bling <path>CLI argument (highest priority)BLING_PATHenvironment variable./bling.jsonin 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 stringpersonality.tone,personality.formality,personality.humor— non-empty stringstheme.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} |
roll_identity | mutates in-memory cache | no | Generates a random WOW character with rarity scoring |
save_last_roll | write (disk) | no | Persists the most-recent roll to bling.json (creates <path>.bak first) |
get_rarity_report | read (in-memory) | yes | Returns the share-card text for the most-recent roll |
All tools return both content[].text (JSON-stringified) and structuredContent (the parsed object). Errors come back with isError: true and a { error: string } body.
WOW (Weird Office Workers) — what makes it interesting
The random-roll system is built for collectibility:
- 13 weighted pools, 465 entries — names, job titles, habits, coffee rituals, height, accessories, etc.
- 5 rarity bands per pool — Common (50%), Uncommon (30%), Rare (15%), Legendary (4%), Mythic (1%)
- 5 character tiers computed from rarity score:
- Filing Clerk (50% of rolls)
- Team Lead (30%)
- Middle Manager (14%)
- C-Suite (5%)
- HR Warned Us About (1%)
- Named Subjects — hand-authored 1-of-1 characters appear at ~0.5% probability, always classified as "HR Warned Us About"
- HOMUNCULUS frame — every roll wraps the paragraph in a classified-document share card with subject ID, cohort (weekday), tier, ingestion date, and a flag (e.g. Do Not Contact)
Distribution is empirically tested: a 10k-roll test in tests/mystery_box.test.ts enforces ±2pp tolerance against the spec target.
Example output
Development
Inspection scripts
Two Node ESM helpers under scripts/ let you inspect the WOW engine without booting the MCP server (these are included only in a cloned repo — they are not shipped in the npm install bling-bag package):
Project layout
License
MIT
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
1
Stargazers on the source repository.
npm downloads
223
Package downloads in the last 30 days.
Last commit
1mo ago
Most recent push to the default branch.
Tools exposed
5
Callable tools this server registers over MCP.
Directory activity
1 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about MCP Bling
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/tjclaude88-mcp-bling)HTML Embed
<a href="https://allmcps.com/mcp/tjclaude88-mcp-bling"><img src="https://allmcps.com/api/badge/tjclaude88-mcp-bling?style=directory" alt="MCP Bling on AllMCPs" /></a>