Initial server

Author: ar2rsawseen

.dockerignore

@@ -0,0 +1,58 @@
+# Node modules
+node_modules
+npm-debug.log
+yarn-error.log
+
+# Build output (will be built inside Docker)
+build
+
+# Environment files
+.env
+.env.local
+.env.*.local
+
+# Token files (secrets should not be in image)
+*.token
+*_token.txt
+countly_token.txt
+
+# Git
+.git
+.gitignore
+.gitattributes
+
+# IDE
+.vscode
+.idea
+*.swp
+*.swo
+*~
+.DS_Store
+
+# Testing
+coverage
+.nyc_output
+test-results
+
+# Documentation
+*.md
+!README.md
+docs
+
+# CI/CD
+.github
+.gitlab-ci.yml
+.travis.yml
+azure-pipelines.yml
+
+# Docker
+.dockerignore
+docker-compose.yml
+docker-compose.*.yml
+Dockerfile.dev
+
+# Misc
+*.log
+.cache
+tmp
+temp

.env.example

@@ -0,0 +1,113 @@
+# Countly MCP Server - Environment Configuration
+# Copy this file to .env and configure your settings
+
+# ==============================================================================
+# REQUIRED CONFIGURATION
+# ==============================================================================
+
+# Countly Server URL
+# The base URL of your Countly server instance
+# Example: https://your-countly-instance.com or https://api.count.ly
+COUNTLY_SERVER_URL=https://api.count.ly
+
+
+# ==============================================================================
+# AUTHENTICATION (Choose ONE of the following methods)
+# ==============================================================================
+
+# Method 1: Direct Auth Token (recommended for development)
+# Provide the authentication token directly as an environment variable
+# COUNTLY_AUTH_TOKEN=your-auth-token-here
+
+# Method 2: Auth Token File (recommended for production/Docker)
+# Provide a path to a file containing the authentication token
+# Useful for Docker secrets, Kubernetes secrets, or secure file storage
+# COUNTLY_AUTH_TOKEN_FILE=/run/secrets/countly_token
+
+# Note: If neither is set, the token must be provided by the MCP client
+# via metadata.countlyAuthToken or as a tool argument
+
+
+# ==============================================================================
+# OPTIONAL CONFIGURATION
+# ==============================================================================
+
+# Request Timeout (in milliseconds)
+# Maximum time to wait for Countly API responses
+# Default: 30000 (30 seconds)
+COUNTLY_TIMEOUT=30000
+
+
+# ==============================================================================
+# AUTHENTICATION PRIORITY
+# ==============================================================================
+# The server uses the following priority for authentication:
+# 1. MCP client metadata (metadata.countlyAuthToken)
+# 2. Tool argument (countly_auth_token)
+# 3. Environment variable (COUNTLY_AUTH_TOKEN)
+# 4. Token file (COUNTLY_AUTH_TOKEN_FILE)
+#
+# Client-provided tokens (1-2) will override server-level tokens (3-4)
+# This allows multi-tenant setups where different clients use different tokens
+
+
+# ==============================================================================
+# DOCKER DEPLOYMENT EXAMPLE
+# ==============================================================================
+# For Docker deployments with secrets:
+# 
+# docker run -d \
+#   -e COUNTLY_SERVER_URL=https://your-countly-instance.com \
+#   -e COUNTLY_AUTH_TOKEN_FILE=/run/secrets/countly_token \
+#   -v /path/to/token/file:/run/secrets/countly_token:ro \
+#   countly-mcp-server
+#
+# Or using Docker Compose:
+# 
+# services:
+#   countly-mcp:
+#     image: countly-mcp-server
+#     environment:
+#       COUNTLY_SERVER_URL: https://your-countly-instance.com
+#       COUNTLY_AUTH_TOKEN_FILE: /run/secrets/countly_token
+#     secrets:
+#       - countly_token
+# secrets:
+#   countly_token:
+#     file: ./countly_token.txt
+
+
+# ==============================================================================
+# MCP CLIENT CONFIGURATION EXAMPLE
+# ==============================================================================
+# If using MCP client (e.g., Claude Desktop), configure in your MCP settings:
+#
+# {
+#   "mcpServers": {
+#     "countly": {
+#       "command": "node",
+#       "args": ["/path/to/countly-mcp-server/build/index.js"],
+#       "env": {
+#         "COUNTLY_SERVER_URL": "https://your-countly-instance.com",
+#         "COUNTLY_AUTH_TOKEN": "your-auth-token-here"
+#       }
+#     }
+#   }
+# }
+#
+# Or using metadata for per-user authentication:
+#
+# {
+#   "mcpServers": {
+#     "countly": {
+#       "command": "node",
+#       "args": ["/path/to/countly-mcp-server/build/index.js"],
+#       "env": {
+#         "COUNTLY_SERVER_URL": "https://your-countly-instance.com"
+#       },
+#       "metadata": {
+#         "countlyAuthToken": "your-auth-token-here"
+#       }
+#     }
+#   }
+# }

.env.tools.example

@@ -0,0 +1,82 @@
+# Countly MCP Server - Tools Configuration Examples
+# 
+# Control which tool categories and CRUD operations are available
+# Format: COUNTLY_TOOLS_{CATEGORY}={OPERATIONS}
+# Operations: C (Create), R (Read), U (Update), D (Delete)
+#
+# Examples:
+#   CRUD or ALL or * = All operations enabled (default)
+#   CR = Only Create and Read
+#   R = Only Read (read-only mode)
+#   NONE or empty = Disable category completely
+
+# =============================================================================
+# DEFAULT CONFIGURATION (if not specified, all operations are allowed)
+# =============================================================================
+
+# Set default for all categories (can be overridden per category below)
+# COUNTLY_TOOLS_ALL=CRUD
+
+# =============================================================================
+# CATEGORY-SPECIFIC CONFIGURATION
+# =============================================================================
+
+# Core Tools (search, fetch) - Required for ChatGPT Connectors
+# These are read-only tools, typically should not be disabled
+# COUNTLY_TOOLS_CORE=R
+
+# Apps Management (list_apps, get_app_by_name, create_app, update_app, delete_app, reset_app)
+# Example: Allow read and create, but not update or delete
+# COUNTLY_TOOLS_APPS=CR
+
+# Analytics & Dashboards (get_analytics_data, get_dashboard_data, get_events_data, get_slipping_away_users, etc.)
+# Typically read-only
+# COUNTLY_TOOLS_ANALYTICS=R
+
+# Crash Analytics (list_crash_groups, view_crash, add/edit/delete comments, resolve, etc.)
+# Example: Allow read and comment creation, but not editing or deleting
+# COUNTLY_TOOLS_CRASHES=CR
+
+# Notes Management (list_notes, create_note, delete_note)
+# COUNTLY_TOOLS_NOTES=CRD
+
+# Events Configuration (create_event)
+# COUNTLY_TOOLS_EVENTS=C
+
+# Alerts Management (list_alerts, create_alert, delete_alert)
+# COUNTLY_TOOLS_ALERTS=CRD
+
+# Views Analytics (get_views_table, get_view_segments, get_views_data)
+# COUNTLY_TOOLS_VIEWS=R
+
+# Database Operations (query_database, list_databases, get_document, etc.)
+# Example: Read-only database access
+# COUNTLY_TOOLS_DATABASE=R
+
+# Dashboard User Management (get_all_dashboard_users)
+# Returns dashboard/admin users who access the Countly dashboard
+# COUNTLY_TOOLS_DASHBOARD_USERS=R
+
+# App User Management (create_app_user, delete_app_user, export_app_users)
+# Manages end-users of applications being tracked by Countly
+# COUNTLY_TOOLS_APP_USERS=CRD
+
+# =============================================================================
+# EXAMPLE CONFIGURATIONS
+# =============================================================================
+
+# Example 1: Read-only mode for everything
+# COUNTLY_TOOLS_ALL=R
+
+# Example 2: Full access to analytics and crashes, read-only for apps
+# COUNTLY_TOOLS_ANALYTICS=R
+# COUNTLY_TOOLS_CRASHES=CRUD
+# COUNTLY_TOOLS_APPS=R
+
+# Example 3: Disable database and user management completely
+# COUNTLY_TOOLS_DATABASE=NONE
+# COUNTLY_TOOLS_DASHBOARD_USERS=NONE
+# COUNTLY_TOOLS_APP_USERS=NONE
+
+# Example 4: Allow everything except deletion operations
+# COUNTLY_TOOLS_ALL=CRU