Skip to main content
Glama
fmeies

etracker MCP Server

by fmeies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

etracker MCP Server

An MCP (Model Context Protocol) server that exposes the etracker analytics API to AI assistants. Partners connect via HTTP/SSE and authenticate with their own API key plus an etracker account token passed per request.

Architecture

  • Transport: StreamableHTTP (MCP over HTTP + SSE)

  • Auth: Two-header scheme — X-Api-Key (partner key) + X-ET-Token (etracker account token)

  • Rate limiting: Three-layer bucket — burst guard (8 req/10 s), global window (40 req/5 min), per-partner window (20 req/5 min)

  • Sessions: In-memory, scoped per MCP session. Session affinity (ClientIP) required when running multiple replicas.

Related MCP server: analytics.usa.gov MCP Server

Endpoints

Method

Path

Auth

GET

/health

none

ALL

/mcp

required

Tools

Tool

Description

list_reports

Lists all available etracker reports for the account

get_report_info

Returns available attributes and key figures for a report

get_report_metadata

Returns raw column definitions (types, sortable, filterable flags)

get_pageviews

Web analytics data (default report: EATime)

get_conversions

Conversion and e-commerce data (default report: EAConversions)

get_ad_performance

Marketing/ad channel performance (default report: EAMarketing)

get_report_data

Generic tool — fetch data from any report with filters

compare_periods

Compare a metric between two date ranges

All data tools accept from/to (YYYY-MM-DD, max 90 days), optional attributes and figures (up to 5 each), limit/offset, and sort_column/sort_order.

Authentication

The etracker token is not stored in the server — partners pass it per request via X-ET-Token. The server only stores the mapping of partner API keys to partner IDs.

Generate a partner key:

openssl rand -hex 32

PARTNER_API_KEYS format (JSON object):

{"<key>": "<partner-id>", "<key2>": "<partner-id2>"}

Local development

cp .env.example .env
# Edit .env and set PARTNER_API_KEYS
npm install && npm run dev

Docker

docker build -t etracker-mcp .
docker run -p 3000:3000 \
  -e PARTNER_API_KEYS='{"mykey":"partner-a"}' \
  etracker-mcp

Docker Compose

cp .env.example .env
# Edit .env: set PARTNER_API_KEYS and IMAGE
docker compose up -d

Kubernetes / Helm

Do not use --set for partnerApiKeys — Helm interprets {, }, and , as special syntax and corrupts the JSON. Use a values file instead:

# my-values.yaml
partnerApiKeys: '{"<key>":"<partner-id>"}'
service:
  type: ClusterIP  # or NodePort / LoadBalancer
helm install etracker-mcp ./helm -f my-values.yaml

Ingress

# my-values.yaml
partnerApiKeys: '{"<key>":"<partner-id>"}'
ingress:
  enabled: true
  className: nginx
  host: etracker-mcp.example.com
  tls: true
  tlsSecretName: etracker-mcp-tls

All Helm values

Value

Default

Description

partnerApiKeys

""

JSON object mapping API keys to partner IDs

replicaCount

1

Number of replicas (session affinity handles routing)

image.repository

etracker-mcp

Container image

image.tag

latest

Image tag

service.type

NodePort

Service type

service.nodePort

30300

NodePort value (30000–32767)

service.sessionAffinityTimeoutSeconds

3600

Session stickiness timeout

ingress.enabled

false

Enable ingress

ingress.host

etracker-mcp.example.com

Ingress hostname

ingress.tls

false

Enable TLS

etrackerReports.pageviews

EATime

Override default pageviews report ID

etrackerReports.conversions

EAConversions

Override default conversions report ID

etrackerReports.ad

EAMarketing

Override default ad report ID

resources.requests.cpu

100m

CPU request

resources.requests.memory

128Mi

Memory request

resources.limits.cpu

500m

CPU limit

resources.limits.memory

256Mi

Memory limit

MCP client configuration

{
  "mcpServers": {
    "etracker": {
      "url": "https://etracker-mcp.example.com/mcp",
      "headers": {
        "X-Api-Key": "<your-partner-key>",
        "X-ET-Token": "<your-etracker-token>"
      }
    }
  }
}

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • AppSignal MCP

    pauldub
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to query and fetch error and performance monitoring data from AppSignal through the Model Context Protocol. Supports searching and retrieving detailed information about application errors and performance samples with flexible filtering options.
    5
    MIT
  • analytics.usa.gov MCP Server by GSA-TTS

    analytics.usa.gov MCP Serverofficial

    GSA-TTS
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables LLMs to query and analyze government website analytics from analytics.usa.gov via the Model Context Protocol, supporting single report, multiple reports, and aggregation tools.
    4
    MIT

  • Measure.events MCP Server

    Le-Circus
    A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to query privacy-first web analytics from Measure.events, including pageviews, top pages, referrers, and custom event tracking, all via natural language.
    6
    2
    MIT