get_vehicle_context — TuneWorks MCP Tool Read-only
get_vehicle_context
(get vehicle context) is one of 96 tools on the
TuneWorks
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_vehicle_context from your client
- Claude Code TuneWorks get_vehicle_context run in your project directory
- Claude Desktop TuneWorks get_vehicle_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TuneWorks get_vehicle_context ~/.cursor/mcp.json
- VS Code TuneWorks get_vehicle_context .vscode/mcp.json
- Zed TuneWorks get_vehicle_context ~/.config/zed/settings.json
- Windsurf TuneWorks get_vehicle_context ~/.codeium/windsurf/mcp_config.json
- Cline TuneWorks get_vehicle_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TuneWorks get_vehicle_context ~/.gemini/settings.json
- Grok TuneWorks get_vehicle_context .mcp.json (in your project root)
- ChatGPT TuneWorks get_vehicle_context Settings → Connectors → Advanced → Developer mode
- Claude.ai TuneWorks get_vehicle_context Settings → Connectors → Add custom connector
- LangChain TuneWorks get_vehicle_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tuneworks https://tuneworks.ai/mcpOther tools on this server
- calculate_race_fuel_and_weight
- calculate_gear_ratio_speed
- calculate_tire_pressure_adjustment
- calculate_corner_balance
- calculate_spring_wheel_rate
- calculate_fuel_injector_size
- convert_afr_lambda
- calculate_brake_bias
- compare_tire_sizes
- check_race_alignment
- calculate_lap_time_delta
- calculate_ethanol_blend
- diagnose_handling_issue
- analyze_tire_temperatures
- recommend_autocross_damper_adjustment
- find_autocross_sites
- get_tuneworks_app_capabilities
- create_vehicle
- update_vehicle
- list_vehicle_modifications
- get_vehicle_modification
- create_vehicle_modification
- update_vehicle_modification
- archive_vehicle_modification
- delete_vehicle_modification
- get_garage_summary
- list_vehicles
- list_logs
- get_log_context
- archive_vehicle
- list_setups
- create_setup
- update_setup
- archive_setup
- list_sessions
- create_session
- update_session
- copy_session
- archive_session
- list_maintenance
- create_maintenance
- update_maintenance
- archive_maintenance
- list_shop_lists
- get_shop_list
- list_shop_list_items
- create_shop_list
- update_shop_list
- add_shop_list_category
- add_shop_list_item
- copy_shop_list
- reset_shop_list_items
- update_shop_list_item
- archive_shop_list
- delete_shop_list
- get_share_build_options
- preview_share_build
- get_user_settings
- update_user_preferences
- update_unit_settings
- create_vehicle_make
- update_vehicle_make
- delete_vehicle_make
- list_chart_channel_sets
- create_chart_channel_set
- mark_chart_channel_set_used
- delete_chart_channel_set
- list_favorite_charts
- create_favorite_chart
- delete_favorite_chart
- get_vehicle_map_config
- save_vehicle_map_config
- complete_maintenance
- list_ecu_files
- inspect_ecu_file
- process_ecu_file
- retry_ecu_file
- delete_ecu_file
- send_share_build
- list_teams
- create_team
- rename_team
- update_team_member_role
- remove_team_member
- revoke_team_invite
- leave_team
- delete_team
- send_team_invite
- list_custom_tracks
- get_custom_track
- create_custom_track
- update_custom_track
- delete_custom_track
- list_object_attachments
- delete_object_attachment
This list was read from the server itself, by connecting to it and calling tools/list on 18 October 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.