Clicky

MCP server for Clicky Analytics
  • typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "colintoh-clicky-mcp": {
      "command": "node",
      "args": [
        "/path/to/clicky-mcp/dist/index.js"
      ],
      "env": {
        "CLICKY_SITE_ID": "YOUR_SITE_ID",
        "CLICKY_SITE_KEY": "YOUR_SITE_KEY"
      }
    }
  }
}

You can run the Clicky MCP Server to fetch traffic analytics from Clicky and expose tools that let you retrieve total visitors, domain visitors, top pages, traffic sources, and page-specific data through an MCP client.

How to use

To use this MCP server, run it locally or connect to it from an MCP client. The server exposes five tools that you can invoke to fetch analytics data from Clicky for specified date ranges, domains, or pages. Use an MCP client to call the tools by name and supply the required parameters, such as dates, domain filters, or URLs. The server will return structured results you can drill into in your dashboards or conversations.

How to install

# Prerequisites
- Node.js (14+)
- npm (comes with Node.js)

# 1) Install dependencies
npm install

# 2) Build the project
npm run build

# 3) Start the server
npm start

# Development mode
npm run dev

Configuration

You must provide your Clicky credentials to use the server. Choose one of the following methods and replace placeholders with your actual values.

# Option 1: Environment variables
export CLICKY_SITE_ID="YOUR_SITE_ID"
export CLICKY_SITE_KEY="YOUR_SITE_KEY"
# Option 2: Command line arguments
npm start -- --site-id YOUR_SITE_ID --site-key YOUR_SITE_KEY
# Option 3: .env file
# Create .env file in project root
CLICKY_SITE_ID=YOUR_SITE_ID
CLICKY_SITE_KEY=YOUR_SITE_KEY

Security note: Never commit your actual credentials to version control. The .env file should be kept out of source control.

Claude Desktop integration

To use the MCP server with Claude Desktop, add it to your Claude Desktop configuration and provide credentials.

{
  "mcpServers": {
    "clicky-analytics": {
      "command": "node",
      "args": ["/path/to/clicky-mcp/dist/index.js"],
      "env": {
        "CLICKY_SITE_ID": "YOUR_SITE_ID",
        "CLICKY_SITE_KEY": "YOUR_SITE_KEY"
      }
    }
  }
}

Notes and tips

If you plan to run this locally, replace "/path/to/clicky-mcp/" with the actual path to your local project where the MCP server is built. Restart Claude Desktop after updating the config to apply changes.

Troubleshooting

  • If you see authentication errors, double-check that CLICKY_SITE_ID and CLICKY_SITE_KEY are set correctly in the environment or passed via the command line.
  • If the server cannot reach the Clicky API, verify network access and that the credentials have the required permissions.
  • For date range issues, ensure your start and end dates follow the YYYY-MM-DD format and do not exceed the 31-day limit enforced by the API.

Available tools

get_total_visitors

Get total visitor counts for a specified date range.

get_domain_visitors

Get visitor data filtered by referrer domain with optional segmentation.

get_top_pages

Get the most popular pages for a date range.

get_traffic_sources

Get traffic sources breakdown for a date range and optional page URL filter.

get_page_traffic

Get traffic data for a specific page by URL.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational