ccu-mcp

What this does

ccu-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

CCU_HOST
CCU_PASSWORD
CCU_USER
CCU_HTTPS
CCU_PORT
CACHE_DIR
MCP_ALLOWED_ORIGINS
MCP_ALLOWED_HOSTS
CCU_PROFILES
CCU_DEFAULT_PROFILE
CCU_TLS_VERIFY
CCU_TLS_FINGERPRINT
CCU_CA_CERT
CCU_TIMEOUT
CCU_SCRIPT_TIMEOUT
CACHE_TTL
CCU_RATE_LIMIT_BURST
CCU_RATE_LIMIT_RATE
RESOURCE_POLL_INTERVAL
LOG_LEVEL

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install ccu-mcp?

Run the Claude Code command in the install section to add ccu-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with ccu-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to ccu-mcp as well.

Does ccu-mcp need an API key?

Yes. Before it can run, set these environment variables: CCU_HOST, CCU_PASSWORD, CCU_USER, CCU_HTTPS, CCU_PORT, CACHE_DIR, MCP_ALLOWED_ORIGINS, MCP_ALLOWED_HOSTS, CCU_PROFILES, CCU_DEFAULT_PROFILE, CCU_TLS_VERIFY, CCU_TLS_FINGERPRINT, CCU_CA_CERT, CCU_TIMEOUT, CCU_SCRIPT_TIMEOUT, CACHE_TTL, CCU_RATE_LIMIT_BURST, CCU_RATE_LIMIT_RATE, RESOURCE_POLL_INTERVAL, LOG_LEVEL. They go in the env block of your MCP config.