home / mcp / servicetitan mcp server
Provides direct access to ServiceTitan data and actions via MCP, including customers, jobs, appointments, technicians, and invoices.
Configuration
View docs{
"mcpServers": {
"cahlan-servicetitan-mcp": {
"command": "servicetitan-mcp",
"args": [],
"env": {
"ST_APP_KEY": "YOUR_APP_KEY",
"ST_CLIENT_ID": "YOUR_CLIENT_ID",
"ST_TENANT_ID": "YOUR_TENANT_ID",
"ST_ENVIRONMENT": "production",
"ST_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
}
}
}
}You can use this MCP server to give AI assistants direct access to ServiceTitan, enabling you to manage jobs, look up customers, schedule appointments, dispatch technicians, and track invoices from your AI workflows. It acts as a bridge between your AI client and ServiceTitan’s data and actions, streamlining contractor workflows.
To use this MCP server, connect it to your MCP client by running the server locally or hosting it in your environment, then reference it in your client configuration. Once connected, you can search for customers, view and manage jobs, check invoices, find appointment slots, and assign technicians all through natural language prompts or structured prompts supported by your AI assistant.
Prerequisites you need on your machine before installation:
Step by step installation and run flow:
# 1) Install the package in editable mode
pip install -e .
# 2) Run the MCP server (command form)
servicetitan-mcp
# 3) Or run the server directly via Python (module form)
python -m servicetitan_mcp.serverConfiguration and startup require environment variables for ServiceTitan access. You will typically set these in your environment or in a dedicated .env file used by your process manager. The variables you need are shown in the configuration examples and in the connection setup below.
The server uses OAuth2 Client Credentials for authentication with ServiceTitan. Your client credentials and application key must be kept secure and not exposed in client-side code. Use a secure secret store or environment management to inject ST_CLIENT_ID, ST_CLIENT_SECRET, ST_APP_KEY, ST_TENANT_ID, and ST_ENVIRONMENT at runtime.
The following environment variables are required to run and used by the server. They should be provided to the MCP server process at startup.
Search customers by name, phone, email, or address.
Get full customer details including contacts and service history.
List jobs with filters for status, date range, customer, or technician.
Get complete job details including notes and assigned tech.
Create a new job for a customer.
Find available appointment slots in a date range.
Schedule or reschedule a job appointment.
List active technicians with current status and schedule.
Assign a technician to a job appointment.
Get invoice details with line items and payment status.
List unpaid/overdue invoices for collections follow-up.