Overview
What is ColorsMCP?
ColorsMCP is a Model Context Protocol (MCP) server built with .NET 9.0 that provides knowledge about colors. It supports multiple transport modes for integration with MCP clients, including STDIO, HTTP Streamable (Docker), and SSE (Azure Function App).
How to use ColorsMCP?
Install and run the server using the .NET CLI for STDIO, build and run a Docker image for HTTP, or deploy an Azure Function App for SSE. Configure your MCP client (e.g., VS Code) with a mcp.json file pointing to the appropriate server endpoint as shown in the README.
Key features of ColorsMCP
- .NET 9.0 implementation
- Supports STDIO, HTTP, and SSE transports
- Docker image for HTTP Streamable mode
- Azure Functions deployment for SSE
- Optional OAuth authentication/authorization for HTTP
Use cases of ColorsMCP
- Generate a palette of colors from a given family (e.g., blue) and output to an HTML file
- Access color knowledge programmatically via an MCP client
- Deploy as a cloud resource with Azure Functions and secure with keys
FAQ from ColorsMCP
What transport modes are supported?
STDIO, HTTP Streamable (Docker), and SSE (Azure Function App). HTTP can also run with OAuth authentication.
How do I configure VS Code to use ColorsMCP?
Add a server entry to .vscode/mcp.json with the appropriate type (stdio, http, or sse) and the required URL/command.
What are the runtime dependencies?
STDIO mode requires .NET 9.0. HTTP mode requires Docker. SSE mode requires an Azure Functions deployment.
Does ColorsMCP support authentication?
Yes. The HTTP Docker image can be built with OAuth authentication/authorization, and the SSE Azure Function App requires an x-functions-key header.
How can I test the MCP server?
Set the environment variable DANGEROUSLY_OMIT_AUTH=true and run npx @modelcontextprotocol/inspector.
