Behr Colormapper MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| behr_match_paintB | Convert a digital sRGB color to the nearest Behr paint colors using CIEDE2000 perceptual distance. |
| behr_search_colorsB | Find Behr colors by exact or partial paint code or color name. Exact codes rank first. |
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 2 tools
The two tools have clearly distinct purposes: one converts an sRGB color to nearest Behr matches, the other searches by code/name. No overlap or ambiguity in selection.
Both tools follow a consistent 'behr_' prefix and verb_noun pattern (match_paint, search_colors). Predictable and readable.
Two tools are sufficient for the core mapping and lookup tasks, but the set feels slightly thin for a color service; a third tool (e.g., color detail) would add value without bloat.
The surface covers matching digital colors to Behr and searching by code/name, which are the primary workflows. Minor gaps include no explicit reverse mapping (Behr to sRGB) or dedicated color detail retrieval, though search likely returns enough.