









































Works out-of-box with your favorite AI agents

ServiceMax is a field service management application for manufacturers and service providers that install and maintain equipment at customer sites. PTC acquired it in 2023. ServiceMax Core runs in the customer's Salesforce org and adds its own objects: Work Order for field and depot service events, Work Detail for labor, parts, travel and expense lines, Installed Product for the units delivered and installed at a customer location, plus Service Contract and Location, next to standard Salesforce records such as Case. Service managers, dispatchers and technicians share one installed base.
Where a connection exposes the relevant objects, the ServiceMax MCP lets an agent answer questions that need several list views and reports. A service manager asks which Work Orders for one account are still open past their scheduled date. A dispatcher has the agent pull the service history of one Installed Product before assigning a technician. A contracts lead checks which Installed Products are covered by an expiring Service Contract. The agent can also draft a Work Order for a dispatcher to review.
You sign in to your Salesforce org through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client, and get_connection_details shows which objects and fields that connection offers. Salesforce applies the connecting user's profile, permission sets and sharing rules to every request, so use an integration user with only the access needed. If you run Asset 360 for Salesforce instead of ServiceMax Core, the object names differ, so check get_connection_details first.
Have any questions? We’re here to help You
Yes, there are two kinds of MCP server for ServiceMax. ServiceMax AI has its own MCP server, toggled in the AI Console, which exposes AI actions configured in ServiceMax as MCP tools; it is in beta and off by default. Makini's ServiceMax MCP instead connects Claude, ChatGPT, Cursor or another client to the records in your Salesforce org, such as Work Orders and Installed Products, through one endpoint.
ServiceMax Core adds its own custom objects to a Salesforce org, with API names prefixed SVMXC__, while Asset 360 for Salesforce is built on standard Salesforce objects such as Asset, Work Order, Work Order Line Item and Service Contract. Some Asset 360 objects require a Salesforce Field Service license. Prompts written for one product will not match the other, so check get_connection_details for the objects your org really has.
In ServiceMax Core the Work Order object is SVMXC__Service_Order__c, with more than 200 fields. Commonly used ones are SVMXC__Order_Status__c, SVMXC__Order_Type__c (for example Field Service or Depot repair), SVMXC__Priority__c, SVMXC__Scheduled_Date_Time__c and SVMXC__Dispatch_Status__c, a formula field that shows the stage of the order. Using these exact names helps when you ask an agent to filter or group Work Orders.
ServiceMax Core data lives in your Salesforce org, so it is reached through the Salesforce APIs rather than a separate ServiceMax API. API access is on by default in Enterprise, Performance, Unlimited and Developer editions, and Professional Edition can add it. Every caller needs the API Enabled permission. With Makini your agent never calls Salesforce directly: it talks to the Makini MCP endpoint, and Makini maintains the connector.
ServiceMax uses the Covered Product object, which lists the installed products, part numbers or groups of products entitled by a Service Contract. Each Covered Product belongs to its contract and can point to an Installed Product, a Product and SLA Terms. Where the connection exposes these records, an agent can list the units on one contract and flag Work Orders raised against units without coverage.
A ServiceMax connection needs a Salesforce user with the API Enabled permission and read access to the ServiceMax objects the agent should use. A dedicated user, for example on the Salesforce Integration user license, keeps agent activity separate from staff logins. Grant object access through permission sets, and remember that sharing rules decide which accounts and Work Orders appear. Makini scopes the connection's token to those credentials and logs every call.
ServiceMax Go lets technicians capture work order debriefs and customer signatures offline, and Smart Sync sends them to Salesforce later, on a schedule, manually or after a record update. The agent reads your Salesforce org through Makini, so work captured offline appears only after the device has synced. When asking about jobs finished in the last hour, expect some of them to be missing.
Makini's ServiceMax tool list includes create_work_order and update_work_order, but a write succeeds only where your connection exposes it and the Salesforce user has create or edit rights on the object. Validation rules, required fields and automation in your org still run on every saved record. Start with read-only questions, let the agent draft Work Orders for a dispatcher to review, and test writes in a sandbox first.