Skip to main content

Connectors

Modified: 6 Nov 2026 Trimble Agent Studio Workflows Help

Go to Build > Connectors to create and manage custom connectors so agents can discover and use external tools.

Note: The MCP connector registry in Trimble Agent Studio is an early-access feature, ahead of the full connector marketplace launch on the Trimble Console. Expect the workflow below to evolve.

A connector registers an external MCP (Model Context Protocol) server with Trimble Agent Studio, so its tools can be discovered, governed, and enabled on any agent. Once registered, a connector appears in the connector catalog and can be attached to any agent you have access to.

The Connectors page lists every MCP server registered in your organization, grouped into My connectors and Third Party sections. Select Show more to expand a section. Each card shows who owns the connector, how many tools it exposes, its health, and its type: a native MCP Server or an API Bridge that exposes an existing OpenAPI service as MCP tools. Connectors communicate over HTTPS with Trimble ID authentication. The agent acts with the user's identity and permissions, so a person cannot do more through an agent than they could do directly.

Switch between grid and list layouts with the layout toggle.

Select a connector to view its overview and the tools affiliated with it. A tool is a single callable capability exposed by a connector, such as get_current_weather or get_forecast.

Figure 1. A connector's tools

Browsing the connector catalog and opening a connector's tools

To register a new connector, select New. For instructions, see Register a new MCP connector.

Figure 2. Connectors

The Connectors catalog with the My connectors section and Third Party connectors

Built-in tools

On an agent, open the Built-in tab of Add tools to enable platform tools. datetime is almost always worth enabling, because without it the model does not reliably know what today is. myprofile lets an agent personalize answers without asking. Image generation is a switch on the agent settings Outputs tab, not a built-in tool.

Figure 3. Built-in tools

The Built-in tab of the Add tools dialog with a toggle per tool
Tool What it gives the agent
API Request (curl) HTTP requests to APIs, similar to the curl CLI
Datetime (datetime) The current date and time
Unload Old Tool Results (fetch_tool_result) Unloads old tool results to save tokens, and loads them back when needed
My Profile (myprofile) The current user's identity, contact information, and organization
Past Conversations Access (search_past_conversations, list_past_conversations, get_past_run) Search, list, and read the current user's past conversations with this agent
Trimble Help (trimble_help) Search of Trimble Help articles
URL Context (url_context) Fetch and extract content from public web URLs
User Directory (list_users_in_account, list_users_in_organization, get_user_by_id) Look up people in the organization or account directory
Web Search (web_search) Web search for current information

Custom MCP, client-side tools, and Agent UI Kit

The Custom MCP tab attaches a server to one agent (name, URL, and authentication: none, on-behalf-of actor token, or agent token). Custom MCP connections are marked for deprecation; prefer registering a connector so the server is governed and reusable.

When a host application embeds Trimble Assist, it can register client-side tools that run locally in the application (for example navigate the UI, read the current selection, or scroll to a section).

The Agent UI Kit connector lets an agent return charts, sortable tables, and diagrams instead of plain text.

Figure 4. Agent UI Kit

An agent answering with a chart in Trimble Assist

For a video walkthrough of connectors, see Using connectors - Video.

Submit

Table of Contents