Claude Desktop

Add the Clics local MCP server to Claude Desktop for privacy-friendly analytics queries from chat.

Run Clics as a local MCP server in Claude Desktop. Your API key stays on your machine; Claude talks to Clics through a local process.

When to use this

Choose Claude Desktop over Claude web when you want a native app, offline-capable chat UI, or local stdio MCP instead of a remote HTTP connector.

Prerequisites

Node.js 18 or newer
Claude Desktop installed
A Clics API key from Settings → API keys

Config file

claude_desktop_config.json location:

OS	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`
Linux	`~/.config/Claude/claude_desktop_config.json`

In the app: Settings → Developer → Edit Config.

Configuration

{
  "mcpServers": {
    "clics": {
      "command": "npx",
      "args": ["-y", "@clicsdev/mcp"],
      "env": {
        "CLICS_API_KEY": "your_api_key"
      }
    }
  }
}

Enable the server

Save the config file
Fully quit Claude Desktop (menu → Quit, not just close the window)
Reopen Claude Desktop
Look for the hammer/tools icon indicating MCP tools are available

Example prompts

“What are my top referrers this week?”
“List goals and funnels for my SaaS project”
“Create a page goal for /dashboard”

Tips

Quit and reopen is required after every config change
Test the server manually: CLICS_API_KEY=your_key npx -y @clicsdev/mcp
Use a dedicated API key for your personal machine

Troubleshooting

Problem	Fix
No tools icon	Confirm JSON is valid and Claude was fully restarted
Server crash on start	Check Node.js version; run `npx -y @clicsdev/mcp` in Terminal
Permission errors	Ensure `npx` is available in the PATH Claude inherits (launch from Terminal on macOS if needed)

For terminal-based Claude workflows, see Claude Code.

Add the Clics MCP server to Claude Desktop

Claude Desktop