servicetitan-api

To fetch ServiceTitan data across multiple tenants, use the MCP connector with bearer token authentication to execute per-tenant tool calls for jobs, leads, and revenue data within specified date ranges. It supports four tenants: utah, grimes, rivercity, and rivercity2.

Yes, you can consolidate ServiceTitan revenue and technician performance metrics from different branches by running per-tenant get_revenue and get_technician_performance tool calls across the four supported tenants, enabling centralized executive reporting and strategic decision-making.

Available ServiceTitan data endpoints include get_leads for lead attribution and get_business_units for business unit tracking, alongside endpoints for jobs, technician performance, revenue, and customer data, all accessible through per-tenant MCP tool calls.

Multi-tenant data access for ServiceTitan accounts from Utah to rivercity2 works by providing a defined set of isolated per-tenant tools, each requiring bearer token authentication to securely retrieve tenant-specific jobs, leads, and customer data via endpoint-based retrieval.

Yes, you need bearer token authentication to securely retrieve ServiceTitan customer data via MCP, as the connector enforces secure access through endpoint-based data retrieval and defined per-tenant tool calls with date-range inputs.

The best way to centralize ServiceTitan service metrics for executive reporting is to use a multi-tenant MCP connector to aggregate jobs, leads, and revenue data across all tenants, consolidating monthly service metrics into a unified view.