
A lightweight wrapper around thecolorapi.com that lets Claude work with color data without needing authentication. You can query color schemes, conversions, and palettes through a streamable HTTP endpoint hosted on the Pipeworx gateway. The setup is straightforward: drop a URL into your MCP config and you're done. Instead of calling specific tools, you can use ask_pipeworx to request color information in plain English and let the gateway route it automatically. Handy when you're building design tools, need programmatic access to color theory, or want to generate palettes on the fly without managing API keys or rate limits.
Color API MCP — wraps thecolorapi.com (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
identify_color | Identify a color by hex code (e.g., "#FF5733"). Returns color name, RGB/HSL/HSV/CMYK values, and WCAG contrast ratios for accessibility. |
generate_scheme | Generate harmonious color palettes from a seed hex color (e.g., "#3498DB"). Returns complementary, analogous, triadic, or monochromatic schemes with hex codes. |
convert_color | Convert between color formats: RGB to hex, HSL, HSV, CMYK. Returns the closest named color for the input values. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"colorapi": {
"url": "https://gateway.pipeworx.io/colorapi/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/colorapi/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Colorapi data" })
The gateway picks the right tool and fills the arguments automatically.
MIT