An MCP server that stores and serves a bot's configured identity and visual theme from a local bling.json file. It can also generate a random 'Weird Office Worker' identity, score its rarity, and save that roll as the bot's new identity.
From the registry: Give your bot an identity!
Please install the `bling-bag` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js 20 or later** — Node.js 20+ is required to run the MCP server via npx or a local install.
- **Have an MCP-compatible client** — Use an MCP client such as Claude Code, Claude Desktop, Codex, Cursor, or another compatible client.
- **Create a bling.json identity file** — Create a bling.json file containing the bot identity. The server requires name, personality.tone, personality.formality, personality.humor, theme.primary_color, and theme.accent_color. Point the server to this file with BLING_PATH or place it as ./bling.json in the server working directory.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","bling-bag"]
- optional environment variables:
- `BLING_PATH`: Absolute path to the bling.json identity file. If omitted, the server looks for ./bling.json in its working directory. CLI argument --bling <path> can also override this. (example: `<absolute-path-to-your-bling.json>`)
Note: Preferred install path is npx. The server uses stdio transport. For production, you can pin a version by changing args to ["-y", "bling-bag@<version>"]. The config path resolution order is: --bling <path>, then BLING_PATH, then ./bling.json in the working directory.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.BLING_PATHrequiredPath to the bot identity file bling.json used by the server.AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.