bmobot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BMOBOT_API_BASE | No | Custom API base URL. The {service} placeholder is replaced with the service name (e.g., hash, json, cron). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hashC | Hash text using MD5, SHA-1, SHA-256, SHA-512, or other algorithms |
| hmacB | Generate HMAC signature for text with a secret key |
| encodeB | Encode/decode text: base64, URL, hex, HTML entity encoding |
| convert_caseB | Convert text between camelCase, snake_case, kebab-case, PascalCase, CONSTANT_CASE, Title Case, and more |
| slugifyB | Convert text to a URL-safe slug |
| count_wordsB | Count words, characters, sentences, and estimate reading time |
| extract_from_textA | Extract emails, URLs, numbers, hashtags, mentions, or phone numbers from text |
| format_jsonA | Format, validate, and pretty-print JSON |
| json_diffA | Compare two JSON objects and show differences |
| json_queryA | Query JSON with dot-notation path (e.g. 'users.0.name') |
| test_regexB | Test a regular expression against text and see matches |
| explain_regexB | Explain a regular expression in plain English |
| format_sqlC | Format and pretty-print SQL queries |
| analyze_sqlB | Extract tables, columns, JOINs, and structure from a SQL query |
| parse_cronA | Parse a cron expression into human-readable description and compute next run times |
| decode_jwtA | Decode a JWT token to see its header, payload, and expiration |
| parse_semverA | Parse, compare, or check if a version satisfies a range (npm-style ^, ~, >=, etc.) |
| http_statusA | Look up HTTP status code meaning, category, and usage guidance |
| diff_textA | Compare two texts and show a unified diff |
| csv_to_jsonA | Convert CSV data to JSON array |
| yaml_to_jsonB | Convert YAML to JSON |
| json_to_yamlA | Convert JSON to YAML |
| generate_uuidC | Generate UUID (v4 or v7) or ULID identifiers |
| generate_passwordB | Generate secure random passwords or passphrases |
| generate_loremC | Generate lorem ipsum placeholder text |
| generate_fake_dataC | Generate realistic fake data for testing — people, addresses, companies, etc. |
| generate_qrB | Generate a QR code from text or URL (returns base64 PNG or SVG) |
| validate_emailA | Validate an email address — syntax, MX records, disposable detection, typo suggestions |
| color_paletteA | Generate color palettes — complementary, analogous, triadic, split-complementary, and more |
| check_contrastA | Check WCAG color contrast ratio between foreground and background colors |
| test_globA | Test if a file path matches a glob pattern (supports *, **, ?, character classes, brace expansion) |
| datetime_nowC | Get current time in any timezone with various format options |
| datetime_diffB | Calculate the difference between two dates/times |
| validate_ipA | Validate an IP address and identify version (IPv4/IPv6), type, and range |
| calculate_cidrA | Calculate network details from CIDR notation — range, broadcast, host count |
| markdown_to_htmlB | Convert Markdown to HTML |
| extract_markdown_tocB | Extract table of contents from a Markdown document |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
Each tool has a clearly distinct purpose, even among related utilities like regex explain vs test or hash vs hmac. The descriptions sufficiently differentiate similar-sounding tools.
Tool names mix verb-first (explain_regex, generate_uuid), noun-first (json_diff, http_status), and single nouns/verbs (hash, encode, hmac), breaking a consistent pattern. However, all use snake_case and are descriptive, so they remain readable.
With 37 tools, this exceeds the 25+ threshold for 'too many' per the rubric. While each tool has a distinct function, the sheer number may overwhelm agents and increase selection difficulty.
The server covers a wide range of developer utilities—text, regex, data formats, datetime, validation, generation, and Markdown. Minor gaps exist (e.g., no XML handling or URL encoding-specific tool), but core utility coverage is strong.