get_load_test_url_timings — Loadster MCP Tool Read-only
get_load_test_url_timings
(get load test url timings) is one of 62 tools on the
Loadster
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_load_test_url_timings from your client
- Claude Code Loadster get_load_test_url_timings run in your project directory
- Claude Desktop Loadster get_load_test_url_timings ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Loadster get_load_test_url_timings ~/.cursor/mcp.json
- VS Code Loadster get_load_test_url_timings .vscode/mcp.json
- Zed Loadster get_load_test_url_timings ~/.config/zed/settings.json
- Windsurf Loadster get_load_test_url_timings ~/.codeium/windsurf/mcp_config.json
- Cline Loadster get_load_test_url_timings ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Loadster get_load_test_url_timings ~/.gemini/settings.json
- Grok Loadster get_load_test_url_timings .mcp.json (in your project root)
- ChatGPT Loadster get_load_test_url_timings Settings → Connectors → Advanced → Developer mode
- Claude.ai Loadster get_load_test_url_timings Settings → Connectors → Add custom connector
- LangChain Loadster get_load_test_url_timings pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http loadster-mcp https://api.loadster.com/mcpOther tools on this server
- get_screenshot
- get_command_schema
- get_example
- get_scripting_api
- get_variable_schema
- list_command_types
- validate_script
- append_dataset_rows
- create_dataset
- delete_dataset
- get_dataset
- list_datasets
- update_dataset
- list_engines
- submit_feedback
- get_documentation
- create_monitor
- delete_monitor
- disable_monitor
- enable_monitor
- get_incident
- get_monitor
- get_monitor_cycle_detail
- get_monitoring_summary
- list_incidents
- list_monitor_cycles
- list_monitoring_locations
- list_monitors
- update_monitor
- get_load_test_report
- get_load_test_status
- list_load_tests
- stop_load_test
- update_load_test_notes
- create_scenario
- delete_scenario
- get_scenario
- launch_load_test
- list_scenarios
- update_scenario
- create_project
- create_script
- delete_script
- delete_script_asset
- duplicate_script
- get_play_status
- get_script
- get_script_asset
- get_script_revision
- get_step_detail
- import_script
- list_projects
- list_script_assets
- list_script_revisions
- list_scripts
- play_script
- put_script_asset
- restore_script_revision
- stop_script
- update_project
- update_script
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.