-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.env.example
More file actions
53 lines (48 loc) · 2.9 KB
/
Copy path.env.example
File metadata and controls
53 lines (48 loc) · 2.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# Environment variables for the UTM Helper MCP server.
#
# Copy to .env and adjust:
# cp .env.example .env
#
# The .env file is auto-discovered when running the server (even from
# subdirectories). NEVER commit your .env file.
#
# -----------------------------------------------------------------------------
# Configuration is POINTERS ONLY: it says *where to look* for the spec, never
# how the server behaves. All behavior lives in the spec repo (GUIDE.md /
# utm-spec.yaml), changed by reviewed PR.
#
# The single pointer is provided as the Arcade tool secret UTM_SPEC_SOURCE_URL.
# - Production: set it on the Arcade dashboard (or `arcade secret set`).
# - Local dev: set it here in .env — Arcade injects it into the tool Context.
# -----------------------------------------------------------------------------
# UTM_SPEC_SOURCE_URL — the raw base URL of the Git spec source. The server
# appends file names (e.g. GUIDE.md) to it, so it MUST end in a "/" path that
# serves raw file contents. Works with any host that serves raw files
# (GitHub raw, GitLab raw, a self-hosted mirror, ...).
#
# Leave this UNSET to use the announced first-run default: the opinionated seed
# spec shipped in this repo (ArcadeAI/utm-helper-mcp@main). A warning is logged
# when the default is used, so a misconfigured deploy is never silent.
#
# UTM_SPEC_SOURCE_URL="https://raw.githubusercontent.com/ArcadeAI/utm-helper-mcp/main/"
# -----------------------------------------------------------------------------
# Campaign registry (Google Sheet) — pointers + a shared service credential.
#
# The utm_campaign registry lives in a Google Sheet read by list_campaigns().
# The Sheet is read with a server-side SERVICE-ACCOUNT credential, so end users
# need no direct Google/Sheet access. Setup (admin):
# 1. Create a Google Cloud service account; download its key JSON.
# 2. Enable the Google Sheets API for that project.
# 3. Share the registry Sheet (Viewer) with the service account's email.
# 4. The Sheet's first row MUST be exactly: campaign | description | added_by | added_at
# -----------------------------------------------------------------------------
# UTM_CAMPAIGN_SHEET_ID — the Sheet ID (the long token in the Sheet URL between
# /d/ and /edit). Required; there is no default registry, so a missing ID fails
# loud rather than guessing.
# UTM_CAMPAIGN_SHEET_ID="1AbCdEfGhIjKlMnOpQrStUvWxYz0123456789abcdEFG"
# UTM_CAMPAIGN_SHEET_RANGE — the A1 tab/range to read. Optional; defaults to
# "Campaigns!A:D" (the whole Campaigns tab, columns A–D).
# UTM_CAMPAIGN_SHEET_RANGE="Campaigns!A:D"
# UTM_CAMPAIGN_SA_JSON — the FULL service-account key JSON (one line). Required
# for list_campaigns(). Keep this secret; never commit it.
# UTM_CAMPAIGN_SA_JSON='{"type":"service_account","project_id":"...","private_key":"-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n","client_email":"svc@project.iam.gserviceaccount.com", ...}'