Mandate 5: Standardized APIs, MCPs, and Gateway

Access to Trimble’s capabilities will adhere to the standardized API structure and be managed through a unified API and/or MCP gateway.

Why? So that…

Trimble’s APIs and MCP servers…

Are discoverable in a common way (internally and externally).
Utilize common Trimble identity and access management.
Are available to developer personas (internal and external) via modern web protocols.
Well documented for workflow (connector/transformer) and agentic (MCP) uses.
Protected by platform services in conjunction with Trimble cyber security.

What do I need to do?

For APIs

Register your APIs as proxies in the Cloud Console.
Upload your Open API Specification to the Cloud Console.
Review and address the Trimble API linting results based on your API Specification.

For MCPs

How this mandate is measured

Are your APIs published in Trimble Cloud Console?
Are your MCPs registered in Trimble Agent Studio?
Have your OpenAPI specifications been linted by Trimble’s API Standard Spectral ruleset?

Getting started & more information

All Trimble teams can publish HTTP APIs to the Trimble Cloud Console today. More information…

All Trimble teams can lint their APIs today using the Trimble HTTP API linter based on Spectral. More information… This ruleset is being incorporated into Cloud Console, so all APIs published in the Console are linted by default, starting in Q2 2026.

Q: Is there a template for MCPs that our team can use to get started?

A: Yes, please reach out to Tyler Barnard or Ciprian Borzasi for how to gain access.

Q: How do I register my MCP?

A: You can register your MCP server at

Stage: https://studio.stage.trimble-ai.com

Prod: https://studio.ai.trimble.com (Coming Soon)

Q: What is API linting?

A: An API linter is a ruleset that checks an API for compliance with many of Trimble’s API standards and then provides API improvement recommendations.

If you have a capability that is better suited for asynchronous processing, see Mandate 4.