What can you do with this server?

The Bling-bag server lets you give your bot a personality, appearance, and backstory via a custom config or randomly generated identity. * get_identity: Retrieve the bot's full configured identity from bling.json (name, personality, quirks, appearance, theme colors). * get_theme_for_platform: Get styling formatted for a specific platform — terminal (ANSI), web (CSS variables), slack, discord, or ide — based on the bot's theme. * roll_identity: Generate a random "Weird Office Worker" identity with name, job title, desk habits, coffee ritual, rarity score, tier, and a screenshot-ready share card. Supports a legends variant for historical figures in absurd corporate roles. * save_last_roll: Persist the most recently rolled identity to bling.json, automatically backing up any existing config to .bak. * get_rarity_report: Retrieve the formatted plain-text share card for the most recent roll, including the HOMUNCULUS frame with subject ID, cohort, tier, rarity score, and flags.

Which integrations are available for this server?

Generates Discord embed colors and platform-formatted styling for bot identities, enabling consistent visual presentation of AI agents in Discord environments. Generates Slack embed colors and platform-formatted styling for bot identities, enabling consistent visual presentation of AI agents in Slack workspaces.

de en es ja ko ru zh

Bling-bag

by tjclaude88

Overview Schema Related Servers Score Discussions

TypeScript

Local

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.

npm version Glama

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".

Related MCP server: being-mcp-server

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/<github-user>/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:

--bling <path> CLI argument (highest priority)
BLING_PATH environment variable
./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": {
    "species": "human",
    "height": "permanently mid-sigh",
    "accessory": "a lanyard with 14 badges of varying importance",
    "expression": "polite disappointment",
    "material": "a cardigan, at least one"
  },
  "office": {
    "job_title": "ASCII Comptroller",
    "desk_setup": "a coffee mug labelled WORLD'S OKAYEST DBA",
    "habit": "microwaves fish despite three separate HR warnings",
    "coffee_ritual": "black coffee, no nonsense",
    "meeting_energy": "always 4 minutes late, always with a reason",
    "passive_aggressive": "Per my last email"
  },
  "theme": {
    "primary_color": "#9C6B3A",
    "accent_color": "#D9D9D9"
  },
  "homunculus": {
    "subject_id": "0147",
    "cohort": "Tuesday",
    "classification": "Middle Manager",
    "ingested": "2025-07-14",
    "flag": "flagged for review"
  }
}

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

1. Call get_identity → receive name, personality, appearance, theme
2. Call get_theme_for_platform with platform="terminal" (or web/slack/discord/ide)
3. Use the returned styling in agent output (ANSI codes for headings, etc.)

Flow B — generate a fresh random identity

1. Call roll_identity → receive identity + rarity + framed share card
2. (Optional) Call get_rarity_report → receive just the framed share card again
3. Call save_last_roll → persists the rolled identity to bling.json (with .bak backup of any prior config)
4. Future calls to get_identity now return the rolled 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

HOMUNCULUS CORPUS · Subject 4483 · Cohort: Wednesday
Classification: Middle Manager · Rarity 94.5 · 80th percentile

Personnel record — Colin, Wizard of Light Bulb Moments. Distinguishing
features: a slightly-too-big blazer over a plain tee; a flip phone in
a belt holster; expression: patient disagreement. Notable behaviours:
clips their fingernails at the desk on Wednesday afternoons; a
kombucha SCOBY fermenting next to the keyboard; the kind to ask 'can
we park that?' without parking anything.

— RELATABILITY CORPUS v3.1 · ingested 2024-03-08 · flagged for review

Development

npm install          # install dependencies
npm run build        # compile TypeScript → dist/
npm run dev          # build then start the MCP server (stdio)
npm test             # run all 94 tests once
npm run test:watch   # re-run tests on file changes

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):

node scripts/show-rolls.mjs 8 2026          # print 8 framed share cards (seed=2026)
node scripts/distribution-check.mjs 10000   # tally tiers across 10k rolls vs. spec target

Project layout

src/
  index.ts             # MCP server entry point (stdio transport)
  identity.ts          # bling.json loader + validator
  tools.ts             # MCP tool registrations
  types.ts             # shared TypeScript types
  mystery_box.ts       # WOW engine barrel + rollIdentity orchestrator
  mystery_box/
    rng.ts             # seedable PRNG, weighted picker
    pools.ts           # 13 trait pools (465 entries)
    scoring.ts         # rarity score + tier thresholds
    rendering.ts       # paragraph templates + HOMUNCULUS frame
    named.ts           # hand-authored Named Subjects
tests/                 # vitest test suites
scripts/               # dev-time inspection tools
docs/superpowers/      # design specs and implementation plans

License

MIT

Available Tools

5 tools

get_identityGet Bot IdentityA

Read-onlyIdempotent

Get the bot's full identity from bling.json — name, personality, quirks, appearance, and theme colours. Returns the configured identity (hand-written or saved from a roll). Errors if bling.json is missing or invalid.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable context beyond this: it specifies the source file (bling.json), details what data is returned, and mentions error conditions (missing or invalid file), which are not captured in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose in the first sentence, followed by error details. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema) and rich annotations, the description is largely complete. It explains what data is retrieved, the source, and error cases. However, it could slightly enhance completeness by mentioning the return format or example output, though this is not critical due to the straightforward nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4 as there are no parameters to document. The description does not need to compensate for any parameter gaps, and it appropriately focuses on the tool's behavior and output instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the verb 'Get' and the resource 'bot's full identity from bling.json', listing specific attributes like name, personality, quirks, appearance, and theme colours. It clearly distinguishes from siblings like get_rarity_report or get_theme_for_platform by focusing on identity retrieval rather than reports or platform-specific themes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: to retrieve the bot's configured identity, including hand-written or saved roll data. However, it does not explicitly state when not to use it or name alternatives like roll_identity for creating new identities, leaving some room for improvement in sibling differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_rarity_reportGet WOW Rarity ReportA

Read-onlyIdempotent

Return the formatted share card (lore header, paragraph, lore footer) for the most-recent WOW roll. The report is plain text designed to be screenshotted directly. Errors if no roll has happened this session.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`report`	No
`error`	No

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering safety and idempotency. The description adds valuable context beyond annotations: it specifies the output format ('formatted share card', 'plain text'), the error condition ('Errors if no roll has happened'), and the recency constraint ('most-recent'), enhancing behavioral understanding without contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and resource, followed by output details and error conditions in two efficient sentences. Every sentence adds critical information (e.g., format specifics and usage limits) with zero waste, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, annotations cover safety/idempotency, output schema exists), the description is complete. It explains what the tool does, when to use it, output format, and error conditions, leaving no gaps for an AI agent to understand and invoke it correctly without needing additional explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4 as no parameter documentation is needed. The description does not discuss parameters, which is appropriate since there are none, and it focuses on the tool's purpose and constraints instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Return the formatted share card') and resource ('most-recent WOW roll'), distinguishing it from siblings like 'roll_identity' (which creates rolls) and 'save_last_roll' (which saves rolls). It precisely defines the output format ('lore header, paragraph, lore footer', 'plain text designed to be screenshotted directly'), making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool ('for the most-recent WOW roll') and when not to use it ('Errors if no roll has happened this session'), providing clear context and exclusions. This distinguishes it from alternatives like 'roll_identity' for creating rolls or 'get_identity' for retrieving identity data, offering complete guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_theme_for_platformGet Theme for PlatformA

Read-onlyIdempotent

Get platform-specific styling for the bot. Supported platforms: terminal (returns ANSI escape codes), web (CSS variables), slack, discord, ide. Unknown platforms get the raw hex theme colours.

ParametersJSON Schema

Name	Required	Description	Default
`platform`	Yes	Target platform: terminal, web, slack, discord, or ide

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds valuable context beyond this by specifying what is returned for each platform (e.g., ANSI escape codes for terminal, CSS variables for web) and the fallback for unknown platforms (raw hex colours), enhancing behavioral understanding without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, followed by specific details in a single, efficient sentence. Every part of the text adds value, such as listing platforms and fallback behavior, with no redundant or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter) and rich annotations, the description is mostly complete. It explains what the tool does and the platform-specific outputs. However, without an output schema, it could benefit from more detail on the return structure (e.g., format of the theme data), slightly limiting completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, clearly documenting the 'platform' parameter. The description adds some semantic value by listing the specific platform options and explaining the outcome for unknown platforms, but it does not provide additional syntax or format details beyond what the schema already covers, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get platform-specific styling for the bot') and specifies the resource ('theme'), distinguishing it from sibling tools like get_identity or roll_identity. It explicitly lists supported platforms, making the purpose specific and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use this tool by listing supported platforms (terminal, web, slack, discord, ide) and handling for unknown platforms. However, it does not explicitly state when not to use it or name alternatives among sibling tools, which prevents a perfect score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

roll_identityRoll a WOW IdentityA

WOW — Weird Office Workers. Roll a fresh random bot identity: a quirky office-worker character with a rarity score and a screenshot-ready share card. Stores the roll for save_last_roll and get_rarity_report.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`identity`	Yes
`rarity`	Yes
`paragraph`	Yes
`framed`	Yes
`lore`	Yes

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds valuable context beyond annotations by specifying that it 'Stores the roll' (implying state change) and generates a 'random' identity with 'rarity score' and 'share card', which clarifies the mutation and output behavior. It does not contradict annotations, as 'Roll' implies creation (consistent with readOnlyHint=false) and storage aligns with non-idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action ('Roll a fresh random bot identity') and efficiently adds details in a single, well-structured sentence. Every part earns its place by clarifying the character type, output features, and storage implications without unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 0 parameters, rich annotations, and an output schema (which handles return values), the description is complete. It covers the purpose, output characteristics (rarity, share card), and interaction with siblings (storage for save_last_roll and get_rarity_report), providing all necessary context for an agent to use it effectively without over-explaining.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing on the tool's purpose and output. A baseline of 4 is applied since it compensates by explaining the output semantics (rarity score, share card) rather than redundant parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Roll a fresh random bot identity') and resource ('quirky office-worker character'), distinguishing it from siblings like 'get_identity' (which likely retrieves) and 'save_last_roll' (which stores). It explicitly mentions the output includes a 'rarity score' and 'screenshot-ready share card', making the purpose highly specific and differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context by stating it 'Stores the roll for save_last_roll and get_rarity_report', indicating when to use this tool (to generate a new identity) versus alternatives (e.g., use save_last_roll to store it, get_rarity_report for analysis). However, it does not explicitly state when NOT to use it or compare to all siblings like 'get_identity' or 'get_theme_for_platform', missing full alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

save_last_rollSave Last WOW Roll to bling.jsonA

Destructive

Persist the most-recent WOW roll by writing it to the configured bling.json path. If a file already exists at that path it is first copied to .bak so user-tuned configs are recoverable. Returns the backup path (or null if the target was new).

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`ok`	No
`written_to`	No
`backup`	No
`error`	No

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds valuable behavioral context beyond annotations: it explains that existing files are backed up to '<path>.bak' for recovery, which is a critical detail not covered by annotations like destructiveHint. It also clarifies the return value behavior ('Returns the backup path or null'), enhancing transparency about outcomes. No contradictions with annotations are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose in the first sentence, followed by backup behavior and return details. Each sentence adds essential information without redundancy, making it efficient and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (file writing with backup), rich annotations (e.g., destructiveHint), and the presence of an output schema, the description is complete. It covers the operation, backup mechanism, and return value, providing all necessary context for an agent to invoke it correctly without needing to explain return values separately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4 as per rules. The description compensates by explaining the implicit parameter context ('configured bling.json path'), adding meaning about where the file is saved without needing explicit input parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Persist the most-recent WOW roll by writing it to the configured bling.json path'), identifies the resource (WOW roll data), and distinguishes this from sibling tools like get_identity or roll_identity which don't involve file persistence. It uses precise verbs like 'write' and 'copied' to convey the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying 'most-recent WOW roll' and 'configured bling.json path', suggesting it should be used after a roll operation to save results. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions, such as whether it's only for WOW rolls versus other data types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_identity retrieves a saved identity, get_rarity_report provides a formatted report of the latest roll, get_theme_for_platform returns platform-specific styling, roll_identity generates a new random identity, and save_last_roll persists the latest roll. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, such as get_identity, get_rarity_report, get_theme_for_platform, roll_identity, and save_last_roll. This uniformity enhances readability and predictability across the toolset.

Tool Count5/5

With 5 tools, the server is well-scoped for managing bot identities and related operations. Each tool serves a specific role in the identity lifecycle, from creation to retrieval and persistence, without being overly sparse or bloated.

Completeness5/5

The toolset provides complete coverage for the bot identity domain: roll_identity for creation, get_identity and get_rarity_report for retrieval, save_last_roll for persistence, and get_theme_for_platform for styling. There are no obvious gaps, supporting full agent workflows from generation to configuration.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Quallaa
com.quallaa
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
AI & Machine Learning Communication
2
UnifAPI
com.unifapi
Hosted MCP server for live public-data APIs and Skills for AI agents.
Open Data Search AI & Machine Learning
2
Remote Desktop Commander
app.desktopcommander
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Shell Access OS Automation
214
RogerRat A
io.github.opcastil11
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Communication Agent Orchestration
21

Related MCP Servers

consult-mcp
Agent Orchestration Autonomous Agents AI & Machine Learning
oblogin
A
license
A
quality
D
maintenance
MCP server orchestrating local CLI agents (Claude Code, OpenAI Codex, Google Gemini) for cross-validation, second opinions, and persona-driven prompting.
Updated 4 months ago (2026-05-03 17:38 UTC)
18
MIT
being-mcp-server
Knowledge & Memory Autonomous Agents
wnbhr
F
license
A
quality
F
maintenance
MCP server for Being — a Personality Runtime that gives AI agents persistent memory, personality, and relationships. Enables any MCP-compatible client (Claude, OpenClaw, Cursor, etc.) to connect with a Being that remembers, grows, and maintains its own identity across sessions.
Updated 3 months ago (2026-05-28 08:58 UTC)
10
1
PLTM-Claude
Knowledge & Memory AI & Machine Learning Search
Alby2007
A
license
Not graded
quality
F
maintenance
An MCP server that gives Claude Desktop persistent memory, self-awareness, epistemic hygiene, and genuine agency across conversations with a typed memory system, embedding-based semantic search, a 3-judge memory jury, and a real-time dashboard.
Updated 7 months ago (2026-02-14 20:45 UTC)
7
MIT
Vibecoders MCP
RaedBerjaoui
A
license
A
quality
B
maintenance
One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
Updated a month ago (2026-07-25 21:37 UTC)
23
3
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tjclaude88/mcp-bling'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Bling Bag

What you get

WOW — Weird Office Workers

Legends — Historical Figures

Install

Prerequisites

Add the package

For development (modifying the source)

Wire it into your MCP client

Claude Code

Claude Desktop

Pinning to a version (recommended for production)

Developer-mode invocation (from a local clone)

Config resolution order

bling.json — the bot's identity file

Minimum example

Full example (with all optional sections)

Validation rules

Typical agent flows

Flow A — adopt the configured identity

Flow B — generate a fresh random identity

Tool reference

WOW (Weird Office Workers) — what makes it interesting

Example output

Development

Inspection scripts

Project layout

License

Available Tools

Output Schema

Output Schema

Output Schema

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

`bling.json` — the bot's identity file