Log inSubmit server
MCP Bling logo

MCP Bling

by tjclaude88

Gives MCP-compatible agents persistent identities, platform-specific themes, and random character rolls saved to bling.json.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install MCP Bling

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tjclaude88-mcp-bling": {
      "command": "npx",
      "args": [
        "-y",
        "bling-bag"
      ],
      "env": {
        "BLING_PATH": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

tjclaude88/mcp-bling MCP server gives AI agents a configurable identity with personality, appearance, backstory fields, and theme colours. It reads and validates a bling.json file, formats colours for terminal, web, Slack, Discord, and IDE use, and can generate random identities from the WOW or Legends pools. Reach for it when an agent needs a repeatable persona or a new identity that can be reviewed and persisted. The server runs over stdio and can be launched with npx, an installed package, or a local build.

Use cases

  • Configure a persistent agent persona
  • Generate a random office-worker identity
  • Format agent colours for Slack or Discord
  • Save a generated identity to bling.json
  • Create a screenshot-ready rarity card

Key features

  • Persistent identity stored in bling.json
  • WOW and Legends identity pools
  • Platform-specific theme formatting
  • Rarity scoring and share cards
  • Backup before saving a new identity
  • Structured validation errors

Tools5

What MCP Bling lets your agent do. Expand a tool for its parameters.

Verified live~472 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/6 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · bling-bag (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads235Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Bling works

What tjclaude88/mcp-bling does

tjclaude88/mcp-bling MCP server gives an agent a stored identity and tools for presenting that identity across several environments. The identity can include a name, personality, appearance, office details, theme colours, and optional metadata. Required configuration includes a non-empty name, three personality values, and primary and accent colours written as six-digit hexadecimal values.

The server also supports generated identities. The default WOW pool creates quirky office-worker characters, while the Legends pool places historical figures in absurd corporate roles. Generated results include character details, traits, a rarity score, and a formatted share card.

How it works

The server uses stdio transport, so an MCP client starts it as a child process rather than connecting to a network port. Configuration is resolved in this order: the --bling command-line option, the BLING_PATH environment variable, then ./bling.json in the working directory.

get_identity reads the configured file and returns the identity. get_theme_for_platform converts the configured colours into platform-specific output. A terminal request returns ANSI codes, a web request returns CSS variables, and Slack, Discord, and IDE requests receive their supported formatting. Unknown platforms receive the raw hexadecimal colours.

roll_identity creates a session-level result without immediately changing the file. save_last_roll writes that result to bling.json and first backs up an existing file as bling.json.bak. get_rarity_report returns the latest roll's share-card text. Calls that depend on a missing file or previous roll return structured errors.

Setup and configuration

Install Node.js 20 or later, then either install bling-bag with npm or run it on demand through npx -y bling-bag. Add the command and its arguments to an MCP client configuration, using an absolute path in BLING_PATH when the identity file is stored outside the working directory. A local clone can instead run the compiled dist/index.js with Node.

A minimal bling.json needs name, personality.tone, personality.formality, personality.humor, theme.primary_color, and theme.accent_color. Theme values must match #RRGGBB; shorthand colours and values without the leading hash are invalid. Optional sections can describe physical traits, office details, and homunculus metadata.

For repeatable deployments, pin the npm package version instead of using an unversioned latest release.

Tools and capabilities

The five MCP tools are:

  • get_identity: Reads the configured identity.
  • get_theme_for_platform: Produces platform-specific theme output.
  • roll_identity: Generates a WOW or Legends identity and stores it in memory for the session.
  • save_last_roll: Persists the latest generated identity and creates a backup when needed.
  • get_rarity_report: Returns the latest generated share card.

The WOW generator uses weighted trait pools and rarity bands, then assigns a character tier from the resulting score. Both text content and parsed structured content are returned by the tools.

Limitations and notes

A missing or invalid bling.json prevents identity reads and produces a structured validation error. save_last_roll cannot run until roll_identity has been called in the current session. The generated identity is not persistent until explicitly saved.

The inspection scripts mentioned in the project documentation are available from a cloned repository, not from the installed npm package. The server is intended for MCP clients that can launch local stdio processes, including Claude Code, Claude Desktop, Codex, and Cursor.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Bling

tjclaude88/mcp-bling is an MCP server that connects AI agents to a local bling.json identity file and identity-generation tools. Its main tools read identities, format themes for platforms, roll WOW or Legends characters, save the latest roll, and return rarity share cards. It runs locally over stdio for compatible MCP clients.

Install Node.js 20 or later, then run it with `npx -y bling-bag` or install the package with npm. Add that command to your MCP client configuration. For development, clone the repository, install dependencies, build it, and launch `dist/index.js` with Node.

Create a bling.json file containing a name, personality tone, formality, humor, and primary and accent theme colours. The colour values must use six-digit `#RRGGBB` notation. Set `BLING_PATH` to an absolute file path or place the file at `./bling.json` in the server's working directory.

Yes, call `roll_identity` first and then call `save_last_roll`. The save operation writes the latest in-memory roll to bling.json and backs up an existing configuration to bling.json.bak before replacing it. It returns the backup path when a previous file was overwritten.

Yes, Cursor is named in the provided compatibility guidance and can launch the server through its stdio configuration. Use the package command or a local Node command, and set `BLING_PATH` when the identity file is not in the working directory.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

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 PreviewMCP Bling AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tjclaude88-mcp-bling?style=directory)](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>