trimble-connect-mcp
Provides tools for interacting with Trimble Connect, enabling management of projects, folder trees, files, versions, members, groups, and permissions via the Core API v2.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@trimble-connect-mcp Sign in to Trimble Connect, then list my projects."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: routine-mcp
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 | |
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 syncCheck 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/callbackIf 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.pyEnvironment variables
Variable | Default | Notes |
| — | required |
| — | required |
|
| used in the OAuth scope ( |
|
| must match the URL registered in the Developer Console |
|
| where downloaded files are saved |
|
| where tokens and the region cache are stored |
| (off) | set to |
Tools
Read — always available
Tool | What it does |
| Sign in with Trimble ID in the browser (OAuth2 + PKCE), callback |
| Cancel a pending sign-in and release the callback port |
| Sign-in status, including |
| Whether write mode is on, and how to turn it on |
| List the server regions (NA / EU / AP) |
| List projects across every region, filter by name, |
| Details of one project |
| Project members and their roles |
| The project's roles (ADMIN / USER) |
| Contents of a folder (defaults to the project root) |
| Folder tree as text, bounded by depth and entry count |
| File metadata |
| Version history of a file |
| Download a file (default |
| Keyword search |
| Read the ACL of a folder or file |
| Project groups and their members |
| 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 |
| Create one folder | — |
| Create a whole tree (e.g. a CDE) from paths like | — |
| Rename a folder or file | — |
| Move a folder or file to another folder | — |
| Copy a file (server-side) | — |
| Copy a folder with its contents (the server walks the tree; bounded by | — |
| Upload a NEW file (fails if the name already exists) | — |
| Upload a NEW VERSION of an existing file |
|
| Delete a folder or file ( |
|
Write — permissions
Tool | What it does | Gate |
| Grant | — |
| Drop users or groups from the ACL (back to inherited access) |
|
| Replace the ENTIRE ACL (advanced — wipes existing entries) |
|
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 |
| Invite a user to the project by email ( | — |
| Change a member's role | — |
| Remove a member from the project |
|
| Create or rename a group | — |
| Add members to a group | — |
| Remove members from a group |
|
| Delete a group (any permission granted to it is lost) |
|
| Raw POST/PATCH/PUT/DELETE for endpoints with no dedicated tool |
|
Troubleshooting
Symptom | Fix |
| The URL in the Developer Console must match |
| The port is taken — call |
Browser shows | The sign-in wait expired (10 minutes) — call |
| Not an error — finish signing in, then call |
|
|
| A destructive tool needs |
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 |
No projects listed | Run |
| You are on |
An endpoint has no dedicated tool (ToDos, Views, Releases, Activities…) | Use |
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
Available Tools
40 toolstc_add_group_usersA
Add project members to a group.
Requires TC_ENABLE_WRITE=1. Users must already be project members (invite them first with tc_add_project_user).
Args: project_id: Project ID. group_id: Group ID. user_ids: Member ids from tc_list_project_members.
Returns: {"added": [ids], "count": int}
Inputs: group_id (required), user_ids (required), project_id (required). Returns: result
tc_add_project_userA
Invite a user to a project by email.
Requires TC_ENABLE_WRITE=1. The invitee gets status PENDING until they open the project.
Args: project_id: Project ID. email: Email address to invite. role: "USER" (default) or "ADMIN" — check tc_list_project_roles. notify: Send the invitation email (default True).
Returns the created member object with {"invited": true}.
Inputs: email (required), project_id (required), role, notify. Returns: result
tc_api_getARead-onlyIdempotent
Advanced escape hatch: perform a raw GET on the Trimble Connect Core API (v2) and return the raw JSON.
Use when no dedicated tool covers an endpoint (e.g. 'todos?projectId=X', 'views', 'releases', 'projects/{id}/activities'). Read-only — for writes use the dedicated tools, or tc_api_write.
Args: path: Path relative to the API base, e.g. 'projects/{id}/activities' or 'todos'. Must not include a scheme/host. project_id: Optional — route the call to this project's region. Omit to call the master (North America) server. params: Optional query parameters as a flat string dict.
Returns raw JSON (paginated list endpoints are fetched fully up to a safety cap).
Inputs: path (required), params, project_id.
tc_api_writeADestructive
Advanced escape hatch: raw POST/PATCH/PUT/DELETE on the Core API (v2).
Only for endpoints with no dedicated tool (todos, views, releases, attributes...). Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: method: "POST", "PATCH", "PUT" or "DELETE". path: Path relative to the API base, e.g. 'todos'. No scheme/host. confirm: Must be true — safety gate. project_id: Optional — route to this project's region (recommended; otherwise the master/North America server is used). params: Optional query parameters. body: Optional JSON body.
Returns the raw JSON response (or {"status": 204} for empty responses).
Inputs: path (required), method (required), body, params, +2 more.
tc_auth_statusARead-onlyIdempotent
Check whether the user is signed in to Trimble Connect.
Returns login state, token expiry, and the signed-in user's name/email (from the cached ID token). Call this first if any other tool returns an authentication error, and after a tc_login call that came back with "pending": true (login_in_progress marks a browser sign-in still waiting).
Inputs: no named parameters. Returns: result
tc_copy_fileA
Copy one file into another folder (server-side copy).
Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID (source and target must be the same project). file_id: Source file ID. target_folder_id: Destination folder ID. version_id: Optional specific version to copy; default = latest. copy_metadata: Also copy the file's metadata/attributes. merge_existing: If a file with the same name exists in the target, add the copy as a NEW REVISION of it instead of failing. Cannot be combined with copy_metadata.
Returns the new file object with {"copied": true}.
Inputs: file_id (required), project_id (required), target_folder_id (required), version_id, +2 more. Returns: result
tc_copy_folderA
Copy a folder and everything inside it to another location.
Trimble Connect has no server-side folder-copy endpoint, so this walks the tree and recreates folders + copies files one by one. Slow for large trees — max_items caps the work. Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. folder_id: Folder to copy. target_parent_folder_id: Folder that will contain the copy. new_name: Name for the copy (default: same name as the source). max_items: Safety cap on folders+files processed (default 300).
Returns: {"copied": true, "new_folder_id", "folders_created", "files_copied", "errors": [...], "truncated": bool}
Inputs: folder_id (required), project_id (required), target_parent_folder_id (required), new_name, +1 more. Returns: result
tc_create_folderA
Create ONE new folder inside a parent folder.
Requires TC_ENABLE_WRITE=1 (see tc_write_status).
Args: project_id: Project ID (resolves the region). name: New folder name (max 255 chars, must be unique in the parent). parent_folder_id: Parent folder; omit to create under the project ROOT folder.
Returns: {"created": true, "id", "name", "parentId", "path"}. For a whole CDE tree use tc_create_folder_structure instead.
Inputs: name (required), project_id (required), parent_folder_id. Returns: result
tc_create_folder_structureA
Create a whole folder tree in one call (e.g. an ISO 19650 CDE).
Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. paths: Folder paths relative to the start folder, '/' separated, e.g. ["01-WIP/01-ARC", "01-WIP/02-STR", "02-SHARED", "03-PUBLISHED"]. Intermediate levels are created automatically, so listing only the leaves is enough. parent_folder_id: Start folder; omit for the project ROOT. skip_existing: Reuse a folder that already exists instead of failing (default True) — makes the call safe to re-run.
Returns: {"created": [{"path","id"}], "existing": [{"path","id"}], "errors": [{"path","error"}], "root_folder_id": str}
Inputs: paths (required), project_id (required), skip_existing, parent_folder_id. Returns: result
tc_create_groupA
Create a user group in a project.
Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. name: Group name (e.g. "Architects", "Contractor - Site").
Returns the created group with {"created": true}.
Inputs: name (required), project_id (required). Returns: result
tc_delete_groupADestructive
Delete a project group. DESTRUCTIVE — any folder permission granted to this group disappears with it.
Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: project_id: Project ID. group_id: Group ID. confirm: Must be true — safety gate.
Returns: {"deleted": true, "group_id": str}
Inputs: group_id (required), project_id (required), confirm. Returns: result
tc_delete_itemADestructive
Delete a folder or a file. DESTRUCTIVE — there is no undo via the API.
Trimble Connect deletes are soft (an admin can restore from the web UI), but this API offers NO restore endpoint. Requires TC_ENABLE_WRITE=1 AND confirm=true. Always show the user what will be deleted first.
Args: project_id: Project ID. item_id: Folder or file ID. confirm: Must be true — safety gate. item_type: "FOLDER" (default) or "FILE". force: Required to delete a folder that is NOT empty (deletes the whole subtree, runs as a background job).
Returns: {"deleted": true, ...} or an error explaining what is missing.
Inputs: item_id (required), project_id (required), force, confirm, +1 more. Returns: result
tc_download_fileARead-onlyIdempotent
Download a file from Trimble Connect to the local disk.
Read-only on the Trimble side; writes only to the local download folder.
Args: project_id: Project the file belongs to. file_id: File ID (from tc_list_folder). version_id: Optional specific version (from tc_list_file_versions); default latest. file_name: Optional name for the saved file; defaults to the file's name from metadata. save_dir: Optional target directory; default TC_DOWNLOAD_DIR (~/Downloads/TrimbleConnect).
Returns: {"saved_to": str, "size_bytes": int}
Inputs: file_id (required), project_id (required), save_dir, file_name, +1 more. Returns: result
tc_folder_treeARead-onlyIdempotent
Render a compact text tree of the project's folder structure.
Recursively walks folders breadth-limited by max_depth and max_entries — ideal for a quick overview of a CDE structure before drilling in.
Args: project_id: Project ID. folder_id: Start folder (default: project root). max_depth: Levels to descend, 1-6 (default 3). max_entries: Hard cap on total lines to keep output small (default 400).
Returns: Markdown-ish text tree. Folders show their ID so you can call tc_list_folder / tc_folder_tree on a subtree; files show size and last modified date. A trailing note reports truncation, if any.
Inputs: project_id (required), folder_id, max_depth, max_entries. Returns: result
tc_get_fileARead-onlyIdempotent
Get metadata of a file (latest version): name, size, revision, dates.
Args: project_id: Project the file belongs to (resolves the region). file_id: File ID (from tc_list_folder).
Returns the raw file JSON from the API.
Inputs: file_id (required), project_id (required). Returns: result
tc_get_permissionsARead-onlyIdempotent
Read the access control list (ACL) of a folder or file.
Args: project_id: Project ID. item_id: Folder or file ID. item_type: "FOLDER" (default) or "FILE".
Returns: {"acl": {"READ": [ids], "FULL_ACCESS": [ids], "NO_ACCESS": [ids]}, "inheritance": bool, ...}. Ids are project user ids (tc_list_project_members) or group ids (tc_list_groups); the special id "tc-groups:*" means all project members. Files support only READ and FULL_ACCESS.
Inputs: item_id (required), project_id (required), item_type. Returns: result
tc_get_projectARead-onlyIdempotent
Get full details of one project (raw API object).
Args: project_id: Project ID from tc_list_projects.
Returns the complete project JSON including rootId (root folder), license info, counts and settings.
Inputs: project_id (required). Returns: result
tc_grant_permissionsA
Give users/groups a permission level on a folder or file (safe merge).
Reads the current ACL, moves the given subjects to the requested level, and writes the whole ACL back — everyone else keeps what they had. Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. item_id: Folder or file ID. subject_ids: User ids (tc_list_project_members) and/or group ids (tc_list_groups). Use "tc-groups:*" for all project members. level: "READ", "FULL_ACCESS", or "NO_ACCESS" (folders only). item_type: "FOLDER" (default) or "FILE". inheritance: Optional — set True/False to also change whether the folder inherits permissions from its parent.
Returns: {"updated": true, "acl": {...}, "inheritance": bool}
Inputs: item_id (required), project_id (required), subject_ids (required), level, +2 more. Returns: result
tc_list_file_versionsARead-onlyIdempotent
List the version history of a file.
Args: project_id: Project the file belongs to. file_id: File ID.
Returns: {"count": int, "versions": [...]} with versionId, revision, size, createdOn/modifiedOn and author per version (fields as provided by the API).
Inputs: file_id (required), project_id (required). Returns: result
tc_list_folderARead-onlyIdempotent
List the contents (subfolders and files) of one folder.
Args: project_id: Project ID (used to resolve the correct region). folder_id: Folder ID to list. Omit to list the project's ROOT folder.
Returns: {"folder_id": str, "count": int, "items": [{"id","name", "type" ("FOLDER"|"FILE"),"size","revision","versionId","modifiedOn", "modifiedBy",...}]}. Use item ids to descend into subfolders or fetch file details.
Inputs: project_id (required), folder_id. Returns: result
tc_list_groupsARead-onlyIdempotent
List the user groups of a project.
Groups are the practical way to grant folder permissions to a whole discipline or company at once.
Args: project_id: Project ID.
Returns: {"count": int, "groups": [{"id","name","usersCount",...}]}
Inputs: project_id (required). Returns: result
tc_list_group_usersARead-onlyIdempotent
List the members of a project group.
Args: project_id: Project ID (resolves the region). group_id: Group ID from tc_list_groups.
Returns: {"count": int, "users": [{"id","email","name","status"}]}
Inputs: group_id (required), project_id (required). Returns: result
tc_list_project_membersARead-onlyIdempotent
List members (users) of a project with their role and status.
Args: project_id: Project ID from tc_list_projects. include_removed: Also list users with status REMOVED (default False). group_id: Optional — only members of this group (see tc_list_groups).
Returns: {"count": int, "members": [{"id","email","name","role" ("ADMIN"|"USER"),"status" ("ACTIVE"|"PENDING"|"REMOVED")}]}. Member ids are what folder-permission tools expect as subject ids.
Inputs: project_id (required), group_id, include_removed. Returns: result
tc_list_project_rolesARead-onlyIdempotent
List the roles available in a project (typically ADMIN and USER).
Args: project_id: Project ID.
Returns: {"roles": [str]}
Inputs: project_id (required). Returns: result
tc_list_projectsARead-onlyIdempotent
List all Trimble Connect projects the signed-in user can access.
Queries every region and merges the results. Use this to find a project's ID before calling folder/file tools.
Args: name_filter: Optional case-insensitive substring to filter by name. refresh: Re-discover regions before listing (default False).
Returns: {"count": int, "projects": [{"id","name","rootId","region", "access","createdOn","modifiedOn",...}]}
Inputs: refresh, name_filter. Returns: result
tc_list_regionsARead-onlyIdempotent
List Trimble Connect regional servers (North America, Europe, Asia...).
Returns: {"count": int, "regions": [{"location": str, "origin": str}]} — 'origin' is the regional API base URL. Projects live in exactly one region; other tools resolve the region automatically from project_id.
Inputs: no named parameters. Returns: result
tc_loginAIdempotent
Sign in to Trimble Connect via the browser (OAuth2 + PKCE).
Opens the user's default browser at the Trimble Identity login page and listens on the registered localhost callback (TC_REDIRECT_URI, default http://localhost:8385/callback). Tokens are cached locally and refreshed automatically, so this is only needed the first time or after the session fully expires.
The call does NOT block indefinitely: if the sign-in is not finished within wait_seconds it returns {"pending": true, "auth_url": ...} while the callback listener keeps waiting in the background (up to 10 minutes total). In that case tell the user to finish signing in — opening auth_url manually if no browser appeared — and then call tc_auth_status to confirm. Do NOT immediately call tc_login again; a second call simply waits on the same pending login.
Args: wait_seconds: How long to wait before returning a pending result (default 90). Use a small value to return quickly. open_browser: Set false to only return auth_url without launching a browser (useful when the browser cannot be opened automatically).
Returns: {"logged_in": true, "user": {...}} on success, {"logged_in": false, "pending": true, "auth_url": ...} if the user has not finished yet, or {"error": ...}.
Inputs: open_browser, wait_seconds. Returns: result
tc_login_cancelAIdempotent
Abort a browser sign-in that is still waiting and free the callback port.
Use when a tc_login attempt was abandoned (wrong account, browser closed) and the local callback listener should stop before starting a new login.
Returns: {"cancelled": true|false}
Inputs: no named parameters. Returns: result
tc_move_itemA
Move a folder or file into another folder.
Requires TC_ENABLE_WRITE=1. Moving a folder moves its whole subtree, and permissions may change through inheritance in the new location.
Args: project_id: Project ID. item_id: Folder or file ID to move. new_parent_folder_id: Destination folder ID. item_type: "FOLDER" (default) or "FILE".
Returns: {"moved": true, "id", "name", "parentId", ...}
Inputs: item_id (required), project_id (required), new_parent_folder_id (required), item_type. Returns: result
tc_remove_group_usersADestructive
Remove members from a group (they stay in the project).
Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: project_id: Project ID. group_id: Group ID. user_ids: Member ids to remove. confirm: Must be true — safety gate.
Returns: {"removed": [ids], "count": int}
Inputs: group_id (required), user_ids (required), project_id (required), confirm. Returns: result
tc_remove_permissionsADestructive
Remove users/groups from a folder's or file's ACL entirely.
They fall back to whatever the parent folder / project grants them. To actively BLOCK someone instead, use tc_grant_permissions with level="NO_ACCESS". Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: project_id: Project ID. item_id: Folder or file ID. subject_ids: User/group ids to drop from the ACL. confirm: Must be true — safety gate. item_type: "FOLDER" (default) or "FILE".
Returns: {"updated": true, "acl": {...}, "removed": [ids]}
Inputs: item_id (required), project_id (required), subject_ids (required), confirm, +1 more. Returns: result
tc_remove_project_userADestructive
Remove a member from a project. DESTRUCTIVE — they lose all access.
Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: project_id: Project ID. user_id: Member id from tc_list_project_members. confirm: Must be true — safety gate.
Returns: {"removed": true, "user_id": str}
Inputs: user_id (required), project_id (required), confirm. Returns: result
tc_rename_groupA
Rename a project group.
Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. group_id: Group ID. new_name: New group name.
Returns the updated group with {"renamed": true}.
Inputs: group_id (required), new_name (required), project_id (required). Returns: result
tc_rename_itemA
Rename a folder or a file.
Requires TC_ENABLE_WRITE=1. Renaming and moving must be separate calls — the API ignores the new name if a new parent is sent at the same time.
Args: project_id: Project ID. item_id: Folder or file ID. new_name: New name. item_type: "FOLDER" (default) or "FILE".
Returns: {"renamed": true, "id", "name", ...}
Inputs: item_id (required), new_name (required), project_id (required), item_type. Returns: result
tc_searchARead-onlyIdempotent
Search Trimble Connect for files, folders, todos etc. by text.
Args: query: Search text (e.g. a file name or keyword). project_id: Optional — limit the search to one project (faster, searches only that project's region). Omit to search all regions.
Returns: {"count": int, "results": [...]} (raw search results from the API, per region).
Inputs: query (required), project_id. Returns: result
tc_set_permissionsADestructive
REPLACE the whole ACL of a folder or file (advanced).
Everything not listed in acl loses its explicit permission. Prefer
tc_grant_permissions / tc_remove_permissions, which merge safely.
Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: project_id: Project ID. item_id: Folder or file ID. acl: {"READ": [ids], "FULL_ACCESS": [ids], "NO_ACCESS": [ids]} — levels may be omitted. "tc-groups:*" = all project members. confirm: Must be true — safety gate. item_type: "FOLDER" (default) or "FILE". inheritance: Optional — whether the folder inherits from its parent.
Returns: {"updated": true, "acl": {...}, "previous_acl": {...}}
Inputs: acl (required), item_id (required), project_id (required), confirm, +2 more. Returns: result
tc_update_project_userA
Change a project member's role (e.g. USER → ADMIN).
Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. user_id: Member id from tc_list_project_members (not the email). role: "ADMIN" or "USER".
Returns the updated member object with {"updated": true}.
Inputs: role (required), user_id (required), project_id (required). Returns: result
tc_upload_fileA
Upload a NEW file from the local disk into a Trimble Connect folder.
Fails if a file with the same name already exists in that folder — use tc_upload_new_version to add a revision instead. Requires TC_ENABLE_WRITE=1.
Args: project_id: Project ID. folder_id: Destination folder ID (tc_list_folder / tc_folder_tree). local_path: Full path of the file on this computer. name: Optional name to use in Trimble Connect (default: file name).
Returns: {"uploaded": true, "file_id", "version_id", "revision", "name", "size_bytes"}
Inputs: folder_id (required), local_path (required), project_id (required), name. Returns: result
tc_upload_new_versionADestructive
Upload a file as a NEW VERSION of an existing file in that folder.
The existing file keeps its history; the uploaded content becomes the latest revision that everyone will see. Requires TC_ENABLE_WRITE=1 AND confirm=true.
Args: project_id: Project ID. folder_id: Folder that already contains the file. local_path: Full path of the new content on this computer. name: Name of the existing file in Trimble Connect (default: the local file name) — it must match exactly, otherwise a new file is created instead. confirm: Must be true — safety gate.
Returns: {"uploaded": true, "file_id", "version_id", "revision", ...}
Inputs: folder_id (required), local_path (required), project_id (required), name, +1 more. Returns: result
tc_write_statusARead-onlyIdempotent
Check whether this server may modify data in Trimble Connect.
Write tools (create/rename/move/copy/upload/delete, permissions, members, groups) only work when the environment variable TC_ENABLE_WRITE=1 is set for this MCP server in Claude Desktop. Destructive tools additionally require confirm=true on the call.
Returns: {"write_enabled": bool, "env_var": str, "how_to_enable": str, "destructive_tools_need": "confirm=true"}
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 40 tools
Each tool targets a distinct resource-action pair (e.g., list_projects vs get_project, upload_file vs upload_new_version). Even closely related tools like tc_list_folder and tc_folder_tree are explicitly differentiated by output format (raw items vs text tree), and permission tools have clear semantics (get, merge, replace, remove). No two tools appear to do the same thing.
All tools share the `tc_` prefix and mostly follow a verb_noun pattern (get_project, create_folder, list_groups). A few exceptions like tc_folder_tree, tc_auth_status, and tc_write_status use noun-first naming, but the pattern remains predictable and readable.
With 40 tools, the surface is very large. While the domain is broad, many tools are granular (e.g., 7 group tools, 6 permission tools) and there are two raw API escape hatches (tc_api_get/write) that add complexity. This exceeds the typical well-scoped range and could overwhelm agents.
The tool set provides comprehensive coverage of the Trimble Connect CDE: auth, project management, folder/file operations (create, read, update, delete, copy, move, versioning), permissions, groups, members, and search. Raw API tools fill any remaining gaps, so there are no obvious dead ends.
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server giving Claude AI access to 22+ NYC public-record databases for real estate due diligence
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-powered MCP server that enables Claude and other LLMs to interact directly with construction documents, drawings, and specifications through advanced RAG and hybrid search capabilities.8MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.11 npm-
- AlicenseAqualityBmaintenanceMCP server that lets Claude manage an ISO 19650 / TCVN 14177 Common Data Environment on Autodesk Construction Cloud — projects, CDE folder trees, permissions, files, document status and naming compliance.451MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets users query, validate, convert, and compare IFC/BIM files using natural language. Runs fully locally and integrates with AI agents like Claude.8MIT