trimble-connect-mcp
A local MCP server giving Claude access to Trimble Connect, with 40 tools for projects, folder trees, files, versions, members, groups, and permissions via the Core API v2.
README
Trimble Connect MCP
A local (stdio) MCP server that gives Claude access to Trimble Connect: projects, folder trees, files, versions, members, groups and permissions — 40 tools over the Core API v2.
Contents
- Requirements
- Step 1 — Install
- Step 2 — Register a Trimble application
- Step 3 — Configure Claude Desktop
- Step 4 — First run
- Write mode
- Other MCP clients
- Environment variables
- Tools
- Troubleshooting
- Contributing
- License
Requirements
| Item | Requirement |
|---|---|
| OS | Windows 10/11 (macOS and Linux should work but are untested) |
| Host | Claude Desktop, Codex, or any MCP client that speaks stdio |
| Python | 3.10+ |
| uv | Install uv |
| Account | A Trimble ID with access to your Trimble Connect projects |
Step 1 — Install
git clone https://github.com/nhantruong96/trimble-connect-mcp.git
cd trimble-connect-mcp
uv sync
Check that the server imports:
uv run python -c "import server; print('OK')"
Run uv sync again after every git pull.
Step 2 — Register a Trimble application
-
Go to the Trimble Developer Console and create an application.
-
Copy the Client ID and Client Secret.
-
Under Callback URLs, add exactly:
http://localhost:8385/callback -
If port 8385 is already taken, change it in both places: the Callback URL in the Developer Console and
TC_REDIRECT_URIin your config (for examplehttp://localhost:8590/callback).
The redirect URI must match character for character — http://localhost without
a port, 127.0.0.1 instead of localhost, or a missing /callback will all be
rejected.
Step 3 — Configure Claude Desktop
Open %APPDATA%\Claude\claude_desktop_config.json (or Settings → Extensions)
and add the block below, replacing the paths and the client id/secret:
{
"mcpServers": {
"trimble-connect": {
"command": "C:\\path\\to\\trimble-connect-mcp\\.venv\\Scripts\\python.exe",
"args": ["C:\\path\\to\\trimble-connect-mcp\\server.py"],
"env": {
"TC_CLIENT_ID": "<client id>",
"TC_CLIENT_SECRET": "<client secret>",
"TC_APP_NAME": "Trimble_Connect_MCP",
"TC_REDIRECT_URI": "http://localhost:8385/callback",
"TC_ENABLE_WRITE": "1"
}
}
}
}
A ready-made template is in
claude_desktop_config.example.json.
Never commit your real config — it holds the client secret.
Quit Claude Desktop completely, then reopen it.
Step 4 — First run
Ask in plain language:
"Sign in to Trimble Connect, then list my projects."
- The browser opens the Trimble ID page; once you sign in the tools are ready.
- Tokens refresh automatically — you only sign in once.
- After 90 seconds
tc_loginreturnspending=trueplus anauth_url. Finish signing in in the browser, then ask Claude to calltc_auth_status. - If you abandon a sign-in, call
tc_login_cancelbefore starting a new one. - To sign out, delete
%USERPROFILE%\.trimble_connect_mcp\tokens.json.
The region (NA / EU / AP) is detected automatically and cached in
%USERPROFILE%\.trimble_connect_mcp\.
Write mode
The server is read-only by default. Two gates protect every write:
- Set
TC_ENABLE_WRITE=1in theenvblock of your config and restart the host. Verify withtc_write_status. - Destructive tools (delete, overwrite a version, replace an ACL, remove a
member) additionally require
confirm=true.
There is no restore tool — Core API 2.0 has no undelete endpoint. Deleted items can only be recovered by hand in the Trimble Connect web interface.
Other MCP clients
- Take the
.venv\Scripts\python.exeandserver.pypaths from Step 3. - Register a stdio server using them as
commandandargs. - Set the same environment variables as in Step 3.
- Restart the client.
To check that the server starts at all:
uv run python server.py
Environment variables
| Variable | Default | Notes |
|---|---|---|
TC_CLIENT_ID |
— | required |
TC_CLIENT_SECRET |
— | required |
TC_APP_NAME |
Trimble_Connect_MCP |
used in the OAuth scope (openid <app name>) |
TC_REDIRECT_URI |
http://localhost:8385/callback |
must match the URL registered in the Developer Console |
TC_DOWNLOAD_DIR |
~/Downloads/TrimbleConnect |
where downloaded files are saved |
TC_TOKEN_DIR |
~/.trimble_connect_mcp |
where tokens and the region cache are stored |
TC_ENABLE_WRITE |
(off) | set to 1 to enable the write / delete / permission tools |
Tools
Read — always available
| Tool | What it does |
|---|---|
tc_login |
Sign in with Trimble ID in the browser (OAuth2 + PKCE), callback http://localhost:8385/callback. Non-blocking: past wait_seconds (default 90s) it returns pending=true and keeps listening in the background for up to 10 minutes |
tc_login_cancel |
Cancel a pending sign-in and release the callback port |
tc_auth_status |
Sign-in status, including login_in_progress |
tc_write_status |
Whether write mode is on, and how to turn it on |
tc_list_regions |
List the server regions (NA / EU / AP) |
tc_list_projects |
List projects across every region, filter by name, refresh=true to bypass the cache |
tc_get_project |
Details of one project |
tc_list_project_members |
Project members and their roles |
tc_list_project_roles |
The project's roles (ADMIN / USER) |
tc_list_folder |
Contents of a folder (defaults to the project root) |
tc_folder_tree |
Folder tree as text, bounded by depth and entry count |
tc_get_file |
File metadata |
tc_list_file_versions |
Version history of a file |
tc_download_file |
Download a file (default ~/Downloads/TrimbleConnect) |
tc_search |
Keyword search |
tc_get_permissions |
Read the ACL of a folder or file |
tc_list_groups / tc_list_group_users |
Project groups and their members |
tc_api_get |
Raw GET against any Core API endpoint (todos, views, releases, activities…) |
Write — folders and files (needs TC_ENABLE_WRITE=1)
| Tool | What it does | Gate |
|---|---|---|
tc_create_folder |
Create one folder | — |
tc_create_folder_structure |
Create a whole tree (e.g. a CDE) from paths like 01-WIP/01-ARC; existing folders are skipped, so it is safe to re-run |
— |
tc_rename_item |
Rename a folder or file | — |
tc_move_item |
Move a folder or file to another folder | — |
tc_copy_file |
Copy a file (server-side) | — |
tc_copy_folder |
Copy a folder with its contents (the server walks the tree; bounded by max_items) |
— |
tc_upload_file |
Upload a NEW file (fails if the name already exists) | — |
tc_upload_new_version |
Upload a NEW VERSION of an existing file | confirm=true |
tc_delete_item |
Delete a folder or file (force=true for a non-empty folder) |
confirm=true |
Write — permissions
| Tool | What it does | Gate |
|---|---|---|
tc_grant_permissions |
Grant READ / FULL_ACCESS / NO_ACCESS to users or groups — merges safely by reading the current ACL and changing only the entries you name |
— |
tc_remove_permissions |
Drop users or groups from the ACL (back to inherited access) | confirm=true |
tc_set_permissions |
Replace the ENTIRE ACL (advanced — wipes existing entries) | confirm=true |
Trimble Connect has only three levels: READ, FULL_ACCESS, NO_ACCESS (files
do not support NO_ACCESS). The special id tc-groups:* means every project
member. The underlying PATCH .../permissions overwrites the whole ACL, which
is why tc_grant_permissions / tc_remove_permissions are preferred over
tc_set_permissions.
Write — members and groups
| Tool | What it does | Gate |
|---|---|---|
tc_add_project_user |
Invite a user to the project by email (role: USER/ADMIN) |
— |
tc_update_project_user |
Change a member's role | — |
tc_remove_project_user |
Remove a member from the project | confirm=true |
tc_create_group / tc_rename_group |
Create or rename a group | — |
tc_add_group_users |
Add members to a group | — |
tc_remove_group_users |
Remove members from a group | confirm=true |
tc_delete_group |
Delete a group (any permission granted to it is lost) | confirm=true |
tc_api_write |
Raw POST/PATCH/PUT/DELETE for endpoints with no dedicated tool | confirm=true |
Troubleshooting
| Symptom | Fix |
|---|---|
redirect_uri mismatch on the sign-in page |
The URL in the Developer Console must match TC_REDIRECT_URI character for character (Step 2) |
Cannot listen on localhost port 8385 |
The port is taken — call tc_login_cancel, or change the port in both places (Step 2) |
Browser shows connection refused on the callback page |
The sign-in wait expired (10 minutes) — call tc_login again |
tc_login returns pending: true |
Not an error — finish signing in, then call tc_auth_status |
Writing to Trimble Connect is disabled |
TC_ENABLE_WRITE=1 is not set, or the host was not restarted |
Refused: this would… |
A destructive tool needs confirm=true — check the target, then call again |
| HTTP 403 | Your Trimble account has no access to that project |
| HTTP 409 / 412 on create or upload | An item with that name exists — to overwrite, use tc_upload_new_version |
| No projects listed | Run tc_list_projects with refresh=true; check tc_auth_status shows the right account |
ImportError: cannot import name 'MCPServer' |
You are on mcp 1.x — run uv sync to get the 2.x version pinned in uv.lock |
| An endpoint has no dedicated tool (ToDos, Views, Releases, Activities…) | Use tc_api_get, e.g. todos?projectId=… or projects/{id}/activities |
Contributing
Development setup, repository layout, and how to add a tool are in CONTRIBUTING.md.
The upstream API is https://app.connect.trimble.com/tc/api/2.0 (master, North
America); other regions are discovered through the /regions endpoint.
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.