MCP server

Dreeve ships with a Model Context Protocol (MCP) server. It lets the AI client you already use, such as Claude Code, Claude Desktop, Cursor or VS Code, read your activities, metrics and settings and answer questions about them.

Enabling the MCP server

The MCP server is available at /mcp, for example https://dreeve.example.com/mcp. It has its own key:

Generate a key under Settings → Security → MCP access in the admin panel. It looks like drvm_ followed by 64 hex characters.
Set it as DREEVE_MCP_KEY in your .env file and recreate your containers.

While DREEVE_MCP_KEY is not set, the MCP server rejects every request.

Connecting a client

Replace https://dreeve.example.com with the URL of your Dreeve instance and drvm_... with your key.

> claude mcp add --transport http dreeve https://dreeve.example.com/mcp --header "Authorization: Bearer drvm_..."

Add the server to claude_desktop_config.json:

{
    "mcpServers": {
        "dreeve": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://dreeve.example.com/mcp",
                "--header",
                "Authorization:${AUTH_HEADER}"
            ],
            "env": {
                "AUTH_HEADER": "Bearer drvm_..."
            }
        }
    }
}

{
    "mcpServers": {
        "dreeve": {
            "url": "https://dreeve.example.com/mcp",
            "headers": {
                "Authorization": "Bearer drvm_..."
            }
        }
    }
}

{
    "servers": {
        "dreeve": {
            "type": "http",
            "url": "https://dreeve.example.com/mcp",
            "headers": {
                "Authorization": "Bearer drvm_..."
            }
        }
    }
}