has_arco — gdex mcp MCP Tool
has_arco
(has arco) is one of 30 tools on the
gdex mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call has_arco from your client
- Claude Code gdex mcp has_arco run in your project directory
- Claude Desktop gdex mcp has_arco ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor gdex mcp has_arco ~/.cursor/mcp.json
- VS Code gdex mcp has_arco .vscode/mcp.json
- Zed gdex mcp has_arco ~/.config/zed/settings.json
- Windsurf gdex mcp has_arco ~/.codeium/windsurf/mcp_config.json
- Cline gdex mcp has_arco ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI gdex mcp has_arco ~/.gemini/settings.json
- Grok gdex mcp has_arco .mcp.json (in your project root)
- ChatGPT gdex mcp has_arco Settings → Connectors → Advanced → Developer mode
- Claude.ai gdex mcp has_arco Settings → Connectors → Add custom connector
- LangChain gdex mcp has_arco pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gdex-mcp https://gdex-mcp.k8s.ucar.edu/mcp
Other tools on this server
- list_datasets
- get_dataset_metadata
- get_dataset_field
- describe_dataset
- get_file_groups
- get_dataset_files
- find_dataset_files
- get_filesearch_datatypes
- get_filesearch_grid_filters
- get_filesearch_cyclone_fix_filters
- get_filesearch_sensor_filters
- get_filesearch_grid_files
- get_filesearch_cyclone_fix_files
- get_filesearch_sensor_files
- get_filesearch_result_page
- get_data_access
- get_arco_variables
- search_arco_variables
- get_portal_metrics
- get_dataset_metrics
- get_staff
- list_request_statuses
- check_request_status
- get_request_files
- get_control_file_template
- validate_subset_request
- submit_subset_request
- submit_and_wait_for_request
- purge_request
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.