@rowvyn/servicetitan-mcp 2.4.0 → 2.4.2

package/.env.example

@@ -10,7 +10,7 @@ ST_READONLY=true                     # true | false (default: true)
 ST_CONFIRM_WRITES=false              # Require _confirmed: true on write operations (default: false)
 ST_DOMAINS=                          # comma-separated: crm,pricebook,reporting (empty = all)
 ST_LOG_LEVEL=info                    # debug | info | warn | error
-ST_TIMEZONE=                         # IANA timezone for date alignment (e.g. America/New_York)
+ST_TIMEZONE=                         # IANA timezone for date alignment and display conversion (e.g. America/New_York)
 ST_MAX_RESPONSE_CHARS=100000         # Max characters in tool response before truncation
 ST_ALLOWED_CALLERS=                  # Optional comma-separated caller allowlist (matches authInfo or proxy-injected caller headers when available)
 # ST_RESPONSE_SHAPING=true           # Set to false to disable response transformation (returns raw API data)

package/CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/), and this project adheres to [Semantic Versioning](https://semver.org/).
 
+## [2.4.2] - 2026-03-29
+
+### Fixed
+- **README cleanup** — removed misleading "0.001% revenue accuracy" stat (replaced with "Dashboard-matched revenue"), stripped internal "Report 175" jargon throughout. No code changes.
+
 ## [2.4.0] - 2026-03-28
 
 ### Added

package/README.md

@@ -20,7 +20,7 @@ The only MCP server for the ServiceTitan API — 467 tools across 15 domains, pl
 - **ServiceTitan has no official MCP server** or developer tooling beyond REST docs
 - **Raw API access is friction-heavy** — OAuth token management, module-prefix routing, pagination, and response parsing all fall on you
 - **This server handles all of that** and adds 10 intelligence tools that aggregate multiple endpoints into operational insights
-- **Revenue accuracy within 0.001% of ServiceTitan's own dashboard** (verified on production data using Report 175 — the same source ST's internal engine uses)
+- **Dashboard-matched revenue** — verified on production data using the same Reporting API source that powers ST's own dashboard
 
 ---
 
@@ -28,7 +28,7 @@ The only MCP server for the ServiceTitan API — 467 tools across 15 domains, pl
 
 - **467 tools across 15 domains** — CRM, dispatch, accounting, payroll, inventory, marketing, and more
 - **10 intelligence tools** — composite analytics that aggregate multiple API calls into revenue summaries, ops snapshots, technician scorecards, and more
-- **Dashboard-accurate revenue** — `intel_revenue_summary` uses Report 175 to match ST's dashboard within 0.001%
+- **Dashboard-matched revenue** — `intel_revenue_summary` pulls from the same source as ST's own dashboard
 - **Read-only by default** — `ST_READONLY=true` out of the box; write tools only activate when you're ready
 - **Safety layer** — confirmation workflow for writes/deletes, audit logging with sensitive field redaction
 - **Domain filtering** — expose only the tool groups you need via `ST_DOMAINS`
@@ -183,7 +183,7 @@ The real differentiator. These 10 tools aggregate multiple API calls and report
 
 | Tool | What It Returns |
 |------|----------------|
-| `intel_revenue_summary` | Dashboard-accurate revenue by business unit using Report 175 — matches ServiceTitan within 0.001%. Includes completed revenue, non-job revenue, adjustments, collections, and BU productivity rollups. |
+| `intel_revenue_summary` | Dashboard-matched revenue by business unit. Includes completed revenue, non-job revenue, adjustments, collections, and BU productivity rollups. |
 | `intel_daily_snapshot` | 6-metric same-day ops briefing: revenue-to-date, jobs in progress, call outcomes, bookings, open estimates, and upcoming next-day jobs. |
 | `intel_technician_scorecard` | Per-tech jobs, revenue, avg ticket, productivity, lead gen, membership close rate, and sales from both tech and marketing leads — with team averages. |
 | `intel_membership_health` | Active memberships, signups, cancellations, renewals, retention rate, invoiced revenue, and conversion by business unit. |
@@ -198,7 +198,7 @@ These tools are why this server exists. Raw CRUD tools are table stakes. Intelli
 
 ### Revenue Accuracy
 
-`intel_revenue_summary` uses ServiceTitan's **Reporting API** (Report 175: "Revenue") to calculate totals. This is the same source ST's own dashboard uses — which means it includes:
+`intel_revenue_summary` uses ServiceTitan's **Reporting API** to calculate totals. This is the same source ST's own dashboard uses — which means it includes:
 
 - **Completed Revenue** — revenue from completed jobs
 - **Non-Job Revenue** — membership fees, add-ons, and other income not tied to a specific job
@@ -246,7 +246,7 @@ Copy `.env.example` to `.env` and fill in your credentials.
 | `ST_MAX_RESPONSE_CHARS` | `100000` | Cap tool response size |
 | `ST_DOMAINS` | *(all)* | Comma-separated domain allowlist (e.g. `crm,dispatch,reporting`) |
 | `ST_LOG_LEVEL` | `info` | Log level: `debug`, `info`, `warn`, `error` |
-| `ST_TIMEZONE` | `UTC` | IANA timezone for the tenant (e.g. `America/New_York`) — critical for date-bound intelligence tools |
+| `ST_TIMEZONE` | `UTC` | IANA timezone for the tenant (e.g. `America/New_York`) — used for date-bound intelligence queries and local-time display conversion in all tool responses |
 | `ST_RESPONSE_SHAPING` | `true` | Set to `false` to disable intelligence response transformation |
 | `ST_CORS_ORIGIN` | _(none)_ | Allowed CORS origin for Streamable HTTP / SSE. Required for browser access. |
 | `ST_ALLOWED_CALLERS` | _(none)_ | Comma-separated caller identity allowlist (e.g. `alice@example.com,svc-user`) |
@@ -254,7 +254,7 @@ Copy `.env.example` to `.env` and fill in your credentials.
 | `ST_MCP_PORT` / `PORT` | `3100` | HTTP server port for Streamable HTTP and SSE transports |
 | `ST_MCP_API_KEY` | _(none)_ | API key for authenticating remote MCP clients (required for HTTP transports) |
 
-> **Set `ST_TIMEZONE`** to your tenant's local timezone. Without it, date-only queries (e.g. `startDate: "2026-02-01"`) are interpreted as UTC midnight — which can miss or include invoices and jobs near day boundaries for non-UTC tenants.
+> **Set `ST_TIMEZONE`** to your tenant's local timezone. Without it, date-only queries (e.g. `startDate: "2026-02-01"`) are interpreted as UTC midnight — which can miss or include invoices and jobs near day boundaries for non-UTC tenants, and tool responses will keep timestamps in UTC instead of your local display timezone.
 
 Boolean env vars accept: `true`, `false`, `1`, `0` (case-insensitive).
 
@@ -299,7 +299,7 @@ The CLI and this MCP server share the same design philosophy: push the business
 
 | Feature | This Server | Community MCP Servers |
 |---------|------------|----------------------|
-| Revenue accuracy | ✅ 0.001% of dashboard | ❌ $17–21K off per period |
+| Revenue accuracy | ✅ Dashboard-matched | ❌ $17–21K off per period |
 | Intelligence tools | ✅ 10 tools | ❌ None |
 | Domain coverage | ✅ 467 tools, 15 domains | ⚠️ 10–50 tools |
 | Safety layer | ✅ Read-only default, audit log | ❌ None |