globus-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLOBUS_CLIENT_ID | No | Client ID for a registered Globus application | |
| GLOBUS_CLIENT_SECRET | No | Client secret for a registered Globus application |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| globus_compute_list_endpointsB | List Globus Compute endpoints that the user has access to. |
| globus_compute_register_python_functionA | Register a Python function with Globus Compute. Use globus_compute_submit_task to run the registered Python function on an endpoint. |
| globus_compute_register_shell_commandA | Register a shell command function with Globus Compute. Use globus_compute_submit_task to run the registered shell command on an endpoint. |
| globus_compute_submit_taskA | Submit a function execution task to a Globus Compute endpoint. Use globus_compute_get_task_status to monitor progress and retrieve results. |
| globus_compute_get_task_statusB | Retrieve the status and result of a Globus Compute task. |
| globus_transfer_search_endpoints_and_collectionsA | Use a filter string to search all Globus Transfer endpoints and collections that are visible to the user. |
| globus_transfer_list_endpoints_and_collectionsC | List Globus Transfer endpoints and collections that the user has access to, filtered based on the provided scope. |
| globus_transfer_submit_taskA | Submit a transfer task between two Globus Transfer collections. Use globus_transfer_get_task_events to monitor the task's progress. |
| globus_transfer_get_task_eventsA | Get a list of Globus Transfer task events to monitor the status and progress of a task. The events are ordered by time descending (newest first). |
| globus_transfer_list_directoryB | List contents of a directory on a Globus Transfer collection |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The tools are cleanly separated into two distinct domains (Globus Compute and Globus Transfer), with no overlap in functionality. Each tool has a unique and clear purpose, aided by detailed descriptions that specify when to use each.
All tool names follow a consistent pattern: globus_{domain}_{verb}_{noun} in snake_case. This makes it predictable and easy for an agent to infer functionality from the name.
With 10 tools covering the key operations for both Compute and Transfer services, the count is well-scoped. Each tool addresses a distinct need without unnecessary duplication, and the set feels complete for typical workflows.
The tool surface covers the essential operations for both services: registration, listing, submission, and status retrieval for Compute; listing, searching, directory browsing, submission, and event monitoring for Transfer. Minor omissions like delete or cancel are present but don't significantly hinder core usage.