Globus MCP Server

The Globus MCP Server enables LLM applications to interact

with Globus services.

Supported Tools

Globus Transfer

• `globus_transfer_list_endpoints_and_collections` - List endpoints and collections the user has

access to

• `globus_transfer_search_endpoints_and_collections` - Use a filter string to search all endpoints

and collections that are visible to the user

• `globus_transfer_submit_task` - Submit a transfer task between two collections
• `globus_transfer_get_task_events` - Get a list of task events
• `globus_transfer_list_directory` - List contents of a directory on a collection

Globus Compute

• `globus_compute_list_endpoints` - List endpoints that the user has access to
• `globus_compute_register_python_function` - Register a Python function
• `globus_compute_register_shell_command` - Register a shell command
• `globus_compute_submit_task` - Submit a task to an endpoint
• `globus_compute_get_task_status` - Retrieve the status and result of a task

Configuration

The following configuration is compatible with most LLM applications that support MCP such as

Claude Desktop:

{
  "mcpServers": {
    "globus-mcp": {
      "command": "uvx",
      "args": ["globus-mcp"]
    }
  }
}

Limiting Tool Registration

By default, the Globus MCP server registers tools for every service. To register tools for only

specific services, use the `--services` command-line flag:

{
  "mcpServers": {
    "globus-mcp": {
      "command": "uvx",
      "args": [
        "globus-mcp",
        "--services",
        "compute"
      ]
    }
  }
}

Specifying Client Credentials

If you've registered a client application

in the Globus web UI, you can specify the client

credentials via the `GLOBUS_CLIENT_ID` and `GLOBUS_CLIENT_SECRET` environment variables:

{
  "mcpServers": {
    "globus-mcp": {
      "command": "uvx",
      "args": ["globus-mcp"],
      "env": {
        "GLOBUS_CLIENT_ID": "...",
        "GLOBUS_CLIENT_SECRET": "..."
      }
    }
  }
}